How to force install of earlier .net frameworks - visual-studio

I am running Windows 10. I tried to open a solution in Visual Studio, and could not do so without upgrading that solution to .NET Framework 4.8. I don't want to do that, as it is a team project.
I tried to install 4.6.2, which is what it wanted, but could not - got the "a newer version is already installed). So, searching for a way to get it to install, I found a suggestion of uninstalling other .NET framework versions. I uninstalled 4.8 in the Windows Features, although it still seems to be there. I uninstalled 4.5.1 and 4.5.2 from Control Panel.
Now when I log into my computer, I am bombarded with errors that 4.0.30319 is missing, 4.5 is missing, and so forth. I tried going to Visual Studio Installer, to see if I could install them from there, but 4.5 is required by VS Installer. 4.0 will not install. 4.5.1 and 4.5.2 will install. 4.8 installed. But the software isn't detecting any of them.
I installed the 4.5.1 devpack. 4.5.2 devpack. 4.8 devpack. None of these have allowed me to run the VS installer. I can see 4.5.1 in the control panel, so it's there. 4.8 is checked in Windows features, so it is there. But the VS Installer tells me that it needs 4.5 and can't find it.
Does anyone have suggestions as to how to get my VS Installer at least working? From there, maybe I can try individual component versions. Even the VS Installer Setup application won't run, needing 4.5, and the same with attempting to uninstall the VS installer.

Well, I've tried everything I can find online. Tried a .NET Framework Repair Tool (https://learn.microsoft.com/en-us/dotnet/framework/install/repair) which didn't repair anything. Tried installing older versions of VS hoping that they'd "properly" install the necessary .NET Frameworks, but the installs all hung (tried 2017, 2015, 2012, and 2010, since the frameworks that can't be found go back to 4.0.30319). Those were a flop. Can't tell you how many times I've uninstalled and reinstalled 4.8 and 4.5. 4.6 and 4.0 will not install because they say that there's a newer version (why doesn't 4.5 say that??).
Tried a Windows 10 startup repair, and that didn't find anything to repair.
So at this point I've got a ticket in with my IT department to reimage the PC. I've copied all my files to a network share and just waiting for them to come do the deed.
The lesson here is never, never, never, uninstall old versions of the .NET framework that are on your PC. Something is probably still using them.

Related

SQL Server Management Studio 17 problem Visual studio shell isolated

I am getting this problem when trying to launch SQL Server Management Studio 2017. The installation finished with no problems.
problem1
I have reinstalled SSMS, C++ redistributables, .NET Framework 4.5 4.6 4.7, several times, and it keeps the same.
The only thing I can’t install is visual studio 2015 shell isolated. When I try to install, it says the following:
problem2
If I uninstall .NET Framework, and try to install VS Shell isolated, it keeps poping the same screen but with a button of "Accept and install", then it begin to install .NET Framework 4.6 and the screen closes suddenly.
It seems the shell isolated doesnt recognize .NET Framework is installed already, but other software like Visual Studio 2017 Community Edition works perfectly.
It appears in control panel, but if I right-click it, says "change", and then the same screen saying .NET Framework appears.
problem3
Any solution ?
EDIT: I could fix it upgrading to Windows 10. Thanks!
I had a similar issue and fixed it in this way : first I removed all the frameworks I could. After rebooting I removed all the visual c runtime I could. Then, I rebooted again.
After rebooting, I installed in order all the visual c runtime, each bundle in a couple, where x86 was the first. I skipped those who said they were already installed. Finally I installed the framework 4.5.
VS shell should install fine. The issue is due to visual c runtime 2015 being almost compatible with visual c runtime 2017. However, if you manually download and install each version in publication order, the detection should work correctly.
Warning: make a system backup before starting and download all the installers before starting the uninstallation, as after rebooting, certain software may fail as their dependencies could be missing (for example antivirus).

.Net Core 2.1 templates missing from VS2017

I have VS2017 (15.5.4) Professional already installed and today I installed .Net Core SDK 2.1.4 but I cannot see any Core templates in the New Project dialog in VS.
If I run dotnet --version in Powershell, it correctly shows me 2.1.4 installed
I have removed all Core installations on my windows 10 machine, reinstalled 2.1.4, run the repair on VS and also tried devenv /installvstemplates but nothing seems to work.
Can anyone help please?
For .NET Core 2.1, you need Visual Studio version 15.7 or higher. (check it from Help menu > About Microsoft Visual Studio). So, first ensure you have update your visual studio.
Now, to add .NET Core 2.1 (or other newer templates) to visual studio, you need to install the Latest .Net Core SDK from here.
For any templates: Make sure VS has the necessary components, make sure that the cross platform development workload is installed through the Visual Studio Installer.
The SDK 2.1.* only contains the 2.0.* runtimes. At the time of writing, there has been no public preview release for .NET Core 2.1.
You can download 2.2.0 SDK previews from https://github.com/dotnet/cli.
Note that the naming may change in the near future in order to avoid confusion and keep the SDK and Runtime major and minor versions in sync - see https://github.com/dotnet/designs/pull/29.
Update Visual Studio to version 15.6.0.

