When you install CRM 3.0, it will actually run certain components of
CRM 3.0 fine in .NET 2.0 from experience, however falls over on other
components.  The only way to reliably run CRM 3.0 is to use .NET 1.1
to run it.  This was most interesting when we first experienced it as
a tech support issue (seeing CRM 3.0 running fine in some areas and
crashing in others with the error message footer stating .NET 2.0 was
being used made most of the developers gasp in amazement).

That being said, you can actually have both .NET 1.1 and .NET 2.0
running alongside each other.  When I set up a VPC image for running
CRM, it usually has 3 versions of .NET installed on there - .NET
1.0, .NET 1.1 and .NET 2.0.  I go to the .NET 1.1 folder and run a
command as follows to enable me to select .NET 1.1 to run CRM:

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322>aspnet_regiis.exe -i

In fact, most times I just have to run this command and everything
works just fine - no further tweaking involved.  On the odd occasion I
did have to go in through IIS and force CRM to run on .NET 1.1 instead
of .NET 2.0 manually, however those were few and far between.

Kris Rhodes
----
MS CRM Certified (Installation & Configuration, Customisation)
CRM 3.0/VB.NET 1.1 Developer
Quantum Business Technology
Perth  West Australia
Blog: http://rhodeskc.wordpress.com

This information is intended to be advice and advice only.

On May 9, 11:24 pm, "Jacob Mondrup - Vivant IT Management"