Started to open the 1.707 source in VS2010 and the conversion wizard wanted to do something to it.



If I had gone ahead to convert would the solution still open in VS2008 ?



(currently I'm considering renaming the source folder then reinstalling in the default folder and only opening the renamed source folder to play with in VS2010



Kudos, by the way, for the added support for 2010.

Hi Charles,



I have not installed VS2010 yet, waiting for the final release next week.



About your question, I don't think it will open in VS2008 and it does make sense since VS2010 fully support all .Net frameworks so the idea is to have one version of VS installed and then you can tell it which version of the .Net will you be supporting, basically the same as VS2008 in respect to VS2005.

Edhy Rijo

You have the option of setting the target .NET in 2010. ( it is VERY cool )



The conversion didn't actualy convert anything, but I opened a copy instead of the default folder source.



Just installing 1.707 hooked SF into the VS2010 IDE as well, where it seems to be very happy.



Suggest anyone working with VS2010 immediately find the Snippet Designer add-on. Awesome.



I am going to experiment some more with some 3.5 projects to see if I can open and mod them in VS2010 and still work them in VS2008. Seems it would only be a problem if you referenced .net 4.0

The problem with that is that many of the new functionality to the VB language is in VS2010 like no need to put an underscore to brake a line and many other. The whole idea of VS2008 & VS2010 to support all .Net runtime was to be able to upgrade to the new VS2010 and still keep your project in whatever runtime version you want but take advantage of the new features in the new VS version and in this case there are ton of new features for developers in VS2010.

Edhy Rijo

I understand what you're saying and agree.



I haven't experimented yet, but I suspect a 3.5 project in VS2010 IDE won't let you do automatic properties or inferred line continuation. If that is the case - and the IDE prevents you from getting in trouble - it seems you should be able to take advantage of some of the other cool IDE stuff in VS2010 and still have a project that works in the VS2008 IDE (though I'm not sure why I'd want to)



In any case, I would probably developing new projects only in 4.0. I'm going to see what happens to 3.5 projects I am not ready to upgradge to 4.0 yet (at least not until it ships) and see if I use only 3.5 features in VS2010 the project still works in VS2008.



And since the SF source is still 2.0 AFAIK and is used read-only I guess it won't be an issue.

Okay, for benefit of lurkers :



SF Source opened in VS2010 ( have to run conversion wizard ) even though it is not recompiled and the conversion wizard appeared to make no changes can no longer be opened in VS2008



And of course a project originally written in VS2008 3.5 once converted on being opened in VS2010 ( same 3.5 target ) can no longer be opened in Vs2008.



Moral of story - make copies to play with or test your projects in VS2010.



Also interesting to note that you do not have to target 4.0 in order to use inferred line continuation or automatic property declaration ( no need to write standard get/set )



This is cool.



And definitely look into the Snippet Designer extension. Once you have it installed, go to the Snippet Explorer window in Other Windows, find a .snippet and double click it. You can write your snippets right in the IDE in whatever language. Properties for shortcuts etc.

I think the only changes made are to the actual solution file if it is anything like the 2005 to 2008 upgrade. If you had to I bet you could put it back in a pinch by editing the .SLN file in notepad, there were only like two lines that changed. Unless of course Microsft changed everything like they love to do.

In a demo I saw at a recent event you were able to use 90% of the new IDE features without targeting .NET 4.0.

Fun stuff.

Keith Chisarik

All good stuff, guys. Yes, in this case you would have only had to change the SLN back to 9.0 as Keith mentioned. The SF source will remain in VS2008 solution for a while (not sure exactly how long) giving people a little while to get on the VS2010 platform. I would imaging this to be a slower move by many developers than from VS2005 to VS2008. We actually have a lot of developers still in the VS2005 environment and when the SF projects were swapped over that persuaded some to make the move then.



At any rate, the solution changing to 10.0 will not impact the content of the projects. But once you make the move forward, it is hard to go backwards.



I guess that today is the big day for VS2010 and its counterparts, so I am sure that it will be a more common topic in the near future.