After I upgraded my local machine to .NET 4.0 and VS 2010, we deployed the new framework to our test server. I used the Web Installer on the test system. (http://www.microsoft.com/download/en/details.aspx?id=17851)
The application works just fine, but this is the server we build from and the Web Installer did not install the newest version of ASPNET_MERGE.exe and throws an error when trying to merge because it is looking for the .NET 4.0 version.
Does anyone know where I can get this?Can I just copy that directory from my local machine?
May I please have the error message? In Windows 2003, you need to manually enable ASP.NET 4.0 support via your IIS -> Website -> right click "Properties" and go to the ASP.NET tab.
If you have converted it to ASP..NET 4 and still does not work, please advise the error message here. Thanks
As I said, the application works just fine on the server. I have already enabled 4.0 in IIS.
I am getting the error when I try to run the aspnet_merge utility because the 4.0 framework installer I used did not install the newest version of aspnet_merge onto the server.
The error is: An error occurred when merging assemblies: Module or assembly depends on a version of core library that is newer than the one reader uses to resolve system types.
This is because aspnet_merge was not included in the 4.0 framework install that I installed. Any ideas on where I can find it? Google is not very helpful.
Better late than never, but by installing the IDE on the server, it had the updated aspnet_merge utility with it. I simply copied that to the folder that had my shortcut, deleted the old utility, and everything was fine. I had to change the options though
for it to work. I added -a and everything has been working fine since.
-Mike
Marked as answer by mth13 on May 01, 2012 05:01 PM
mth13
Member
331 Points
96 Posts
ASP.NET 4.0 Web Installer did not install the new aspnet_merge utility
Sep 22, 2011 01:23 PM|LINK
Hi again,
After I upgraded my local machine to .NET 4.0 and VS 2010, we deployed the new framework to our test server. I used the Web Installer on the test system. (http://www.microsoft.com/download/en/details.aspx?id=17851)
The application works just fine, but this is the server we build from and the Web Installer did not install the newest version of ASPNET_MERGE.exe and throws an error when trying to merge because it is looking for the .NET 4.0 version.
Does anyone know where I can get this?Can I just copy that directory from my local machine?
We are running Windows Server 2003.
Thanks,
-Mike
necro_mancer
Star
8089 Points
1590 Posts
Re: ASP.NET 4.0 Web Installer did not install the new aspnet_merge utility
Sep 23, 2011 03:10 AM|LINK
hi mth13,
May I please have the error message? In Windows 2003, you need to manually enable ASP.NET 4.0 support via your IIS -> Website -> right click "Properties" and go to the ASP.NET tab.
If you have converted it to ASP..NET 4 and still does not work, please advise the error message here. Thanks
Professional SQL 2008 R2 Service
mth13
Member
331 Points
96 Posts
Re: ASP.NET 4.0 Web Installer did not install the new aspnet_merge utility
Sep 23, 2011 12:21 PM|LINK
Necro_mancer,
As I said, the application works just fine on the server. I have already enabled 4.0 in IIS.
I am getting the error when I try to run the aspnet_merge utility because the 4.0 framework installer I used did not install the newest version of aspnet_merge onto the server.
The error is: An error occurred when merging assemblies: Module or assembly depends on a version of core library that is newer than the one reader uses to resolve system types.
This is because aspnet_merge was not included in the 4.0 framework install that I installed. Any ideas on where I can find it? Google is not very helpful.
-Mike
mth13
Member
331 Points
96 Posts
Re: ASP.NET 4.0 Web Installer did not install the new aspnet_merge utility
May 01, 2012 05:01 PM|LINK
Better late than never, but by installing the IDE on the server, it had the updated aspnet_merge utility with it. I simply copied that to the folder that had my shortcut, deleted the old utility, and everything was fine. I had to change the options though for it to work. I added -a and everything has been working fine since.
-Mike