Last post May 14, 2006 08:18 AM by MNF
Nov 24, 2005 06:33 AM|richbaker|LINK
Running aspnet_merge.exe ...
C:\Program Files\MSBuild\Microsoft\WebDeployment\v8.0\aspnet_merge.exe C:\MyProjects\VDN2\VDN2_deploy\Release -o VDN2_deploy -copyattrs
C:\Program Files\MSBuild\Microsoft\WebDeployment\v8.0\Microsoft.WebDeployment.targets(474,9): error MSB6006: "aspnet_merge.exe" exited with code 1.
Done building project "VDN2_deploy.wdproj" -- FAILED.
========== Rebuild All: 1 succeeded, 1 failed, 0 skipped ==========
Could someone tell what this means and how to fix it?
Nov 25, 2005 12:36 PM|ScottGu|LINK
This is most likely caused by you having two classes with the same name in your project. To figure out which class is the cause, go to your Tools->Options menu in VS and drill into the "Projects and Solutions->Build And run node. There you can set the
MSBuild output verbostity mode -- change it to "normal" for your profile. This will then allow you to see more information on the build error, and it should pin-point the class name conflict.
Hope this helps,
Nov 28, 2005 04:52 AM|richbaker|LINK
Many thanks for that, but I had to change the option to "Detail" to get the exact error. I was trying to build DotNetNuke 4.0. I will post this on the DotNetNuke forum.
Using "AspNetMerge" task from assembly "C:\Program Files\MSBuild\Microsoft\WebDeployment\v8.0\Microsoft.WebDeployment.Tasks.dll".
C:\Program Files\MSBuild\Microsoft\WebDeployment\v8.0\aspnet_merge.exe C:\MyProjects\DNN42\DNN4_deploy\Debug -o DNN4_deploy -debug -copyattrs
The "AspNetMerge" task is using "aspnet_merge.exe" from "C:\Program Files\MSBuild\Microsoft\WebDeployment\v8.0\aspnet_merge.exe".
Utility to merge precompiled ASP.NET assemblies.
Copyright (C) Microsoft Corporation. All rights reserved.
An error occurred when merging assemblies: ILMerge.Merge: ERROR!!: Duplicate type 'DotNetNuke.UI.Skins.Controls.SolPartMenu' found in assembly 'App_Web_fhh6ifkz'.
Done executing task "AspNetMerge" -- FAILED.
Done building target "AspNetMerge" in project "DNN4_deploy.wdproj" -- FAILED.
Done building project "DNN4_deploy.wdproj" -- FAILED.
Time Elapsed 00:00:56.56
Dec 01, 2005 06:59 AM|richbaker|LINK
Dec 02, 2005 12:36 AM|ScottGu|LINK
The compilation and web copy support have a fall-back mechanism where if they detect a duplicate class name they can split it out into a separate assembly. The problem is that you've configured the web deployment project to emit a single assembly -- in
which case obviously it can't split it out (or it would defeat your intent).
What I'd recommend is doing a Quick Find (Ctrl F) for classes named "'DotNetNuke.UI.Skins.Controls.SolPartMenu". This is the class that is defined twice in the project and causing the problem. You'll want to delete or rename one of
them -- in which case it will build fine.
Dec 02, 2005 09:25 AM|richbaker|LINK
I can only find one definition for the class and it is in a partial class.
Dec 02, 2005 10:45 AM|ScottGu|LINK
Are you using the standard DotNetNuke download, or have you made changes to it? If the former, the I will go ahead and try it out on my own machine to try and see if I get the same error.
Dec 02, 2005 11:25 AM|richbaker|LINK
I am using the standard DotNetNuke 4.0.0 Starter Kit Download from
Feb 08, 2006 05:42 PM|MNF|LINK
I have the same error.
Did you find a solution or any workaround?
Feb 08, 2006 09:12 PM|ScottGu|LINK
Can you try these steps:
>>> To figure out which class is the cause, go to your Tools->Options menu in VS and drill into the "Projects and Solutions->Build And run node. There you can set the MSBuild output verbostity mode -- change it to "detailed" for your profile. This will
then allow you to see more information on the build error.
What is the error message that shows up in the output window when you build with this MsBuild verbosity level set?
Feb 09, 2006 02:40 AM|MNF|LINK
The error I have is the same that richbaker reported on 11-28-2005:
An error occurred when merging assemblies: ILMerge.Merge: ERROR!!: Duplicate type 'DotNetNuke.UI.Skins.Controls.SolPartMenu' found in assembly 'App_Web_k5hhsnh0'.
There is also another thread about the same issue.
Feb 12, 2006 10:29 PM|ScottGu|LINK
Unfortunately I think the above error is because DotNetNuke defines that class in two places. I've seen someone else have this same problem before. It only hits when you merge things into a single assembly -- which is why most people using the default
(non-single assembly) build option don't run into it.
You might try building a separate assembly for each directory (one of the other build options that VS 2005 Web Deployment Projects provide). Alternatively, you should search for that class name within the DNN project and eliminate/rename one of the duplicate
May 14, 2006 08:18 AM|MNF|LINK