>>>>>>>>>>>>>>>Hi,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>I suppose that someone here has a beta version of VS 2010. Does VS 2010 include WinForms projects?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>Also, if you install VS 2010 on the PC that has VS 2005 can you use either independently? That is, can you still maintain VS 2005 projects with VS 2005 after installing VS 2010?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>TIA.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>It does include WinForms projects.
>>>>>>>>>>>>>
>>>>>>>>>>>>>You have VS 2010 beta?
>>>>>>>>>>>>
>>>>>>>>>>>>Yes, I do. I checked Windows Forms project yesterday trying to answer Michel's question.
>>>>>>>>>>>
>>>>>>>>>>>Do you also have VS 2008 and/or VS 2005 installed on your PC?
>>>>>>>>>>
>>>>>>>>>>I have VS 2008 SP1. I don't have VS 2005 and don't need it.
>>>>>>>>>
>>>>>>>>>Sorry for many questions but I know you like to answer <g>. Do you find the IDE much different between VS 2008 and VS2010 (in terms of look and feel and general features)?
>>>>>>>>
>>>>>>>>So far I found VS 2010 to be much slower than VS 2008. I haven't worked in them much recently.
>>>>>>>>
>>>>>>>>On the other hand, there are nice features in VS 2010 such as Team Foundation Server for version control.
>>>>>>>
>>>>>>>Thank you, Naomi. I am not surprised that new MS version is much slower than the previous; this is their trade mark <g>. I wonder if I will be able (when I get VS 2010) to disable the version control and make things work faster.
>>>>>>
>>>>>>You don't have to use version control at all. TFS is a seperate install. VS2010 has built-in connectivity for it.
>>>>>>
>>>>>>Personally I use version control for anything I do that may someday be used or referenced again. All client projects, virtually all of my personal applications. It isn't just for corporate use.
>>>>>
>>>>>Same here. I want to be able to look back at previous versions and don't like littering the source code with commented-out code and change comments.
>>>>
>>>>"Littering the code?" :o) I disagree. I think those comments belong in there even with TFS. It's one thing to do a comparison and see what was added, modified, or removed, but the submit change comment is seldom sufficient unless you submit for every single minor change so you can do a good comment with it at the time of submission (and not inline). I don't think that is a replacement for inline comments at all, but rather an overview of changes only.
>>>
>>>There is no right or wrong answer. Personally I don't like the clutter in base code. To me that is the function of a source control program. Inline comments to me are the way it used to be done when there was no better way.
>>>
>>>Source control contains not only a text overview of changes but line by line code differences as well.
>>
>>I think an inline comment can often be very illuminating. No need to write a book just a brief note about what something is for.
>
>You may have misunderstood me. I am all for comments. What I don't like is a lot of dead code in the source with explanations of when and why it was deactivated.

deleted