Upgrading .NET .vdproj from VS2010 issues

[apolon]

I'm coming to Advanced Installer from a Visual Studio vdproj user's perspective. The existing vdproj files are VS2010 based and I'm running VS2013. Advanced Installer picks up the vdproj as an issue and supports an automatic upgrade to an aip VS project. However it doesn't appear to handle .NET based requirements very well. Every project upgrade I've tried ends up with build issues and strange results.

Problem Description:
Advanced Installed doesn't handle .NET Visual Studio vdproj project upgrades so as to produce a similar deployment result as the original vdproj definitions and intent.

How to reproduce:
a) Download the attached VS2010 solution with a vdproj (7 zipped). It is a contrived example that illustrates the issues.
b) Upgrade to VS2013 with Advanced Installer available. Upgrade the vdproj to an aip project as part of the process.
c) The resulting project fails to build with the following style of error messages. The directories/dependencies have not been set up correctly.
Resources referred by the project are missing.
C:\Code\Torq\5473 Advanced Installer\DotNet\Experiments\AdvancedInstaller\Setup_advinst\ClassLibrary.dll
d) The AIP application folder references all the correct files but from the wrong place.
e) The AIP application folder has sub-folders for each c# project in sub-directories for no benefit. They refer to the correct Debug build file location but don't contain all referenced dlls for the primary output of a project.
f) The Release build files are not correctly referenced.

Regards,
Apolon.

[Daniel]

Hello Apolon and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.

d) The AIP application folder references all the correct files but from the wrong place.

I'm not sure why this happens. I've opened a ticket in our bug system tracking regarding this and we'll analyze your scenario. Also, it would be useful if you can send us a buildable sample (solution, project files, resource files, etc) which replicates the behavior so we can test and investigate it.

e) The AIP application folder has sub-folders for each c# project in sub-directories for no benefit. They refer to the correct Debug build file location but don't contain all referenced dlls for the primary output of a project.

This is our default behavior. In order to add the primary output of a project you can use the [Add Project Output] button from the bottom right section of the "Files and Folders" page. Also, in order to delete the above sub-folders, then you can use the [Edit in Advanced Installer] button, go to "Files and Folders" page in Advanced Installer and just delete the unwanted sub-folders.

f) The Release build files are not correctly referenced.

I'm not sure why this happens. Can you please use the "Redo import" context menu option of your "Setup_advinst.aip" file added in your solution and see if the behavior still persist?

All the best,
Daniel