Update on the ASP.NET 2.0 warning

Several of you have reported having successfully installed the .NET 2.0 runtime on a machine running WSS/SPS. If you set the IIS Web Application for WSS/SPS to use ASP.NET 1.1, things appear to continue to work.  We’ve done some more checking and — at least at first — have found similar results.  So I’ll downgrade my earlier warning slightly:

Until WSS Service Pack 2 is released, don’t install .NET 2.0 on a production machine running WSS (or WSS/SPS).  The configuration may or may not behave correctly, and in any event it won’t be supportable.

It’s still a far better idea to wait for WSS SP2, but if you’re using a dev or test machine for multiple applications, some of which are ASP.NET 2.0–based, take your best shot.

Comments

• Anonymous
  April 13, 2005
  You should edit the original post to include this information. I ended up uninstalling .NET 2.0, and reinstalling Sharepoint/IIS to fix the problem, which of course blew away all my sharepoint content. I only found this post afterwards.
• Anonymous
  July 22, 2005
  Okay, this is probably a dumb question, but how exactly do you set the IIS Web Application for WSS/SPS to use ASP.NET 1.1?
  On my IIS (6.0), there's no "ASP.NET" tab, so I must be missing some subtle detail. I'm not running any beta service packs at the moment.
• Anonymous
  July 23, 2005
  I retract my question (unless you want to answer anyway for archival purposes (-: ).
  I was having a weird problem when creating my first top-level site (I'm just starting to mess with Sharepoint), that I assumed was an ASP.NET version problem. Oddly, when I rebooted my server it magically started to work, so most likely the problem was elsewhere.
• Anonymous
  August 15, 2005
  While SPS typically has the same support guidelines as WSS, you shouldn’t always assume SPS 2003 will support what WSS v2 does. This post indicates that WSS v2 will support .NET Framework 2.0 w/ SP2. Nothing has yet been said about SPS 2003 SP2 support for Whidbey.