.NET Framework setup verification tool, cleanup tool and detection sample code now support .NET Framework 4.5.2
I have posted updated versions of the .NET Framework setup verification tool, the .NET Framework cleanup tool, and the sample code to detect .NET Framework install states that support detecting, verifying, and cleaning up the .NET Framework 4.5.2. You can find more information about how to download and use these tools at the following locations:
- .NET Framework setup verification tool user’s guide - https://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
- .NET Framework cleanup tool user’s guide - https://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx
- Sample code to detect .NET Framework install state and service pack level - https://blogs.msdn.com/b/astebner/archive/2009/06/16/9763379.aspx
As always, if you run into any issues or have any feedback about these tools or samples, please let me know by posting a comment on one of my blog posts or using my blog contact form.
Comments
- Anonymous
January 12, 2015
The comment has been removed - Anonymous
January 13, 2015
Hi andrewepbrown@gmail.com - There are multiple versions of the .NET Framework. It is possible that the CaptureOne tool that you're trying to use requires a different version of the .NET Framework than you currently have installed, and that could be why it is trying to install the .NET Framework during its setup process. In order to try to narrow down the .NET Framework install hang that you're seeing, could you please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your setup log files, upload the file named %temp%vslogs.cab that this tool will create to a file server (such as http://onedrive.live.com), and then reply back here and provide a link that I can use to download your log files and take a closer look?