When I try to delete an application file from the Application Files tab of an Install Project in Visual Studio 2013 (using InstallShield LE 2015) the file disappears from the list but all the Visual Studio menus are frozen and I cannot access any tab except the Install project. I have to close Visual Studio 2013 from Task Manager and when I re-open it the deleted file is still present.
MS only provide support for Visual Studio 2017 and newer and I'm reluctant to upgrade.
Related
I am trying to build a VS 2017 solution which includes a Visual Studio Installer Project with the just released Visual Studio Pro 2019. Of course, when I tried to open the solution I got an error because there was not Visual Studio Installer project type in VS 2019. And, I cant find a place to load it from.
How do I add a Visual Studio Installer Project type in the released version of VS 2019?
Install the addin in Visual Studio 2019:
This extension provides the same functionality that currently exists
in Visual Studio 2015 for Visual Studio Installer projects. To use
this extension, you can either open the Extensions and Updates dialog,
select the online node, and search for "Visual Studio Installer
Projects Extension," or you can download directly from this page.
This extension is designed to work with Visual Studio 2017 and
Visual Studio 2019.
Got a big problem with the Visual Studio 2017 Installer Projects Extension for Visual Studio 2017 Professional. I added a Visual Studio Installer Setup project to a solution and set it up the way it's basically supposed to be done (Primary Output in the Application Folder and an icon in the Desktop Folder is all that was needed). Then I right-clicked on the Setup project, clicked "Build" and then I get this:
Please wait while Windows configures Microsoft Visual Studio Professional 2013.
And then it stalls indefinitely. I have to close Visual Studio in Task Manager to stop everything. What's more, I'm Visual Studio Professional 2017, not 2013. I used to have Visual Studio 2013 Ultimate, but I uninstalled it. What could possibly be causing the confusion?
It appears that you have also got Visual Studio 2013 installed, and that there is as conflict between 2013 and 2017 because that message is a Windows Installer repair of VS 2013. Something is happening during your build that requires the VS 2013 installation to be repaired. The Windows Event Log (Application) will have an MsiInstaller log entry saying which component appears to be broken. If you post that information there may be a clue to the problem. If you (for example) have manually removed anything that may belong to the VS 2013 installed product then that would cause the same kind of problem.
You have this similar problem:
Rebuilding Visual Studio Installer project, launches Visual Studio 2013 seetup
Visual Studio 2015 msi build initiates another installation
When you say it stalls indefinitely, I would expect it to ask for the Visual Studio 2013 install image so that it can repair it. If you go to Programs&Features and manually repair VS 2013 it might fix the problem.
I also had Visual Studio 2013 installed as mentioned by #PhilDW.
Navigating to Event Viewer → Windows Logs → Application I found loads of warnings:
Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature 'Visual_Studio_Professional_x86_enu', component '{E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}' failed. The resource 'C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\' does not exist.
The key here being that the folder C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\ did not exist thanks to an answer in the first link provided by #PhilDW.
Created the missing final folder URTInstallPath_GAC in the path mentioned and the installers now build really fast whereas before they used to take forever (sometimes literally!).
I have a visual studio 2008 project if I open it with 2015 visual studio can I open it again with visual studio 2008?
No, the project file will be upgraded and cannot be opened with the previous version of Visual Studio.
However Visual Studio will create a backup of the old project file and other files in your project that will be modified on upgrade.
Using this backup is your only chance to open the project with an earlier version of Visual Studio again.
We have MS Reporting Services .sln files that we open with Visual Studio 2005. We are moving to Visual Studio 2015. When trying to open the .sln files with Visual Studio 2015 we get the following:
We choose to upgrade and get the upgrade report that reports it was successful:
However when trying to open the .sln file after the successful upgrade was reported, it cannot open it.
Any ideas how I can get these files onto the latest version?
Reporting Services is not available in Visual Studio 2015 SSDT yet - it is still in Beta, as noted here hence your issues.
I was developing a solution for Windows Phone 7 on my system using Visual Studio 2012. I installed Visual Studio 2013 and opened the solution with it. I found that Visual Studio 2013 won't let me build a Windows Phone 7 application, so I wanted to re-open the solution in Visual Studio 2012.
Now Visual Studio 2012 shows me the following error message:
This project is incompatible with the current edition of Visual Studio
What do I need to do to 'undo' the changes made to my project in the upgrade process so that I can continue working in the older version of Visual Studio to finish my project?
Visual Studio 2013 upgrades the project to the Windows Phone 8 SDK, and that is not compatible with Visual Studio 2012. If you are using a form of Source Control (Visual Studio Online, GitHub) you should roll back to the previous version. If not, Visual Studio (by default) creates a _backup folder under your solution where it will backup any files modified in the conversion process. Use these to return the project to its pre-visualstudio-2013-state.