QUERY: C# woes .NET 1.1 vs .NET 2.0

[Andrew Wan]

How different is it to program C# for Visual Studio 2003.NET & Visual Studio
2005? I know Visual Studio 2003.NET uses .NET 1.1, whilst VS2005 uses .NET
2.0. So the question really is, what is the difference & significance of
programming C# for .NET 1.1 & .NET 2.0?

[Duggi]

http://msdn2.microsoft.com/en-us/library/t357fb32.aspx

Thanks
-Cnu

Andrew Wan wrote:

How different is it to program C# for Visual Studio 2003.NET & Visual Studio
2005? I know Visual Studio 2003.NET uses .NET 1.1, whilst VS2005 uses .NET
2.0. So the question really is, what is the difference & significance of
programming C# for .NET 1.1 & .NET 2.0?

[Michael Nemtsev]

Hello Andrew,

http://msdn2.microsoft.com/en-us/lib...2e(VS.80).aspx

---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

AWHow different is it to program C# for Visual Studio 2003.NET &
AWVisual Studio 2005? I know Visual Studio 2003.NET uses .NET 1.1,
AWwhilst VS2005 uses .NET 2.0. So the question really is, what is the
AWdifference & significance of programming C# for .NET 1.1 & .NET 2.0?
AW>

[Andrew Wan]

Thanks.

My question really was, if one programmed C# for VS2003 (.NET1.1), will it
easily migrate to VS2005 (.NET2.0)?
"Michael Nemtsev" <ne*****@msn.comwrote in message
news:a2***************************@msnews.microsof t.com...

Hello Andrew,

http://msdn2.microsoft.com/en-us/lib...2e(VS.80).aspx

---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

AWHow different is it to program C# for Visual Studio 2003.NET &
AWVisual Studio 2005? I know Visual Studio 2003.NET uses .NET 1.1,
AWwhilst VS2005 uses .NET 2.0. So the question really is, what is the
AWdifference & significance of programming C# for .NET 1.1 & .NET 2.0?
AW>

[Michael Nemtsev]

Hello Andrew,

It depends on type of app. If only C# without many dependencies on .NET fw
like appdomains and etc - he will.
The worst case is ASP.net - many changes need to be done

---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

AWThanks.
AW>
AWMy question really was, if one programmed C# for VS2003 (.NET1.1),
AWwill it easily migrate to VS2005 (.NET2.0)?
AW>
AW"Michael Nemtsev" <ne*****@msn.comwrote in message
AWnews:a2***************************@msnews.micros oft.com...
AW>

>Hello Andrew,

http://msdn2.microsoft.com/en-us/lib...2e(VS.80).aspx

---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo

AWHow different is it to program C# for Visual Studio 2003.NET &
AWVisual Studio 2005? I know Visual Studio 2003.NET uses .NET 1.1,
AWwhilst VS2005 uses .NET 2.0. So the question really is, what is
the
AWdifference & significance of programming C# for .NET 1.1 & .NET
2.0?
AW>

[Andrew Wan]

..NET fw? appdomains?
So it's like programming VS6 + MFC6. As long as I keep away from using
MFC6/.NET1.1 specific stuff then code will work in future versions of VS.
"Michael Nemtsev" <ne*****@msn.comwrote in message
news:a2***************************@msnews.microsof t.com...

Hello Andrew,

It depends on type of app. If only C# without many dependencies on .NET fw
like appdomains and etc - he will.
The worst case is ASP.net - many changes need to be done

---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

AWThanks.
AW>
AWMy question really was, if one programmed C# for VS2003 (.NET1.1),
AWwill it easily migrate to VS2005 (.NET2.0)?
AW>
AW"Michael Nemtsev" <ne*****@msn.comwrote in message
AWnews:a2***************************@msnews.micros oft.com...
AW>

Hello Andrew,

http://msdn2.microsoft.com/en-us/lib...2e(VS.80).aspx

---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo

