Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.
- The Visual Studio Team

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2529927) KB2529927
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2529927.

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2548139) KB2548139
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2548139.

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2549864) KB2549864
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2549864.

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2565057) KB2565057
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2565057.

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2635973) KB2635973
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2635973.

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2736182) KB2736182
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2736182.

Microsoft Visual Studio 2010 Professional - ENU Service Pack 1 (KB983509) KB983509
This service pack is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this service pack will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/983509.

Security Update for Microsoft Visual Studio 2010 Professional - ENU (KB2645410) KB2645410
This security update is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this security update will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2645410.

Given that and the fact that InstallShield is far less robust that Visual Studio itself, I think it was a really bad idea to stop supporting legacy projects...

And not mentionning that it take far more time to create a workable setup with their limited products as it has a lot of issues like those mentionned above and the fact that the setup is not valid (missing files, files outputted to the wrong folder...)

By the way, I have an application with a bunch of C++ and C# projects where some C++ projects are managed while other are in mixed mode. And I eventually want to make my application works with "any CPU" in the future so it is important that in such a case, it works as expected on 64 bits system.

When we add an InstallShield Limited Edition setup project in a solution, Visual Studio will often stop responding and become much more slower.

And by the way, if such a project is loaded when we open a solution, Visual Studio will crash thus we have to rename the folder so that next time we start Visual Studio the project won't be load automatically (and then load it manually).

And since Visual Studio stop responding much more often when we have such project in a solution, we have to restart Visual Studio much more often (and have to do the manual step to avoid a crash on opening as it look like InstallShield try to uses other projects before they are loaded)

When such a project is loaded, part of Visual Studio often stop responding. In particular, solution explorer and editors are much affected to the point were it almost unusable.

Before I had such project to my solution, I never have such a degradation of performance.