visual studio 2005

[Aaron]

Is it possible to use .net framework 1.1 in vs2005?

where can i find a list of new features of .net framework 2.0?

thanks

 

[Cowboy \(Gregory A. Beamer\) [MVP]]

Currently, nothing is published as an extensive list. Here are some sources:
http://msdn.microsoft.com/whidbey
http://www.asp.net/whidbey

And, no, AFAIK, you cannot use 1.1 in Whidbey.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************************************************
Think outside the box!
***************************************************************

 

[Joe Coder]

Currently, nothing is published as an extensive list. Here are some sources:
http://msdn.microsoft.com/whidbey
http://www.asp.net/whidbey

And, no, AFAIK, you cannot use 1.1 in Whidbey.

That's really cool.....the whole "Visual Studio 2005: IDE Enhancements for
C# Developers" thing I mean....

It does raise one question for me though...

Why doesn't MS just go ahead and tell the Visual Basic programmers to go to
hell?

This is another example of how MS is ignoring the largest group of
programmers (and admittedly programmer wannabes) ever amassed in favor of
their own version of JAVA.

While it is true that any programmer should be able to pick up the new
language and use it, most VB programmers that I have encountered dislike
the syntax of C# primarily because it is so different from the Visual Basic
syntax that they have successfully learned and used in their work
environments.

But, screw that whole "Microsoft has abonandoned the VB programmers"
discussion...it's a done deal.

I am still left wondering why MS doesn't just tell them to learn C# or go
to hell? In the end, MS would only have one language to support and it
would cut their expenses.

I think that VB programmers would actually appreciate the honesty (because
they could stp wasting time and money with Fred.Net) and those that love
programming would make the move.

Com'on Microsoft! Grab yourself by the balls and tell 'em already!

Joe Can't Code

 

[Jon Skeet [C# MVP]]

That's really cool.....the whole "Visual Studio 2005: IDE Enhancements for
C# Developers" thing I mean....

It does raise one question for me though...

Why doesn't MS just go ahead and tell the Visual Basic programmers to go to
hell?

Um, because Whidbey also has loads of extra new features for VB.NET as
well?

This is another example of how MS is ignoring the largest group of
programmers (and admittedly programmer wannabes) ever amassed in favor of
their own version of JAVA.

While it is true that any programmer should be able to pick up the new
language and use it, most VB programmers that I have encountered dislike
the syntax of C# primarily because it is so different from the Visual Basic
syntax that they have successfully learned and used in their work
environments.

So they should use VB.NET.

But, screw that whole "Microsoft has abonandoned the VB programmers"
discussion...it's a done deal.

Really? Is that why VB.NET is getting various features from C# which
have been requested (unsigned types, XML documentation, operator
overloading, for example) and edit and continue (which C# *isn't*
getting, probably) in Whidbey? (Along with various features new to both
languages, such as generics, of course.)

Just because MSDN happens to be featuring one article saying what C# is
getting doesn't mean VB.NET won't be getting a load of stuff too.

 

[Joe Coder]

Um, because Whidbey also has loads of extra new features for VB.NET as
well?


So they should use VB.NET.


Really? Is that why VB.NET is getting various features from C# which
have been requested (unsigned types, XML documentation, operator
overloading, for example) and edit and continue (which C# *isn't*
getting, probably) in Whidbey? (Along with various features new to both
languages, such as generics, of course.)

Just because MSDN happens to be featuring one article saying what C# is
getting doesn't mean VB.NET won't be getting a load of stuff too.

Dude......it was posted as a joke. Just a little poke at my VB.Net
friends.

Relax. Go back to your regularly scheduled life.

Joe Can't Code

 

[Colin Jack]

Hi All,

I think it looks great but I'm worried about one thing.

I've just completed the C# Windows Development MCP and plan to do the Web
and XML Web services ones later in the year. Anyway I just hope Microsoft
bring out a single exam that will let MCAD's upgrade as otherwise I'll
complete mine, with a lot of effort on my part, and have to do it all again
come next year

Ta,

Colin Jack

 

[Matt Hawley]

Colin,

That brings up a good point. My intial thoughts were pointing towards not needing to since the exams relate more towards debugging and the technology. However, there has been a drammatic change in how items are data bound, and others. I personally still think that it won't be an issue, it just may be that future exams may cover more material than what we did. However, time will tell.

Matt Hawley, MCAD .NET
http://www.eworldui.net

Hi All,

I think it looks great but I'm worried about one thing.

I've just completed the C# Windows Development MCP and plan to do the Web
and XML Web services ones later in the year. Anyway I just hope Microsoft
bring out a single exam that will let MCAD's upgrade as otherwise I'll
complete mine, with a lot of effort on my part, and have to do it all again
come next year

Ta,

Colin Jack

 

[Colin Jack]

Yeah I looked at things like the updates to ADO.NET and, at the same time as
thinking it was great, my heart sunk

Hopefully your right but I wouldnt even mind doing a single upgrade exam,
just covering the new stuff. I just wouldnt want to become an MCAD late on
this year and then be doing it all again.

Fingers crossed,

Colin

Colin,

That brings up a good point. My intial thoughts were pointing towards not

needing to since the exams relate more towards debugging and the technology.
However, there has been a drammatic change in how items are data bound, and
others. I personally still think that it won't be an issue, it just may be
that future exams may cover more material than what we did. However, time
will tell.