Archive for April, 2010

How to determine which versions of the .NET Framework are installed

Thursday, April 29th, 2010

To determine which versions of the .NET Framework are installed, locate the %systemroot%\Microsoft.NET\Framework folder. To open this folder, you can paste this address into a Windows Explorer address bar. The following folders contain the released versions of the .NET Framework:

  • v3.5

  • v3.0

  • v2.0.50727

  • v1.1.4322

  • v1.0.3705

Note If you see other folders that have a vN.N.NXXXX format, they may contain beta versions or pre-released versions of the .NET Framework. Those versions are outside the scope of this article.

To determine which versions of the .NET Framework are installed on a computer, follow these steps:

  1. Open any one of the folders in the previous list.

  2. Right-click the Mscorlib.dll file, and then click Properties.

  3. Click the Version tab, and then note the file version.

  4. Use the previous list to determine which version of the .NET Framework is installed on the computer, and then click OK.

PING command using IPv4 vs IPv6

Wednesday, April 21st, 2010

If you ping a machine with IPv6 connectivity enabled you will get a IPv6 address. If you are looking for the IPv4 address instead you can use the following command

ping <ip adddress> -4

ASP issues with IIS

Tuesday, April 20th, 2010

If there is an eventlog error about ASP.net permissions

Run

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

.NET fails to install on Windows Server 2003

Wednesday, April 14th, 2010

My coworker Leigh had an issue installing .NET 3.5 SP1 http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe It would start the installation however never complete and with no errors in event logs. After some research it appears the workaround is to install latest Windows Installer (currently 4.5) http://www.microsoft.com/downloads/details.aspx?FamilyId=5A58B56F-60B6-4412-95B9-54D056D6F9F4&displaylang=en#filelist

After installing and then running the .NET 3.5 SP1 installer it sucessfully completed.