I have a huge web application written with VS2003.  I have a new project being written in VS2005 using the StratFrame framework.  Both are installed on my machine and being used nearly every day to make minor adjustments and such.  The day is coming when I will have to purchase VS2008.  I know that the StrataFrame gang has been busy with that product and working on getting SF ready for prime time.  At some point you are going to say, "That's it for VS2005".  When do you expect that you will no longer write for VS2005 and "encourage" your user base to move forward into VS2008?

Thanks,
Bill

How, please, please. I am still stucked and after endless trials and searches I am starting to give up.

Hi Gordon.

Yeah, I almost went crazy with this one.

Basicaly, I got it fixed following this post: http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=311949

These are the steps that I took:

1. Downloaded the large 197MB NET 3.5 Full Redistribution Package if you need. This is however not required.

2. Used this diagnostic tool which you recommended: (after installing the above package) http://blogs.msdn.com/aaronru/archive/2007/11/29/net-framework-3-5-installation-validation-tool.aspx

3. Run the following from an elevated command prompt:  Winmgmt /verifyrepository

4. If the repository is reported as INCONSISTENT, run “Winmgmt /resetrepository” (if it fails because of service dependency, run “net stop winmgmt” and try again). If the repository is consistent, skip this step.

5. Do “mofcomp C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet.mof” to compile the failed mof.

6. Reapplied the "VS 2008 DVD\WCU\dotNetFramework\dotNetMSP\x86\NetFX2.0-KB110806-v6000-x86.msu"

7. Rebooted and tried running the script in step 2 again. It confirmed everything was now configured correctly.

Hope it helps you 

Thanks for the quick answer, it works now. Had to reinstall KB110806 also.

Thanks

Good to hear