MSM (Merge Module) does not copy to correct folder - by Big Joe D

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 777454 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/24/2013 3:52:03 PM
Access Restriction Public


In my solution I have 3 projects, a Web, a Setup (build) and a Merge Module. The merge module contains 3rd part files. In my setup project on the file system I have a folder called scripts that I use to link the merge module to. I also have the default Web Application Folder that I use to get my Content and Primary output from. Everything builds correctly but when I deploy the MSI the files that should be placed in the Scripts folder that is created is instead put in the Web application root folder. This is not the behavior that I am expecting.
Sign in to post a comment.
Posted by Microsoft on 2/11/2013 at 11:07 AM
Thank you for reporting this issue. The workaround is posted on here: Please give that a try and let us know if it works for you.
Posted by Microsoft on 2/1/2013 at 1:52 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.