Thanks,
Bill

All updates until the next major version of SF will support 2005, so all projects that you are current developing will a.) have a migration path towards 2008 and b.) will still support VS2005.

The next major version of SF (2.0) will more than likely not support VS2005 as there will be many new features that will rely on .NET 3.5 which can only be used in 2008.  So here is a good litmus test, all SF code that comes out that supports .NET 2.0 will still work in VS2005...hope that makes sense

-Larry

I assume all three (VS2003, 2005 and 2008) will work on the same machine as long as the corresponding .NET Frameworks (1.1, 2.0, 3.0/3.5) exist still.  Is this true?

Thanks,
Bill

I saw that post...bummer.  I am really hoping that issue does not come my way.  The upgrade is not in the budget (since I just purchased StrataFrame), so it will have to wait a few more months until the money police back off a little.

I am glad that I can use VS2008 to take care of my 2.0 projects.  That will be nice.

Bill

I've being playing with VS2008 for a couple of months now, and I like it. The thing is, that was on my notebook and life was good. Some weeks ago I decided to put it into production and installed it on a desktop... same environment, Vista Ultimate, nothing really specialy different from the notebook, except more horse power. It won't work, not a SF problem related at all, as it won't work even on a vanilla Windows Application project. This is what I get if I try to open the famous Form1, or any form added to the project:

---------------------------
Microsoft Visual Studio
---------------------------
The service Microsoft.VisualStudio.Shell.Interop.ISelectionContainer already exists in the service container.

Parameter name: serviceType

The project also shows an error at the Error window:

Error 1 .NET Framework 2.0 update not found. The win32manifest will not be embedded. WindowsApplication1

And on the Output window I get something telling me "The Visual C++ Resource Editor Package did not load because of previous errors, yada yada yada" (I learnt this one on Seinfeld)

I have googled everywhere, found many people going nuts on this too, no words from Microsoft.

If anyone has any idea of what I could try, I would appreciate to hear it.

Trent will buy you a beer next time we meet... oh, sorry, I will buy the beer... just got used to that idea...

Yes.  We are even planning on the next major version of allowing different versions to be installed side-by-side.  So the pre-2.0 stuff will definitely be a different program GUID (install GUID) than the next major version so that they can run side-by-side.

Ivan, I have seen this before and I had to load the Windows Vista Software Development Kit and the issue went away...it was really weird when I saw it...but this was before I built my new development machine, which for whatever reason I had not issue

Yep, I've tried that, no good for me. Today I found this:

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=311949

Will try it later...

Ivan George Borges (02/01/2008)

---

Believe it or not (I still don't), but after a while going back and forth following instructions on that Connect forum, I finaly got VS2008 working properly on my desktop.

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

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