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

I suspect (and I doubt that you can say) that v2 is not that for out (within the year), so I suppose I had better get my copy of VS2008 soon. 

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

Yep, this is true, all the VS install side-by-side. I currently have VS2005 and 2008 installed. I used to have vs2003 and vs2005. However, since 2008 can work with .net 2.0, 3.0 and 3.5, VS2005 isn't really needed (you'd still have to have VS2003 for those .net 1.1 projects). In fact, I just (today) switched to VS2008 cause VS2005 decided it would no longer compile my project (see http://forum.strataframe.net/FindPost13874.aspx). Sigh...

Hey Greg,

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

Hey guys.

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...

LOL....good luck with a response there

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.

Cool

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