Custom Modules

Re: Aspnet_merge.exe Exited with Code 1

MNF — Thu, 04 May 2006 05:48:35 GMT

I finally fixed the problem by excluding "admin\Skins\menu.ascx“ and "admin\Containers\actions.ascx" from the Web Application.

See more in my blog post

Re: Aspnet_merge.exe Exited with Code 1

P-Chip — Fri, 03 Mar 2006 18:46:45 GMT

I had the same problem. The only way I found around it was to pick the option "Create a separate assembly for each page and control output" in the Web Deployment project property under Output Assemblies.

HTH

Pat

Re: Aspnet_merge.exe Exited with Code 1

MNF — Fri, 03 Feb 2006 02:33:36 GMT

I have the same error. After changing option to show verbose output it shows:

An error occurred when merging assemblies: ILMerge.Merge: ERROR!!: Duplicate type 'DotNetNuke.UI.Skins.Controls.SolPartMenu' found in assembly 'App_Web_k5hhsnh0'.

C:\Program Files\MSBuild\Microsoft\WebDeployment\v8.0\Microsoft.WebDeployment.targets(474,9): error MSB6006: "aspnet_merge.exe" exited with code 1.

Done executing task "AspNetMerge" -- FAILED.

It seems that it even is not related to a number of modules.

The error doesn't make sense for me.

Aspnet_merge.exe Exited with Code 1

workcontrol — Wed, 25 Jan 2006 05:20:09 GMT

When using VS 2005 Web Deployment Projects to build the project, I got error "Aspnet_merge.exe Exited with Code 1". According to Google, the error comes from duplicate class names in the project, even if the name comes from different name space. Does anyone have work around for this?

I am trying to convert a few DNN 3 to version 4 and was hoping to use the Web Deployment Projects to build assembly names similar to VS 2003. However, each module in DNN 3 has a DataProvider amd SQLDataProvider class. So if you upgrade two modules, you will have dup class names. VS2005 build is a pain in the rear.