views:

1332

answers:

4

The option to target another version of the .Net Framework is disabled on a particular test system we are using on a current project.

I have tried the following without success:

  • Killing all W3WP.EXE processes
  • Restarting the IIS service
  • Remote Debugging has been removed from the box.

Just hoping for some pointers.

+2  A: 

Try reRegistering ASP.NET on IIS.

Ovidiu Pacurar
+1  A: 

I think that this happens if you install the iis after the .net installation. Just use the aspnet_regiis.exe as explained before.

Igal Serban
A: 

Do you have ASP.net Serveice (Allowed) in IIS

In anyway, you can use some vbscript to change the .net version.

+1  A: 

Are you sure you are asking the right question?

There is no new .NET Runtime version to target. If you have a 3.0 or 3.5 Framework your IIS will still display 2.0 as it's runtime because 3.0 and 3.5 differ only in Framework classes and compiler from a 2.0 application!

You should only see 1.X and 2.0 frameworks in your IIS configuration.

Edit: Target switching only happens when your compile your application. Because 2.0, 3.0 and 3.5 all run on the same .NET Runtime Environment 2.0 (VM). You still need to have the additional frameworks installed because their API differs, but all run on the same intermediate language instruction set.

Tigraine