I installed visual studio 2010 ultimate version and everything worked perfectly fine and my development environment worked well.
However I had a recent problem in which every piece of code gives me the error about header files not being found like iostream stdio.h conio.h etc.
I pinpointed the problem to it being caused by me uninstalling visual C++ express 2010 that I had installed previous to the installation of the visual studio 2010.
I tried to completely uninstall and install Visual Studio but it seems some files are always left that I cannot track. I used this link and the answer marked right over there to no avails. Can anybody advise me how to get it right without formatting the whole system.
Link to Question
I seem to have solved the problem using another answer on Stack overflow.
The answer points to this link from Microsoft Connect.
The steps I followed to solve the problem are listed below.
Uninstalled visual c++ using the following vs2010_uninstall tool from Microsoft and used the switches /full /netfx while uninstalling(use command line instead of double click) as follows: VS2010_Uninstall-RTM.ENU.exe /full /netfx
Uninstall Visual Studio Service Pack 1 if its installed
Start Registry Editor in Windows: Win+R type Regedit to open Registry Editor. Do remember to backup your registries and create a restore point.
Search for the key named PaddedVersion
If the search key is found and look at keys ending with VisualStudio\10.0\VC\Libraries or VisualStudio\10.0_Config\VC\Libraries
Delete all keys and subkeys under the VisualStudio\10.0\VC\Libraries or if that doesn't work delete all keys and subkeys under VisualStudio\10.0 or VisualStudio\10.0_Config. The catch here is that all keys must be deleted regardless of their prefix to the above mentioned string as HKEY_LOCAL_MACHINE or HKEY_USERS etc. It has to be deleted in all cases.
Note the PaddedVersion just helps you in finding all such keys.
Once done restart(not compulsory but better if you do it) Windows. Now you are ready to begin re-installation of your version of Visual Studio 2010.
Hope it helps all who are having such a problem..
After trying this, and countless other solutions over the past six months, the solution that worked for me was as follows:
1) Right Click project
2) Select Properties
3) Select Configuration Properties > General > Platform Toolset
4) When you get to Platform Toolset, click on the v110 value which will be in the right column. You will see a drop down appear which will allow you to select v90, v100, or inherit. Of course, v100 is the correct answer. Once v100 is selected, I don't believe you can back to v110 from within VS 2010. You would have to once again open in in VS 2012 to move it back to v110.
Related
At the start I'd like to note that I've spent some time researching this issue and suggested solutions for similar questions like this one didn't help me.
Problem background
I need to migrate a Firebreath plugin project (which I haven't worked on previously) from PC_1 to PC_2.
As far as I'm aware the project was started on PC_1 on Visual Studio 2010 and later moved to Visual Studio 2013 Pro. There's one solution consisting of 19 projects. I have an instruction which says that in order to get the plugin installer I should first Build project_x and after that Build project_y_WiXInstall. Both steps work without any issues on this machine.
Then there's PC_2 which had Visual Studio 2015 Community installed before I started working on it. I've removed it, installed Visual Studio 2013 Pro (version 12.0.21005.1 REL - exactly the same as on PC_1), moved all of the needed files and I'm trying to get rid of all of the compilation errors. So far I figured out I had to install Cmake 2.8, Windows Driver Toolkit 7.1 and manually override an incorrect VCTargetsPath MSBuild variable
Problem description
Currently when I try to compile the project on the new machine I get these two errors (this is an image link since I can't embed images yet on this account). I'm not sure what's going on with the first error message since it looks incomplete and the file CUSTOMBUILD doesn't exist, but I'm not bothered by it too much since the previous compilation error I fixed also had a similar "artifact" as the first error and it disappeared after fixing the second one.
The covered part of the second error message is the project path. The error origin (Microsoft.Cpp.Platform.targets file, line 64) looks like this:
<!-- Error out if toolset does not exists in Visual Studio 2010 or 2012 -->
<VCMessage Code="MSB8020" Type="Error" Arguments="$(_CurrentPlatformToolsetShortName);$(PlatformToolset)" Condition="'$(ToolsetTargetsFound)' != 'true'" />
What didn't help
The error description suggests using an Upgrade Solution... option, but there's no such thing when I right-click the solution
As an accepted answer for the question I've posted at the start of my post suggests, I've checked the Properties of all 19 of my projects (including the project ZERO_CHECK) but their Platform Toolset is already set to Visual Studio 2013 (v120).
I've also tried changing the Platform Toolset to inherit from parent or project defaults for all of the projects. This resulted in it switching to Visual Studio 2010 (v100) (not installed) and after that I've right-clicked on the projects and chose Upgrade VC++ compiler and libraries. After this the Platform Toolset was back to the Visual Studio 2013 (v120) but it didn't help with the compilation error.
As a NON-accepted answer for the question I've posted at the start of my post suggests, I've tried searching for all of the occurrences of 10.0 and V100 in all of my .vcxproj files to replace them but I haven't found any occurrences of them.
[EDIT]
I just got an idea to try building the project with MSBuild from the command line. There's a bit more info compared to errors inside Visual Studio, so maybe it will help with resolving the issue: https://pastebin.com/JhN3dXM3
So the thing you're missing here is that FireBreath projects are built using CMake -- the actual contents of the build directory should always be completely temporary and never stored in source control. To build the project on a new computer you need to run the prep command again from scratch.
If the previous maintainer changed the build files manually and/or migrated it to a newer version of visual studio without using cmake to do it then they did some very ugly things and all bets are off... good luck.
This is why all the firebreath documentation (I wrote most of it) strongly urges that the build directory be transient and you always do project file updates in cmake.
Hope that helps!
I have been using Vs 2017 for several months on dev machine. This fine morning says setup incomplete. Am I missing something?
In this case you need to go to Control Panel => Programs and Features and choose Visual Studio and update it.
VS 2017 (15.6.6) was fine for me on Friday 6/1/18 on Windows 10, but same issue as OP today after a restart.
As suggested by the dialog and Retired Ninja, I ran the Visual Studio Installer (to 15.7.3 after updating VS Installer) and that fixed it.
Note that the 15.7.3 update was a 7.73 GB download. Your download size may vary.
This has happened to me for the last 3 upgrades in Visual Studio Enterprise 2017 (now again on upgrade to 15.9.21).
The fastest fix (and I'm not sure why) is simple and doesn't bomb your settings or take for ever.
In the Visual Studio Installer, click on Modify.
Click "Modify" on the bottom right corner.
Yes it says "Total space required 0 KB".
Yes you didn't really change anything.
It will then act like it is downloading something. (not sure what)
It will then act like it is installing something. (again, not sure what)
Open Visual Studio 2017 and it works.
Hope this helps.
If you have an offline installation like me and can't simply re-run the Visual Studio Installer you can edit devenv.isolation.ini and change the last line to read SetupFinished=true. It will detect your trickery and complain, but at least it will launch again.
Edit: I ended up getting the Visual Studio Installer to fix the issue after choosing the "Download then Install" option. Maybe I was too impatient when I initially stopped the update? My above answer is useful when you need to get work done that isn't affected by the broken features, but you will likely encounter problems later on.
just had the same problem (without any reason with) vs 2019 prof, after googling and reading on that topic, just went to vsix, looked for some individual component to install/uninstall, randomly picked cloud explorer, uninstalled it and some dependent components and VS 2019 prof started normally
decided to leave this here. may be it helps somebody
Solved: I did following steps, run the visual studio and it works for me.
In my case visual studio was working fine , I just restarted the PC, this popup was keep coming when I try to open visual studio.(in my case I was using VS 2019)
Go to this path "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE"
Open devenv.isolation.ini, set SetupFinished=true and save.
Now open visual studio.
Cheers!
In my case did following steps:
Clear temp files (you can %temp% in run command and Shift+Delete files)
Restart your computer
Open visual studio it will work properly.
Update: Faced problem again after couple of days, This time I go to C:\Program Files (x86)\Microsoft Visual Studio\Installer.
Click on retry.
Select one more feature which I had already installed on my Visual Studio
Click on modified and after installation it worked again.
This happened to me after I canceled a plugin update.
I solved by going to this site that has the latest update of Visual Studio.
https://learn.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes
I downloaded and upgraded it.
After that, Visual Studio worked.
If your VS is already upgraded, there´s an option to "repair" on the installer.
For this problem, goto uninstall screen in control panel right-click visual studio and select option change, Installer page will open now, In that window without changing anything click modify. it will solve the problem. I'm using VS Professional 2017
I got the same error today morning. This is what I did:
I ran the visual studio installer then I clicked on Modify.
The installer was showing 0KB Required. I continued and then it downloaded and installed. (Not sure what).
After that installation, it was able to launch.
I hope it works for you as well.
I was using Vs 2019 professional 16.6 and happened to me this issue one morning. I modified the installation by adding Azure Development tools even though I was not using it. This fixed the issue.
I just updated to 15.9.24 and I got this yet again, as I have my resolution above, and Visual Studio 2019 seems to be a lot better with avoid this issue. The installer for 2019 you do have to change something and do the modification, 2017 you don't have to change anything.
I reported this issue through Developer Community:
Setup not complete since 15.9.21
I don't know why but sometimes its buggy
it's up to date but after launch visual studio this error prompted !
you have to click modify in vs installer and just modify it.
its not going to download anything.
after a moment launch vs and enjoy :)
For VS2022, WIN11:
Control Panel > Programs > Programs and Features > Microsoft Visual Studio Installer
Then, click on Change and resume the previous process.
I use ResXFileCodeGeneratorEx for generating ids. This was working till the time I used Visual Studio 2010 IDE but it is not working for Visual Studio 2017.
Please help for the same.
Extension for Visual Studio 2019 can be found here
Extension for Visual Studio 2017 can be found here
The deleted answer to this question pointed to the location of a newly built ResXFileCodeGeneratorEx but was deleted because it only contained a single link and no context. I'm not the original answerer, but figured that it may still be valuable to have this information:
It seems to have been renamed to ResXCodeFileGeneratorEx, and if you search through the menu in Visual Studio under Tools > Extension and Updates, you need to search for "Extended Strongly Typed Resource Generator".
However, the internal name is still the same, so the Custom Tool action should remain ResXFileCodeGeneratorEx.
I'm not aware whether or not it works on Visual Studio 2019, but since the original source is still around, it oughtn't be too hard to resolve that yourself if you need it.
To install it, simply doubleclick the VSIX file, it will popup with the VS Version Instance Selector, where you can select to which of your VS 2017 instances (pro, community, preview) you want to install the extension to.
I am facing problem, I want to write c++ code in visual studio 2015, but I can't create c++ project because there is no c++ template in the New Project window.
I am creating new project in this way
File > New > Project > Visual C++
but there is no c++ template. Please help
The VS2015 installer does not install C++ by default.
Since you already have Visual Studio installed, you can modify the existing install.
On Control Panel->Programs and Features (or run appwiz.cpl) find and run the Installer for Visual Studio 2015.
Wait for Installer dialog to load.
Click the Modify button on the bottom of the installer dialog.
On the Features Tab, expand Programming Languages.
Select Visual C++.
Click the UPDATE button on the bottom right.
That should do it. You may have to insert the install media or suffer through a download, but these days Windows caches the installer info so everything needed may already be present on your system.
Go to the online menu (it's below Recent and Installed. There you'll be able to download C++ templates and samples. See this MSDN article which describes it in greater details.
While most users will be unblocked by the accepted solution, there is another scenario where Visual C++ is not working as intended for VS2015.
I was installing both VS2015 and VS2017 on the same system on the same day. Long story short, I got this person's problem.
From the link:
I am also running into this -- but in my case, I also installed full
VS2015 Pro. It shows that the VC++ common tools are installed, but
they are not on disk in the usual location, they seem to be in the
MSVS/Shared folder (Program Files (x86)/Microsoft Visual
Studio/Shared/14.0/VC/bin/cl.exe reports version 19.00.124218.2).
Uninstalling VS2015 removes these, and reinstalling puts them back in
Shared.
For me at least, it goes worse than just the batch files -- I can't
actually create any C++ projects. Trying to create one just causes the
"New Project" window to pop up again; no error, no warning.
No amount of uninstalling components from both 2015 or 2017 got me
into a usable state (Shared\14.0\VC still persisted as the install
dir, I couldn't find what component was keeping those tools on-disk
and preventing them from being removed). I ended up just copying the
contents of "Microsoft Visual Studio/Shared/14.0" into the "Microsoft
Visual Studio 14.0" folder -- a gross hammer, and VS2015 still can't
create C++ projects, but it got me unstuck, and existing build systems
started finding tools again.
VS team -- I totally get the goals of the layout change, and I love
what you guys are doing with VS overall. But please treat this as a
major bug; you can't decide to permanently change the location of
build tools that have been in one place for multiple years, as it will
break many, many existing build systems. At best, install them in both
locations; let VS2015 manage the "Visual Studio 14.0/VC" dir like it
always has, and let VS2017 manage the Shared/14.0 dir (via the "VS2015
C++ build tools" package). They should be unrelated.
Fix:
Uninstall all copies of Visual Studio
If you have frameworks that can install copies or partial copies of Visual Studio, or rely on them, consider uninstalling them too. For me, this was a couple versions of Qt.
Nuke C:\Windows\Temp and %temp%
Nuke anything visual studio related in C:\PROGRA~1,2,3, %appdata%, and %localappdata%
Reboot
Install the oldest version of Visual Studio you want to use first
Try to build a C++ Win32 console app with that version
If you can do that, you're unblocked. Otherwise, yikes! I don't know what to do next short of a full registry deep-dive keyword purge or a re-install of Windows. With an SSD, the latter is probably faster TBH.
I have Windows 7 64-bit with Microsoft Visual Studio 2010 and subsequent installation of SP1.
If I open up Control Panels | Programs and Features, I see 3 entries for Visual Studio 2010, the third being one ADO.Net.
I tried to uninstall SP1 first and somehow that failed. It asked for the Visual Studio 2010 setup disk, which I put in. Sadly, after the completion, SP1 stayed in the Programs and Features list.
I tried uninstalling VS2010, which uninstalled nicely, but left the entry for SP1. I tried uninstalling SP1, but got a message that I had to have VS2010 installed, so I bit my lip, shoveled down my irritation, and reinstalled VS2010. I received only one option to install SP1, which I did. I guess you can consider that a reapply.
A refresh of Programs and Features showed once again 3 entries. I was able to uninstall SP1, at least the option was there and I was able to complete the uninstall. I kept the VS2010 disk in the CD tray. Sadly, closing Control Panel Programs and Features (CPPF subsequently) and reopening it, nicely showed Microsoft's bug invested SP1. Selecting to uninstall/change the entry results in a dialog to install SP1.
It appears that SP1 might be gone in part, but obviously not entirely. The entry, the executable/DLL tied to that entry is nicely there.
How do I remove/cleanup/delete/nuke VS2010 SP1 inclusive of CPPF and any other trash that it installed?
I just ran the web installer for VS2010 SP 1 with the following parameters. That forced it to uninstall and got me past the blocking issue:
VS10sp1-KB983509.exe /uninstall /force
I tried James solution above but it still didn't work and kept requiring the installation CD.
After further search I found this solution that worked for me:
Microsoft tool to remove Visual Studio 2010
As life moves on, I chose a chose maybe not the best solution, but it is a solution, so here is what I did.
I found an article, which talked about removing the entry from Control Panel | Programs and Features. http://www.roelvanlisdonk.nl/?p=1179. I then did other steps.
First from the link as I have a Windows 7 64-bit system, I went to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall
in the registry. There were two locations, one the obvious with the name completely spelled out and the other with the DisplayName property set to the product name as part of a GUIID. I deleted both entries. The main entry with the nice name as the key was the one that deletes the program ID entry from the list.
I noticed that several products share the same InstallSource. That is bizarro (Smallville rocks and sadly ended), all in the C:\Windows\TEMP folder. As the actual setup program is under ProgramData folder, I am not sure what the TEMP folder entries do.
I deleted the ProgramData portion but left the C:\Windows\TEMP, although I am still thinking of cleaning that up, just am cautious.
I then deleted all other VS2010 components leaving the runtime. By the way, do not forget to delete Premptive's expensive and end user install based pricing product. That is further up (name sort ascending) under Dotfuscator...
That more or less cleaned things up. I am not sure what uses the VS2010 runtime, so I am leaving that. I assume that is what is installed at the VS2010 folder.
A side comment: I still find it strange that Microsoft in the registry follows a ...\Software\Microsoft\ entry. They do not follow that anywhere else. Why there?
Details:
In the registry, the information was:
{5AB7D739-1735-3A9E-BE73-C43507CB4E6F}
Uninstall String: MsiExec.exe /X{5AB7D739-1735-3A9E-BE73-C43507CB4E6F}
Install Source: C:\Windows\TEMP\Microsoft Visual Studio 2010 Service Pack 1_10.0.40219\
InstallLocation: C:\ProgramData\VS\vs10sp1\SetupCache\
Uninstall Path: C:\ProgramData\VS\vs10sp1\SetupCache\
Uinstall String: C:\ProgramData\VS\vs10sp1\SetupCache\Setup.exe
Shared products using C:\Windows\TEMP...40219 folder:
Microsoft SQL Server 2008 R2 Data-Tier Application Framework
Microsoft SQL Server 2008 R2 Data-Tier Application Project
Microsoft SQL Server 2008 R2 Management Objects
Microsoft SQL Server 2008 R2 Transact-SQL Language Service
Microsoft SQL Server System CLR Types
Microsoft Visual C++ 2010 x86 Runtime - 10.0.40219
Microsoft Visual F# 2.0 Runtime
Paths used by other products:
C:\Windows\TEMP\Microsoft Visual Studio 2010 Service Pack 1_10.0.40219\
C:\Windows\TEMP\Microsoft Visual Studio 2010 Service Pack 1_10.0.40219\Dotfuscator\
2 of several keys that share the same C:\Windows\TEMP folder entry (InstallSource):
InstallSource
{09C52940-A4D1-4409-A7CC-1AAE630CF578}
{1AA5BD63-6614-44B2-88A7-605191EDB835}
This answer on the MSDN forum explains a sequence for manual removal, but more importantly it also links to a Microsoft FixIt VS2010 Uninstall Utility which was the only way I was able to get rid of SP1.
None of the solutions here worked for me to remove VS 2010 SP1.
The visual stiduio 2010 uninstall utility worked nicely to remove everything but VS 2010 SP1.
to remove SP1 I went to the setup cache and ran setup as follows:
C:\ProgramData\VS\vs10sp1\SetupCache>setup /uninstall /force