These days a vast amount of applications require the Microsoft .NET Framework to be installed on your system. When a .NET based application runs on a machine without the correct version of the framework present, the results can be unpredictable. It’s a certainty the program will not work correctly or at all, but what happens to inform the user about the issue differs from program to program. Quite often you will get a rather obscure error message pop up which doesn’t really tell you anything informative.
The application failed to initialize properly (0x0000135). Click OK to terminate the application.
This is a common error message but gives you no indication whether the problem is actually related to the program itself or is a problem with .NET.
DotNet / NetCore Versions Jun 28, 2016. Comments. Well, the.NET Core 1.0 RTM release went out yesterday, and everything went just fine! The tooling version is also what gets reported from dotnet -version: dotnet -version 1.0.0-preview2-003121 The naming definitely got messed up for the tooling. Upgrading to ASP.NET Core RTM from. Microsoft has a long history of not providing a reasonable way of looking up the version of the runtime that is hosting your applications.NET Core is no different and in this short post I show one way you can capture a descriptive name of the runtime executing that's suitable for displaying in your application's info page.
Some programs might be a bit more helpful and warn you a specific version of the .NET Framework is required before installation can continue. Other software could actually be intuitive enough to offer to download and install the missing version of .NET automatically.
For those that are not sure what it is, the .NET Framework is an application development platform that makes it easier for software developers to create a range of Windows applications and services. Essentially it makes coding programs faster and less troublesome. A .NET application also runs inside its own virtual machine which is helpful from a security standpoint.
A big issue with .NET is it’s a sizable download and when installed can take up several hundred Megabytes of hard drive space. Programs are also built requiring a certain version of .NET so just installing one version probably won’t be enough. For example, Program A might need .NET 3.5 while program B might need .NET 4.6. In that case, you will need both on your system.
Windows Server, Vista, 7, 8/8.1 and 10 all come with a version of .NET integrated into the operating system. Since there are many versions of the .NET Framework (1.0, 1.1, 2.0, 3.0, 3.5, 4.0, 4.5.x, 4.6.x, 4.7.x and 4.8) and more than one are often present on the same system to run different applications, sometimes even you as a user might not even know which .NET is installed on your computer. Here are a few ways you can find out.1. Raymondcc .NET Detector
One way to check which versions of .NET are installed is through the system registry. If a .NET package is installed, its information should be correctly entered in the registry. We decided to use this method and create a little tool which does the plain and simple task of telling you which versions of .NET you have installed.
The tool couldn’t be simpler to use, just run the executable and it will tell you which .NET’s you have by showing them in dark text, the grayed out entries aren’t installed. Clicking on a version that isn’t currently installed will take you to its download page at Microsoft. The information from the window is copied to the clipboard to paste into help files etc. The program is able to detect .NET Frameworks from 1.0 up to the latest 4.8 (including versions specific to Windows 10), is portable and works on Windows XP and above. Any feedback you might have about the tool is welcome.
Download Raymondcc .NET Detector
2. Raymondcc .NET Detector Command Line Edition
Although there may be a simple tool out there that allows you to use the command line to easily find out what versions of .NET are installed, we haven’t come across one. As a consequence, we created a version of .NET Detector that works from batch scripts and the Command Prompt instead of a GUI. The output will be shown in the console window.
Run NET_Detector_cli.exe from a script or Command Prompt to get a simple display of the installed versions of .NET. Add the argument “/v” to show a second column with the full version number of each installed framework.
This tool works the same way as the GUI version and checks the system registry for the installed versions of .NET. Other checking methods are not as reliable. It works on any XP or above system and detects .NET versions 1.0 to 4.8. Feedback is welcome on this tool as well.
Download Raymondcc .NET Detector CLI Edition
Special Note: We are fully aware that both .NET Detector tools produce a small number of detections in some online Virus Scanners like Virus Total. Raymondcc created and hosts these files so we know every line of code and can assure you the detections are false positives.
3. ASoft .NET Version Detector
This program is a small and lightweight portable tool that gives information on all the different versions of .NET Framework that are installed on a machine. If the system does not have a specific version installed, there are handy button links provided to give you access to the related Microsoft webpage page so you can easily download it. A link to download each version’s Software Development kit (SDK) is also provided.
An installed .NET version will be shown with white text. Clicking the logo next to it will navigate to its install directory. The log box at the bottom shows which versions and related update patches are present, including 32bit/64bit, and the relevant folder locations. The copy button will simply copy all the text in that box to the clipboard.
Go to Help > .NET Version History to see which versions of .NET are installed on which operating systems as standard. ASoft .NET Version Detector detects versions 1.0, 1.1, 2.0, 3.0, 3.5, 4.0, 4.5 and 4.6 of the .NET Framework and can also be run in Windows 2000 and above. The official website is dead but the tool can still be found online.
Download .NET Version Detector
12Next › View All You might also like:
Check .NET Compact Framework Version Installed on Windows Mobile4 Ways to Repair or Remove Microsoft .NET FrameworkWhy are there Multiple Versions of Microsoft .NET Framework in Add or Remove Programs?3 Ways to Check Installed Audio and Video Codecs On Your ComputerError Code 66A when Updating Microsoft .NET Framework 4 from Windows Update 34 Comments - Write a Comment
Or you can execute PowerShell script
github.com/peterM/Net_Framework_Installed_Versions_Getter
Thanks alot.
ReplyOn Windows 8.1 x86 clean install:
1. Installed .NET Framework 4.6.2 and Raymondcc .NET Detector could detect the version but v4.5 was gone I guess cause the program showed as not installed.
2. Afterwards I installed .NET Framework 4.7 but oddly Raymondcc .NET Detector couldn’t detect any version anymore, except v3.5, v2.0.
Thanks for the feedback.
1. v4.6.x is an update to v4.5 and replaces it on the system, so you can’t have both 4.5 and 4.6.2 installed at the same time.
2. The tool was last updated in April when .NET 4.7 was only available for Windows 10 Creators update and the standalone installer hadn’t been released. The tool has now been updated to detect the installer version of 4.7. Do note that 4.7 is also a replacement update for 4.5 or 4.6, so you will get only 4.7 and not 4.6.x or 4.5.x.
Great job indeed
ReplyDear Dale Chen,
This is very good offer. Thanks for this beautiful comment.
PowerShell solution provided by Microsoft: gallery.technet.microsoft.com/How-to-determine-versions-d3669799
ReplyTo find .NET Framework versions by viewing the registry (.NET Framework 1-4)
On the Start menu, choose Run.
In the Open box, enter regedit.exe. You must have administrative credentials to run regedit.exe.
In the Registry Editor, open the following subkey: HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDP.
(taked from msdn.microsoft.com/en-us/library/hh925568(v=vs.110).aspx)
this doesnt work on the latest windows versions
Replywmic /namespace:rootcimv2 path win32_product where “name like ‘%%.NET%%'” get version
it will show the installed version
ReplyAnother way to detect is using the “Microsoft Web Platform Installer” which will exactly show the Framework versions currently installed as well as the ability to download and install versions from it instantly.
ReplyNice work,
Can you please upgrade this tool to detect .NET Framework 4.5.1 and 4.5.2
Currently, I need to check the minor version as per my product prerequisites, would be more beneficial if we get to know the Minor versions using this tool
ReplyIf you put your cursor over 4.5 it will show you the version. Mine says 4.5.50938
ReplyThank you so much for the detector app! <3
ReplyThank you for the Raymondcc .NET Detector app. It was exactly what I needed to fix an “Unhandled Exception” error by helping to install the missing .NET Framework(s) ! :-)
ReplyThanks a lot for Raymondcc .NET Detector. Very quick, very easy, very helpful,
Replyworks well fantastic
ReplyTry this
dir %windir%Microsoft.NETFramework/AD
Replywmic /namespace:rootcimv2 path win32_product where “name like ‘%%.NET%%'” get version
ReplyThanks a lot. Very useful for getting results from users.
ReplyThanks for the fantastic tool!
ReplyFantastic answer
ReplyThanks, that’s helping a lot.
Replyworked thanks!
ReplyThanks a lot
ReplyWoww. I’ve never thought about this. Thanks a lot.
Replythanks raymond, i was trying to use quickpwn and didn’t realize i needed .net so thanks for letting me know and helping me.
ReplyThanks, I was not sure what version I had, as I know I had got a new one but now I do!!!
Many thanks. ;)
ReplyThanks dude. this work very fine.
Replyuseful tool man
thanks
ReplyWoohoo… excellent job Raymond…makes my life easier when checking my customers’ PC(s)
ReplyThanks Ray..
Replyvery useful.. Thank you Ray~
Replythanks Raymond
Reply