How to downgrade Microsoft.Data.Entity.Design from 10.6 to 10.0?

Something upgraded my Microsoft.Data.Entity.Design to version 10.6.10617.1. This broke some EntityFramework code generators which use version 10.0 and if it's missing, they error out.
I uninstalled the EntityFramework June 2011 CTP and ran the following installers from a VS 2010 SP1 installation folder (after doing a remove): DACFramework_enu.msi, DACProjectSystemSetup_enu.msi, & TSqlLanguageService_enu.msi but the 10.6 version is still around.
What software upgrades Microsoft.Data.Entity.Design and how do I get back version 10.0 of it, without doing a complete re-installation of Visual Studio 2010?
That is not enough. You didn't reinstall ADO.NET EF Tools. EF Tools 4.2 CTP are intrusive = they break normal EF designer functionality and should not be installed on your main development machine. To fix your VS installation without reinstalling whole VS try to follow uninstalling procedure described in this article.
I uninstalled Visual Studio completely and cleaned the registry of everything related to Visual Studio and then reinstalled it.

Can two different Windows SDK versions coexist on the same machine without conflict?

I have a machine with Vsiual Studio 2005 and Visual Studio 2008 and Windows SDK version 6.1 (Windows Vista). I am planning to install the latest SDK (Windows 7 and .Net 3.5 Service Pack1), but the MSDN Comptabilty document (http://msdn.microsoft.com/en-us/windows/dd146047.aspx) indicates that the latest SDK is not recommended with VS 2005.
I would like to check if the two SDKs can coexist on the same machine or the latest SDK will oevrride the older version and could cause issues with VS 2005.
Thanks
Just a word of warning, the 7.0 SDK has a badly broken installer. It hacks registry keys that are used by Visual Studio to find SDK components and drops files in the VS install directory. This can render it unusable. The worst problems are documented as sticky posts in the Windows SDK forum at the MSDN forums.
I had problems as well, the installer failed half-way through on my machine with a completely undescriptive error. On a pretty virgin machine with VS2008. It didn't roll back the install even though it failed, I had to edit the registry by hand to fix the damage.
I recommend you actually install the SDK on a machine you don't care about. Then copy the directory to a production machine and edit the VC++ directories yourself. Do strongly favor the v7.1 version instead. Good luck with it.
Should be fine as long as you don't try and install both versions of Visual Studio in the same folder. The SDK is essentially passive, you can have as many of them as you want installed, but you need to make sure that the paths that VS 2005 uses are to the older SDK rather than the newer one.
Since by default, the SDK is installed in a subfolder of the Visual Studio install folder, a long as you put different versions of VS in different folders, everything should work out fine all by itself.
Yes they can. I have 6.1 and 7.0 on one machine (Windows 7 64 bit no VS 2005 though) without any noticeable issues.
Definitely you can . u can set the sdk version u want to use each time .
This links tells how to set up your sdk versions in different visual studio versions.
http://msdn.microsoft.com/en-us/library/ff660764.aspx

I have just installed VS.NET 2003 which left my newer versions (2005/2008) crippled

I had Visual Studio 2008 and 2005 installed on my machine , unfartunately i have to install VS.NET 2003 on it to work on an old project. However after the installation now my VS2008 projects are not compiling as they are unable to resolve the .NET core namespaces. I trying reinstalling .NET 3.5 and VS2008 but it still giving me the same errors while building the solution.
anybody had such experience and any tip to solve it?
strangelly VS 2005 is working fine and it means its working fine with .NET 2.0 deployments however its causing issue with ASP.NET MVC project in VS 2008 which is certainly using .NET 3.5 and yes i have given a try to reinstallation as well
rifferte is correct in that it's safest to install in the other they are released.
Probably the best thing to do at this point is to repair your Visual Studio 2008 installation. You can do this through the Control Panel -> Add Remove Programs menu. This should fix the issues you are seeing.
I think you should try the advice here:
http://channa.gunawardena.org/2008/12/installing-visual-studio-2003-after.html
Basically - you actually have to reinstall the framework outside of VS. That being said - the best advice is to always install VS editions in the order they were released.

Resources