AWHow different is it to program C# for Visual Studio 2003.NET &
AWVisual Studio 2005? I know Visual Studio 2003.NET uses .NET 1.1,
AWwhilst VS2005 uses .NET 2.0. So the question really is, what is
the
AWdifference & significance of programming C# for .NET 1.1 & .NET
2.0?
AW>

[Michael Nemtsev]

Hello Andrew,

Not so, but very close.
Just C# has the best compartability. Another .NET framework features was
changed more

---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

AW.NET fw? appdomains?
AWSo it's like programming VS6 + MFC6. As long as I keep away from
AWusing
AWMFC6/.NET1.1 specific stuff then code will work in future versions
AWof VS.
AW"Michael Nemtsev" <ne*****@msn.comwrote in message
AWnews:a2***************************@msnews.micros oft.com...
AW>

>Hello Andrew,

It depends on type of app. If only C# without many dependencies on
.NET fw
like appdomains and etc - he will.
The worst case is ASP.net - many changes need to be done
---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo

AWThanks.
AW>
AWMy question really was, if one programmed C# for VS2003
(.NET1.1),
AWwill it easily migrate to VS2005 (.NET2.0)?
AW>
AW"Michael Nemtsev" <ne*****@msn.comwrote in message
AWnews:a2***************************@msnews.micro soft.com...
AW>

>>>Hello Andrew,

http://msdn2.microsoft.com/en-us/lib...2e(VS.80).aspx

---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo
AWHow different is it to program C# for Visual Studio 2003.NET &
AWVisual Studio 2005? I know Visual Studio 2003.NET uses .NET
1.1,
AWwhilst VS2005 uses .NET 2.0. So the question really is, what is
the
AWdifference & significance of programming C# for .NET 1.1 & .NET
2.0?
AW>

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

"Andrew Wan" <an************@hotmail.comwrote in message
news:et*************@TK2MSFTNGP06.phx.gbl...
| Thanks.
|
| My question really was, if one programmed C# for VS2003 (.NET1.1), will it
| easily migrate to VS2005 (.NET2.0)?
|

Ar eyou talking about migrating code or your knowledge?

Code should be easily migrated, from 1.1 to 2.0. IIRC all the
classes/methods from 1.1 are present in 2.0 only that some are marked as
"absolete" and will report as warning.

If you give more details of what you need to migrate more detalied info can
be provided.
--
Ignacio Machin
machin AT laceupsolutions com

[Cor Ligthert [MVP]]

Oh,

Too explain I have another expirience.

Cor

[Cor Ligthert [MVP]]

Michael,

Not so, but very close.
Just C# has the best compartability. Another .NET framework features was
changed more

I am curious, what do you mean with this *best*,

Cor

[Michael Nemtsev]

Hello Cor Ligthert [MVP],

having writing the "best" I meant that pure C# issues are easier to be fixed
in .net 2.0 rather then such thing as porting asp.net 1.1 to 2.0

CMichael,
C>

>Not so, but very close.
Just C# has the best compartability. Another .NET framework features
was
changed more

CI am curious, what do you mean with this *best*,
C>
CCor
C>
---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Andrew Wan wrote:

My question really was, if one programmed C# for VS2003 (.NET1.1), will it
easily migrate to VS2005 (.NET2.0)?

It is intended to be an easy upgrade.

Very likely it will be easy.

The stuff you did in 2003 you can also do in 2005.

You can learn the new features gradually.

There are some things that are changed in the way VS and .NET
do it, but my guess is that 5 minutes of googling can resolve
most of the problems.

I would say: GO.

Arne

[riscy]

I just upgraded to new version and upgrade relatively complex
application and found certain button control has been changed. Apart
from that, everything work just fine.

I like the generic concept, much better than arraylist.

There is extended feature within NET 2.0 and new window control.

I enchance it further with visual assist, which is worthwhile package
making coding a lot easier.

In conclusion, go for upgrade and don't look back to NET 1.1.

Now there is new NET 3.0 for Vista as well as DX10. This represent a
significant jump on OS and it would be a while for user to accept Visa,
like Win98 to WinXP. The Visa ready PC is not optimised as DX10 card
has not reach to market maturity yet.

Riscy.