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

  • Thread starter Thread starter Andrew Wan
  • Start date Start date
A

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?
 
Hello Andrew,

http://msdn2.microsoft.com/en-us/library/7cz8t42e(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

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

My question really was, if one programmed C# for VS2003 (.NET1.1), will it
easily migrate to VS2005 (.NET2.0)?
 
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

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

http://msdn2.microsoft.com/en-us/library/7cz8t42e(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

AW> How different is it to program C# for Visual Studio 2003.NET &
AW> Visual Studio 2005? I know Visual Studio 2003.NET uses .NET 1.1,
AW> whilst VS2005 uses .NET 2.0. So the question really is, what is
the
AW> difference & significance of programming C# for .NET 1.1 & .NET
2.0?
AW>
Click to expand...
Click to expand...
 
..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 said:
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

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

http://msdn2.microsoft.com/en-us/library/7cz8t42e(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

AW> How different is it to program C# for Visual Studio 2003.NET &
AW> Visual Studio 2005? I know Visual Studio 2003.NET uses .NET 1.1,
AW> whilst VS2005 uses .NET 2.0. So the question really is, what is
the
AW> difference & significance of programming C# for .NET 1.1 & .NET
2.0?
AW>
Click to expand...
Click to expand...
Click to expand...
 
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?
AW> So it's like programming VS6 + MFC6. As long as I keep away from
AW> using
AW> MFC6/.NET1.1 specific stuff then code will work in future versions
AW> of VS.
AW> 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

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

http://msdn2.microsoft.com/en-us/library/7cz8t42e(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
AW> How different is it to program C# for Visual Studio 2003.NET &
AW> Visual Studio 2005? I know Visual Studio 2003.NET uses .NET
1.1,
AW> whilst VS2005 uses .NET 2.0. So the question really is, what is
the
AW> difference & significance of programming C# for .NET 1.1 & .NET
2.0?
AW>
Click to expand...
Click to expand...
Click to expand...
 
Hi,

| 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.
 
Michael,
Not so, but very close.
Just C# has the best compartability. Another .NET framework features was
changed more
Click to expand...
I am curious, what do you mean with this *best*,

Cor
 
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

C> Michael,
C>C> I am curious, what do you mean with this *best*,
C>
C> Cor
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
 
Andrew said:
My question really was, if one programmed C# for VS2003 (.NET1.1), will it
easily migrate to VS2005 (.NET2.0)?
Click to expand...

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
 
Back
Top