It has been while since I posted anything. Mainly not because I was not learning anything new, but it is because I am not getting enough time nowadays (or in other words, I just got a life now :D ). But then I realized that time and time, I like to read my old post to fix some really odd issue and if I don’t keep record of troubles I had in past, I might forget them again. So I decided to find time to write often… it’s my new mid year resolution :D … lets see if I stick to this or not.

Recently I was playing with Windows 2016 Server in our test environment as part of testing it’s viability for our application suite. And so if you have ever worked with .NET Framework project you know that sometimes it can be royal pain to work if there is a version difference between Framework you have installed and Framework project is expecting.

Something like that happened with me in this case too. I need to have Framework 4.0 and Win 2016 has 4.6 installed by default. So against my better judgment, I decided to uninstalled .Net Framework 4.6 from system. It did let me uninstall it just fine but when I rebooted system, it failed to start Server Manager because guess what !! It was depending on .NET Framework 4. So I thought OK, I can download installed from Web and install it using that. But nooooo, since it’s part of OS now you can’t run installer and install framework from there. So I had catch 22 case. I can’t install .NET Framework from installer because it’s part of OS (and you have to use server manager) And you can’t start server manager for installation because you need .NET Framework 4 !!

Dependency

More >