I'm having trouble installing Visual Studio 2012. When I run the installer I get the message:
Microsoft .NET Framework required for Microsoft Visual Studio Professional 2012 setup
The first time I got this message, I clicked to install. It loaded some stuff but it didn't look like it installed anything. I ran the installer for VS 2012 again and I get the same message but now without any buttons to click on. Is there any solution to this?
What happened before
I had VS 2012 already up and working. I left it alone for quite a while until I decided I wanted to do some programming again. Starting the application resulted suddenly in an error:
Cannot find one or more components. Please reinstall the application.
After searching for a couple of hours I couldn't resolve the problem so I did as it asked and reinstalled VS, but I got the same error again. Then I tried to remove every single application VS installs as indicated by this list and any program that had a similar name. I also removed all .NET versions and C++ redistributables. Now I can't install VS anymore and some games and gadgets are now broken.
And I always, always, always forget the existence of system restore. I doubt my oldest system restore is old enough. This is going to be my last resort.
What I tried
Search for a .NET installation in the control panel, it's not present after clicking the install button on the prompt of the VS 2012 installer.
Reinstall .NET 4.5 using this installer. It installs correctly, but the problem persists.
Turning .NET 3.5.1 off from windows features and install it manually. This fails for an unknown reason (error code -2145124329, which seems undefined). Just turning it off doesn't work either.
Related
Afternoon all,
I had been using the Visual Studio 2022 Preview. Recently I decided to switch to the Release version. I uninstalled VS2022 Preview and installed the 2022 Community Release.
The install runs fine and completes with no issues. However when trying to run VS2022 It comes up with the error attached below.
From my talks with MS found at https://developercommunity.visualstudio.com/t/Unable-to-launch-VS-Comunity-2022-after/1596301?entry=myfeedback&viewtype=all It appears VS2022 Community should be running version 17.0 of the .Threading DLL. However no matter what I have tried it refuses to load.
I have run the uninstaller with -F. Re-installed several times.
Attempted to install 17.0 to the GAC but this does not change the outcome
As per the post on the developer community pretty much everything short of re-installing windows (Which I am 100% trying to avoid)
I ran the FusionLog viewer (Attached) and it looks like there is something re-binding this to the 17.1 .threading version however I know very little about how this works and where I might find a solution, Hence, I am here :). Although my post on the DeveloperCommunity is still active I'm hoping a resolution here maybe faster!
Thank you!
I have this error too, and its becouse you dont have defined startup project.
Right click on your startup project and choose "set as startup project".
Actually the above is incorrect, you can't even get to the startup screen.
The correct answer is you need to remove the V15 version of the dll from the GAC. Instructions from MS can be found here.
Trying to run an old project in Visual Studio 2015. It was created in 2012 or 2013, I cannot remember which. I have uninstalled both programs as I was running out of space, and i think that is what caused this. I get the following options:
And I do not want to change the target, so clicking on the second option brings me to https://www.microsoft.com/net/targeting which I can't seem to find anything there that remedies the situation. Is there a way around this without reinstalling the old version of Visual Studio again? Will that even fix my problem? Thank you.
Just Reinstall Visual Studio. When you uninstalled previous version it caused this problem.
You could try doing a repair reinstall of Visual Studio 2015.
Another point to consider is that Windows 7 (the oldest version of Windows still supported by Microsoft) includes a Windows Update for the .NET Framework v4.6.1 categorized as an "Important" update. I have not confirmed with Windows 8, but I suspect it, too, includes a similar update. Windows 10 comes with .NET 4.6 to start with. That means that any up-to-date supported machine today will be able to run apps targeting any .NET version up to and including 4.6. I recognize that there may be other reasons to continue targeting an older .NET version, but I bring this up just in case the concern is support on client workstations.
I recently, upgraded to Windows 10 and got Visual Studio 2015 Community hoping to build UWP apps and ASP.Net 5 apps. At first, I installed everything, but ended up skipping / canceling the Windows 8.1 / 10 mobile emulators (my PC can't even run them). After everything was installed, I went to create a new UWP app (C#), and got this error:
Next, I try the same thing, but with JavaScript. It works perfectly! on the same UAP 10.0.0.0 that is supposedly missing. The link it provides is completely useless (it sends me to http:/microsoft.com/en-us) -_-. Oddly, this only happens when I try to use C# or VB.Net, JavaScript UWP apps seem to work fine. What is going on here? Where can I find the real link to the SDK I need?
UPDATE
JavaScript UWP apps will be create just fine, but when I attempt to build, I get:
Error "10.0.0.0" is not a supported value forTargetPlatformVersion.
Please change it on the Project Property page. Test
C:\Program Files (x86) \MSBuild\Microsoft\VisualStudio\v14.\JavaScript\Microsoft.VisualStudio.JavaScript.UAP.targets
This is the download link for the standalone SDK, maybe reinstalling the sdk will fix the problem.
https://dev.windows.com/en-us/downloads/windows-10-sdk
Normally you don't always have to reinstall visual studio when something goes wrong because it takes a lot of time to reinstall again. From your question you skipped/cancel that feature, the first thing to do is go to the control panel and double click on visual studio under programs to Modify the software and enable those features.
In the case, visual studio was working properly before but due to some updates it stopped, go to control panel right click the visual studio version you have under programs to repair.
If the above doesn't work try to reinstall it again. I hope this helps.
Recently, I needed to refresh my Windows 8.1 PC, and now that I have finally finished getting all of my programs reinstalled and everything is back to normal, I am ready to finish work on my Windows 8.1 app, but I am having an issue with compiling my apps. Every time I try to compile, I get the following error.
Now normally when I need to refresh my developer licesnse, Visual Studio tells me, but this time I didn't get any prompt at all, and that is the error that I got when trying to compile. How can I fix this? I am installing updates for Visual STudio at the moment, and I am hoping that doing so will somehow magically fix the problem, but I am also aware that it probably won't.
EDIT: Now that I have updated, the message has been shortened to "Can't resolve Windows.metadata."
For some reason, even though the Windows 8.1 SDK is supposed to be installed with Visual Studio Ultimate 2013, it wasn't for me. I was able to find the Windows 8.1 SDK by Googling it, and it came up as the top result. I installed it, and suddenly all of my errors went away and Visual Studio started recognizing them as legitimate Windows 8.1 app code.
I have a C# console app in Visual Studio 2010 that I can run just fine. When I attempt to run the process in debug mode, I am presented with the following error:
I have tried searching for any information, but I haven't been able to find anything. Can anyone provide clues as to why I can't run this with the debugger?
EDIT: I should clarify that I have been able to successfully debug a console app previously, this is a new situation.
From what I can tell when I'm able to reproduce this error, it is caused by being in the middle of installing Windows updates. So, running updates, then postponing a reboot, then attempting to debug code is what was putting me in this broken state.
I had this issue once and it was caused by an pending Windows Update on the Server where the process was running, which I wanted to attach.
I encountered the same issue. It happened to me when I attempted to attach to a process for debugging purposes. At the time I had postponed a pending windows update.
Everything started working fine after I restarted my computer and allowed the update to take place.
Additional notes: I had recently updated to Visual Studio 2010 Ultimate and installed its Service Pack 1.
I had this when I installed .NET 4.6 for Visual Studio 2013.
In this particular case, restarting Visual Studio 2013 solved the problem.
I have finally solved this!
It seemed to have happened after I updated my Windows 7. One of my files must have been out of date.
The fix: Install VS 2010 Service Pack 1
Worked correctly right after I installed. Hitting breakpoints and everything!
Hope this works for you too!
I also updated to Service Pack 1, and made sure Windows updates were up to date, but I was still having the same issue:
"The Version of CLR.dll in the target does not match the one mscordacwks.dll was built for."
Microsoft closed this issue on connect.microsoft.com as not reproducible... Unforgivable, irresponsible support system!!
But on social.msdn.com I was directed to upgrade through this link, and this has resolved the problem in my machine ( Win7,VS2010,target 4.0)
Hope it helps.
Simply. Restarting Visual Studio solved the problem in my case.
I had VS 2010 SP1 for ages and had rebooted many times. There wasn't any windows update in progress either. I closed all my VS 2010 IDEs and then opened them, and the problem was gone.
This happens, when you do a WINDOWS UPDATE and haven't rebooted your system and the update isn't compatible with VISUAL STUDIO. So in order to solve this, just do an update on VISUAL STUDIO to latest. That should FIX it
I had this weird issue after installing .net framework 4.5, when using .net 4 for my project.
updating VS 2010 service pack didn't solve this, only removal of .net 4.5 and 4, and then reinstalling .net 4 only.
I have VS2013 on Win7 and restarting VS worked for me. Seems it is a VS/CLR bug.