Install shield LE in visual studio 2015 not working - c#

I have visual studio 2015 and InstallShield LE.
Everything was fine and suddenly I get "Incompatible" problem. "The application is not installed".
I was trying to reinstall the installsheild and it didnt help.
when i do right click on the project i click on "Reload project" and get this message:
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- Setup, "C:...\Visual Studio 2015\Projects\TestProject\Setup\Setup.isproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.

Probably not what you want to hear, but do yourself a favour and uninstall it as fast as possible! It's an awful piece of software, full of bugs, pathetic or non-existent support, and a steep price if you are dumb enough to want to buy it!
This is the voice of bitter experience, backed up the opinions of a lot of other people who found the same thing.
I use Inno Setup, which is free, simple, is supported and works really nicely. Since discovering it, I've not had any problems.

Related

"C# 2017 compiler could not be created" error message while opening project

I've Visual Studio 2017 community edition. I have a C# project created using Visual Studio 2015. When I try to open the project in VS 2017 I get an error message prompt:
--------------------- Microsoft Visual Studio
Project 'dataStructureInCSharp' could not be opened because the Visual C# 2017 compiler could not be created.
Please re-install Visual Studio.
--------------------------- OK
I'm trying to obtain help if anyone else has faced similar issue. I feel going the uninstall and then reinstall route is very costly for me and would try that option last if I've got no other resort.
What I've done so far :
Tried starting visual studio with administrative privileges
But problem remained same.
I tried creating a new console project solution from scratch but in that case I get very same error and an additional error error also shown below:
System Environment: Windows 7 Ultimate Service Pack 1
You can try to close all VS 2017 instances and delete the folder %localappdata%\Microsoft\VisualStudio\15.0_xxxx\ComponentModelCache, then open VS to create a new Console project.
Or
please re-run the VS 2017 installer as administrator, click the icon beside ‘Launch’ button and choose ‘Repair’ to repair as shown below:
Just to brief the history of my problem, I had first installed Visual Studio(VS) 2017 community when it was in RC stage. This was first time when I saw the workload based UI of visual studio installation. Initially I simply chose .Net desktop development workload to get started as I was interested in creating only console applications to get my hands dirty.
Initially it was all working well. One fine day I added all other workloads I was interested in namely Universal Windows Platform Development, Azure Development, ASP.NET and web development,Node.js development, and Mobile development with .Net. I'm not sure if there any of the specific workloads to be blamed for the issue I've posted.
Just to avoid the case if RC and RTM release builds might not have messed up my entire environment, I simply uninstalled the entire stuff, rebooted my machine and installed it again from scratch from latest RTM release for Visual Studio Community.
I would strongly recommend that you first try possible solutions suggested by #Sara-MSFT before doing clean reinstall just in case if it works. It can save you couple of hours required in whole reinstallation process if it works.

Microsoft.VisualStudio.TestTools.LoadTesting cannot be found after upgrading to Visual Studio 2017

Having recently updated from Visual Studio 2015 to 2017, I ran into a referencing issue where performance testing namespaces and dll references seem to have disappeared.
I finally figured out what had caused it, but figured a few people may run into this, so I will also be including the solution.
To solve this you have to first load up visual studio installer (It's installed alongside Visual Studio 2017) and click on modify.
Then click on Individual components and select the items shown in this image:
Microsoft test manager
testing tools core features
Web performance and load testing tools
Make sure you restart VS 2017 after installing these, I had to do a clean and rebuild as well.

Visual Studio stopped supporting my projects

I have Visual Studio 2013 Ultimate. Today when I opened it, it didn't load any of my solution's projects. Error message:
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- ETL_<Project name>, "<Project path></Project>.csproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
- <Project name></Project>, "<Project path></Project>.sln"
These projects are of types Class Library and Console Application. If I try to create a new project, these types are listed, but when I create it I get message <Project path> cannot be opened because its project type (.csproj is not supported by this version of the application. To open it, please use a version that supports this type of project..
So, Visual Studio is telling me it doesn't support a project it just created?! GJ M$!!
Unfortunately I was unable to solve this. I ended up uninstalling VS Ultimate. Now I use VS Express for Desktop, and it works with my old projects.
My assumption is that something on Windows broke some part of VS. I should have tried to uninstall and reinstall it but didn't have the opportunity.
I have the same thing in a Hyper-V VM. After repair did not work, I deinstalled and reinstalled VS 2017. Same thing.
In the host I can still open the same project with VS, so it is not the project, but the VS install that has a problem.
It puts this in the migration log:
src\DTOWEB\project.json: Failed to migrate XProj project DTOWEB. Could not find project.json at C:\DTOWeb\DTOWEB7\src\DTOWEB\project.json.
I have a second VM that is x86 iso x64, and it can open the project without problems. So again, my conclusion is there is nothing wrong with the project.

GIT integration to show method history in Visual Studio

We use GitHub for our source code repository and Visual Studio for our development (C#). I downgraded from Visual Studio Professional (Trial) to Community Edition and somehow lost the GIT method history I had above each method signature. I've since reinstalled Pro version and still can't see it. This method history was very useful and looked something like:
Last Update 8/1/2015, 3 authors.
Void DoSomething() {}
Clicking on the status line would bring up things like "compare to previous version", history etc.
I'm not sure if it was a feature of Visual Studio Professional (doubtful) or one of the git extensions I possibly installed (see Tools->Extensions and Updates) or something else. I'm new to using GIT/GitHub, especially with Visual Studio and would appreciate some help. My specific questions
1. How do I get history/last author/etc for each method (not file)? Does it work under Professional and Community
2. What are some good Git Tools to install in Visual Studio to see changes/history, etc.? I'm using the command line to commit/push etc., but am not opposed to doing this from Visual Studio if it makes sense.
Thanks,
Dave
What you initially refer to is a feature of Visual Studio called CodeLens. It's available in the Professional and Enterprise editions of Visual Studio 2015, but not available in the Community edition.
To try and resolve this not working, I would:
Make sure you are actually running Visual Studio 2015 Professional edition, and not the Community edition.
Make sure you have Git for Windows installed.
In addition to the excellent answer by Steve (which I'm marking as answer), I'll note that I had additional problems (after installing Git for Windows).
I got errors at startup and didn't see the method info. The errors were:
The 'GitCollaborationPackage' package did not load correctly.
The 'FileIndicatorPackage' package did not load correctly.
The fix was to rename the componentmodelcache directory under C:\Users\cshar\AppData\Local\Microsoft\VisualStudio\14.0
See:
Packages not loading after installing visual studio 2015 RTM
or
http://kuebiko.blogspot.ru/2013/07/setsite-failed-for-package.html

This project(Visual Studio 2012 express) is incompatible with the current version of Visual Studio 2013 express

Am doing a back end project in C# in Visual Studio. My team mate had done it using Visual Studio 2012 express and everything seems to work there. But when i used git to clone it to my system where am using Visual Studio 2013 express, one part of the project says its incompatible with the current version of VS. I could clean and build the project, but was unable to run the project. I searched and found that one solution is to go to Programs and features, select VS, right click,select repair. But even after doing this, the problem persists. Is there any work around?
When I was learning ASP.NET MVC by Informit tutorials I was in the very similar situation. I downloaded the sample sources that was created in VS2013 but had VS2015 installed. It was some kind of bug \ magic, but VS didn't recognized some libraries in VS2015 even they were installed. What is more strange is the fact that when I decided to totally rewrite the project line by line it worked!
Of course, I tried to clean, rebuild, reinstall NuGet packages.
So, if you have an access to sources *.cs, then just try to create new project and copy-paste code.

Categories