Problem description:
The typical needs of developing a setup project for a Visual Studio C# solution in terms of including the primary output and references are handled poorly by the Advanced installer.
How to reproduce:
a) Use the attached VS solution to reproduce the issues.
b) You can't add "Project Output" to the "Application Folder" only to a sub-directory named after a project.
c) When adding Project Output references it includes all references including dlls from the .NET framework. These aren't needed as the MSI being built has a dependency on the .net framework being there.
d) When adding Project Output references it only adds direct dll references and doesn't successfully traverse the dependency like the vdproj based functionality did.
e) Its unclear how to define the equivalents of Visual Studio build configurations. The automatic vdproj converter does do this but its unclear how to achieve this in a manually defined AIP file.
f) Editing source paths per build is possible per file but it appears to have to be done on a per file basis. This incurs needless work by the user since there is a clear Debug/Release pattern involved.
I'm impressed by the Advanced Installer functionality. Its just that the vdproj functionality (for all its faults) did do a lot of things automatically for C# developers. Moving to something like WiX or Advanced Installer loses a lot of that productivity. I'd really like to get that productivity back for the 90% case of small business deployment needs. Can you help by either showing me how to resolve these issues or taking them on board in your product development?
Ideally you should have some multi-vs-project C# solutions in house to use as exemplars and compare the vdproj results to Advanced Installer results in terms of productivity. It would even be worth having some specific documentation for people moving from a vdproj approach addressing real world issues and development processes.
Regards,
Apolon.
FOLLOW US
Get the latest news in Application Packaging