The following questions are probably pretty common. I was just wondering if
anyone might be able to point me in the right direction to finding some good
answers. Thanks!!
1. Does upgrading an existing solution to VS 2005 also upgarde the solution
to use .NET 2.0?
2. Does VS 2005 work with VSS 6?
3. Does VS 2005 work with MSDE?
4. I received a copy of VS Standard Edition at a launch event. Is it
possible to do any serious development using this edition, or is an upgarde
to the pro edition a must? I realize that the standard edition does not
include SQL 2005 integration, but I would be willing to use SQL Management
Studio for now. Is there something else I am missing???
5. Is upgrading an existing solution a pretty reliable process, or is there
a chance that I will end up with issues???
Any insight, or a point in the right direction would be appreciated!!!
> 1. Does upgrading an existing solution to VS 2005 also upgarde the
> solution to use .NET 2.0?
Yes. VS.Net 2005 only works with .Net platform 2.0.
> 2. Does VS 2005 work with VSS 6?
Yes.
> 3. Does VS 2005 work with MSDE?
It can work with virtually *any* data source.
> 4. I received a copy of VS Standard Edition at a launch event. Is it
> possible to do any serious development using this edition, or is an
> upgarde to the pro edition a must? I realize that the standard edition
> does not include SQL 2005 integration, but I would be willing to use SQL
> Management Studio for now. Is there something else I am missing???
I taught myself programming on a 386 SX machine with 4 MB of RAM, and
initially using freeware command-line compilers. It was a great experience.
I became very good at making chicken salad out of chicken s**t. And, after
upgrading my compiler to a pirated copy of Borland C++ 2.0, I wrote a BBS
door role-playing game that used ANSI graphics, and took about 6 months to
play through. I would say that was serious development. It took me a year
and a half to write it, using all kinds of freeware and workarounds due to
my lack of proper tools.
Now I have the latest and greatest of everything. Of course I'm happy to
have it. But I wouldn't trade my experience with almost nothing for almost
anything. It made a good programmer out of me. After all, half of
programming is problem-solving, and figuring out workarounds for various
contingencies.
So, are you missing anything? What can you afford? Get the best tools you
can, of course, but it's up to you what you do with them. You can do
anything you set your mind to.
> 5. Is upgrading an existing solution a pretty reliable process, or is
> there a chance that I will end up with issues???
There is an excellent chance that you will end up with some issues. But it
is as reliable a process as it can be, under the circumstances. You
shouldn't have any problems dealing with the leftovers.

Signature
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.
> The following questions are probably pretty common. I was just wondering
> if anyone might be able to point me in the right direction to finding some
[quoted text clipped - 17 lines]
>
> Any insight, or a point in the right direction would be appreciated!!!
craig - 16 Dec 2005 21:57 GMT
Excellent feedback, Kevin. I really appreciate it.
>> 1. Does upgrading an existing solution to VS 2005 also upgarde the
>> solution to use .NET 2.0?
[quoted text clipped - 62 lines]
>>
>> Any insight, or a point in the right direction would be appreciated!!!