This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Visual Studio 2015 Solution Explorer nodes do not show files for other projects
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 26, 2015
10:56 AM
Visual Studio 2015 Solution Explorer nodes do not show files for other projects
I have solutions in Visual Studio 2015 to which I have added InstallShield 2015 Express Setup projects. When I open the solutions, in Solution Explorer the branches for my projects ("Header Files", "Source Files", etc) do not open to display the files. This happens only when the solution includes a InstallShield Express Setup project. Behavior returns to normal if I remove the setup project from the solution.
Suggestions? Anything to troubleshoot?
I have contacted Microsoft tech support: they can reproduce the issue but so far have no solution.
Thanks,
Paul
Suggestions? Anything to troubleshoot?
I have contacted Microsoft tech support: they can reproduce the issue but so far have no solution.
Thanks,
Paul
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 27, 2015
12:48 PM
From Microsoft tech support:
I surprised that this is a bug, considering that InstallShield is built-in to VisualStudio 2015 as the preferred deployment solution.
-Paul
Subject: RE: [REG:115082013064013] Solution Explorer Filters Don't show file Initial Response
I have discussed this with our Escalation team and confirmed this to be a bug in VS2015. This scenario involving a third-party product may not have been tested before VS2015 release. I will raise a bug with Product Group. Please note that based on product groups priorities they may fix this in next update or can delay fix. I will update once I get any update from product team. Till then please use the alternative solution of unloading setup project temporarily. Thank you for pointing out this issue to Microsoft.
I surprised that this is a bug, considering that InstallShield is built-in to VisualStudio 2015 as the preferred deployment solution.
-Paul
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 26, 2015
05:51 PM
PaulLimburg wrote:
From Microsoft tech support:
I surprised that this is a bug, considering that InstallShield is built-in to VisualStudio 2015 as the preferred deployment solution.
-Paul
Hi There,
Have you heard any more about this?
Peter
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 27, 2015
04:16 PM
Response from Microsoft representative on 9/16/2015:
"The reason was found to be bug in VS2015 which caused file filters to work improperly when Installsheild setup project was one of the projects in a solution.
Solution suggested is to unload InstalSheild setup project temporarily while working with other projects. "
"In reference to case you have raised with Microsoft. (SR# 115082013064013 Solution Explorer Filters Don't show file). I got response from product team. They don’t have plan to fix this bug in upcoming update for Visual Studio. However, this bug will be fixed in a future release of Visual Studio and exact time cannot be committed as of now."
So nothing to do but wait now. -Paul
"The reason was found to be bug in VS2015 which caused file filters to work improperly when Installsheild setup project was one of the projects in a solution.
Solution suggested is to unload InstalSheild setup project temporarily while working with other projects. "
"In reference to case you have raised with Microsoft. (SR# 115082013064013 Solution Explorer Filters Don't show file). I got response from product team. They don’t have plan to fix this bug in upcoming update for Visual Studio. However, this bug will be fixed in a future release of Visual Studio and exact time cannot be committed as of now."
So nothing to do but wait now. -Paul
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)