Web Deployment 2008 - The specified task executable location "bin\aspnet_merge.exe" is invalid. RRS feed

  • Question

  • User-1048133854 posted

     I'm getting the following error when using the new Web Deployment Project 2008. The build logs shows the following:

     C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_compiler.exe -v /DuncanAndTodd.iTrust.Web.csproj -p "C:\Work\Duncan & Todd\iTrust\Source\Web" -u -f -d .\TempBuildDir\
    Running aspnet_merge.exe.
    C:\Program Files\MSBuild\Microsoft\WebDeployment\v9.0\Microsoft.WebDeployment.targets(586,9): error MSB6004: The specified task executable location "bin\aspnet_merge.exe" is invalid.
    Done building project "DuncanAndTodd.iTrust.Web.Deploy.wdproj" -- FAILED.

      This is the line in the Microsoft.WebDeployment.targets file is:

        <Target Name="AspNetMerge" Condition="'$(UseMerge)' == 'true'" DependsOnTargets="$(MergeDependsOn)">


    Not sure if changing ExePath="$(FrameworkSDKDir)bin" would help. Havn't tried it yet.

    Any ideas guys?

    Monday, December 3, 2007 6:01 AM

All replies

  • User-1048133854 posted

    Doing some more digging, it seems the aspnet_merge.exe is not being shipped with the new Web Deployment Project. I check the previous version for path it contained


    Updating the new Microsoft.WebDeployment.targets with the above fixes the problem but this is obviously a hack. Anyone from ASP.NET team like to expand on this?


    Monday, December 3, 2007 8:17 AM
  • User-953368566 posted

    Note that when you do this, you need to close your solution and re-open it.

    It's a really bad hack. Hopefully this is fixed in the RTM version

    Sunday, January 6, 2008 5:56 PM
  • User-762694769 posted

    The new version of aspnet_merge.exe is shipped as part of Windows SDK which is installed together with VS2008 RTM. Eg.:

    C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\aspnet_merge.exe

    Do you have Windows SDK and this exe on your machine?

    Tuesday, January 8, 2008 3:45 PM
  • Tuesday, January 8, 2008 4:47 PM
  • User-1341056535 posted
    I got the same issue on one of my computer (I still don't understand what was different on that one...) and installing SDK 6.1 fixed it up. BUT be aware that: 1) this SDK might take significant amount of time to download and install (I have a DSL at 600 kb/s) 2) If you change your mind and "cancel" the installation in the middle of the process. Your visual Studio might have been already hooked up to this new SDK and this is NOT rolled back by the "CANCEL" action. (merde!) 3) I noticed that the content of the "bin" folder of my old SDK 6.0A was gone after I "removed" the SDK 6.1 (using the setup.exe of SDK 6.1 of course...); I have strong suspicions that the "remove" from SDK-6.1 also did wipe out my older SDK-6.0A... fortunately everything turned out okay after I reinstalled the 6.1
    Wednesday, April 29, 2009 10:59 PM