CODEWITHSUNDEEP
.netwindows-installersetup-project
pdiddy
pdiddy

Reputation: 6297

Creating One MSI for multiple project

I have 2 projects. I want to create ONE single MSI setup package that will install both of those projects.

In My Application Folder I have created 2 subfolders (Project A and Project B folder). So after the install, the project ouputs will be in Program Files\MyProduct\Project A Program Files\MyProduct\Project B

The problem I am having is that Project A and Project B references some common assemblies. But those common assemblies is only copied to Project A folder.

Is there a way to force the msi to copy the common assemblies to Project A and Project B folder ?

Upvotes: 0

Views: 1564

Answers (2)

Charlie Salts
Charlie Salts

Reputation: 13488

Building MSI installers from within Visual Studio, as part of the build process, isn't always the most flexible method. I personally use NSIS as it is extremely powerful but if you're looking to build MSI installers, I suggest you look at Wix.

I rarely let Visual Studio do things for me automatically - I like to be explicit when it comes to declaring which dlls are installed, and where.

Upvotes: 2

Jacob Ewald
Jacob Ewald

Reputation: 2178

In your setup project I assume you have two folders, one for each project. Select the folder that is missing the .dll(s) and right-click it, hit Add->File... and choose the .dll that you want to force to be included with the project output.

Upvotes: 0

Related Questions