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

Closed

as Duplicate Help for as Duplicate

Type:	Bug
ID:	777454
Opened:	1/24/2013 3:52:03 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

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.

Details (expand)

.NET Framework 4.0

1. Create a solution
2. Add a Web Application Project (include a test site)
3. Add a Deployment Project
4. Add a Merge Module Project
5. Create a Custom Folder called Scripts under the File System on Target Machine
6. In the Merge Module project add dummy files to the Merge Module Folder
7. Add the Merge Module output to the Scripts folder in the Deployment project
8. Build your deployment project
9. Create a Site in IIS
10. Under that site create a folder called scripts
11. Create a Virtual application site under the new site created

English

Windows Vista

English

The dummy files in the scripts folder of the deployment project that is linked to the merge module are copied to the root folder of the web application.

The dummy files in the scripts folder of the deployment project that is linked to the merge module should be copied to the scripts folder on the same folder level as the web site.

0 attachments

Posted by Microsoft on 2/11/2013 at 11:07 AM

Thank you for reporting this issue. The workaround is posted on here: http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/1952fc67-ed1e-4a11-ab15-4e83680125c5 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.

Microsoft