Moving from 1.1 to 2.0
-
Had a request from a potential client were they wanted to upgrade their current asp.net application from .net 1.1 to .net 2.0. I suggested they move to .net 3.5 while they are doing it but they flat out refused it, no reason given. I believe their staff is so far behind the curve they are just now learning 2.0. How many people are still working with 1.1? Would you skip 2.0 and go to 3.5?
I know the language. I've read a book. - _Madmatt
-
Hi Mark, 1.1 is ancient history for me. I build for 2.0 on a daily base, I only go for 3.5 if the app warrants that, i.e. when new features are sufficiently relevant. and IMO LINQ is not. 3.0 is irrelevant, it is either 2.0 or 3.5
BigIntegerwill be sufficient to move a few apps to 4.0 in the near future. :)Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
Happy New Year to all.
We hope 2010 soon brings us automatic PRE tags!
Until then, please insert them manually.
You know you can use LINQ with .NET 2.0? Just set the C# 3 compiler to target .NET 2 and implement the Select/Where/etc. methods yourself (or use the Mono implementation). And there have been good
BigIntegerimplementations for .NET available for quite some time. Main reason for .NET 4 for me personally is WPF. All previous WPF versions suck at text rendering, so upgrading to .NET 4 is pretty much required if you want to use WPF. -
Had a request from a potential client were they wanted to upgrade their current asp.net application from .net 1.1 to .net 2.0. I suggested they move to .net 3.5 while they are doing it but they flat out refused it, no reason given. I believe their staff is so far behind the curve they are just now learning 2.0. How many people are still working with 1.1? Would you skip 2.0 and go to 3.5?
I know the language. I've read a book. - _Madmatt
3.5 won't install on windows server 2000. That might be a reason. A few of our clients still use server with 2000 on it so occasionally we have the same request.
-
A couple of days ago I saw a job ad in which they said they were migrating from 1.1 to 2. Strange. Only reason I can think of is that they have licences for VS 2005 but not VS 2008.
Kevin
You don't need Visual Studio to write for any version of .net.
-
Had a request from a potential client were they wanted to upgrade their current asp.net application from .net 1.1 to .net 2.0. I suggested they move to .net 3.5 while they are doing it but they flat out refused it, no reason given. I believe their staff is so far behind the curve they are just now learning 2.0. How many people are still working with 1.1? Would you skip 2.0 and go to 3.5?
I know the language. I've read a book. - _Madmatt
The only part of 3.5 I use is
HashSet<T>; if you don't need that then there's no reason to go to 3.5. -
Had a request from a potential client were they wanted to upgrade their current asp.net application from .net 1.1 to .net 2.0. I suggested they move to .net 3.5 while they are doing it but they flat out refused it, no reason given. I believe their staff is so far behind the curve they are just now learning 2.0. How many people are still working with 1.1? Would you skip 2.0 and go to 3.5?
I know the language. I've read a book. - _Madmatt
Mark Nischalke wrote:
How many people are still working with 1.1?
Not me.
Mark Nischalke wrote:
Would you skip 2.0 and go to 3.5?
Yes. So that there is no need for yet another migration for at least a few years.
50-50-90 rule: Anytime I have a 50-50 chance of getting something right, there's a 90% probability I'll get it wrong...!!
-
You know you can use LINQ with .NET 2.0? Just set the C# 3 compiler to target .NET 2 and implement the Select/Where/etc. methods yourself (or use the Mono implementation). And there have been good
BigIntegerimplementations for .NET available for quite some time. Main reason for .NET 4 for me personally is WPF. All previous WPF versions suck at text rendering, so upgrading to .NET 4 is pretty much required if you want to use WPF.Daniel Grunwald wrote:
you can use LINQ with .NET 2.0
I didn't know that; however I don't need nor like LINQ...
Daniel Grunwald wrote:
good BigInteger implementations for .NET available
Yes, however getting one within the framework is a plus.
Daniel Grunwald wrote:
Main reason for .NET 4 for me personally is WPF
I'm still keeping off WPF (read too many suckage stories in the Lounge), but it is good to know it is getting better. So I will make sure to run 4.0 when diving into WPF. Thanks. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
Happy New Year to all.
We hope 2010 soon brings us automatic PRE tags!
Until then, please insert them manually.
-
You don't need Visual Studio to write for any version of .net.
you could even do it without Notepad. :laugh: :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
Happy New Year to all.
We hope 2010 soon brings us automatic PRE tags!
Until then, please insert them manually.
-
3.5 won't install on windows server 2000. That might be a reason. A few of our clients still use server with 2000 on it so occasionally we have the same request.
-
Had a request from a potential client were they wanted to upgrade their current asp.net application from .net 1.1 to .net 2.0. I suggested they move to .net 3.5 while they are doing it but they flat out refused it, no reason given. I believe their staff is so far behind the curve they are just now learning 2.0. How many people are still working with 1.1? Would you skip 2.0 and go to 3.5?
I know the language. I've read a book. - _Madmatt
-
You don't need Visual Studio to write for any version of .net.
Yes, but there can't be many who do, say, ASP.NET without using VS.
Kevin
-
Jörgen Andersson wrote:
while VS2005 creates websites
VS 2005 can create both too. Web Apps. were added in SP1.
Kevin
-
Jörgen Andersson wrote:
while VS2005 creates websites
VS 2005 can create both too. Web Apps. were added in SP1.
Kevin
Oops. I guess I have to RTFM for the servicepacks too. Could have saved me som work some years ago.
-
Oops. I guess I have to RTFM for the servicepacks too. Could have saved me som work some years ago.
IIRC it was originally a standalone add-in for VS 2005 RTM. Then they bundled it into SP1.
Kevin
-
Had a request from a potential client were they wanted to upgrade their current asp.net application from .net 1.1 to .net 2.0. I suggested they move to .net 3.5 while they are doing it but they flat out refused it, no reason given. I believe their staff is so far behind the curve they are just now learning 2.0. How many people are still working with 1.1? Would you skip 2.0 and go to 3.5?
I know the language. I've read a book. - _Madmatt
Mark Nischalke wrote:
How many people are still working with 1.1? Would you skip 2.0 and go to 3.5?
I stopped at 1.1 and went back to 98 some 5 years ago. Now I am introducing the cool new 0x features to the team (of course, only the subset provided by VS 2010). Hopefully we'll make the switch some time this year :)
-
you could even do it without Notepad. :laugh: :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
Happy New Year to all.
We hope 2010 soon brings us automatic PRE tags!
Until then, please insert them manually.
Me, for instance.
-
Had a request from a potential client were they wanted to upgrade their current asp.net application from .net 1.1 to .net 2.0. I suggested they move to .net 3.5 while they are doing it but they flat out refused it, no reason given. I believe their staff is so far behind the curve they are just now learning 2.0. How many people are still working with 1.1? Would you skip 2.0 and go to 3.5?
I know the language. I've read a book. - _Madmatt
In my opinion a successful migration is one that builds while only adding required functionality for the build to work. Thus a 2.0 migration is also a 3.5 migration. After successful you then add new features of the new build but do not change the old ones until they are broke.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane
-
Yes, but there can't be many who do, say, ASP.NET without using VS.
Kevin
More reason not to do ASP.net. :-D
-
Server 2000 will be out of extendid support in four months, so I would imagine that would speed up migration projects quite a bit. //L
Doubtful. We still have clients working on programs in access 2.0. As long as everything works the client isn't going to upgrade.
-
Exactly. At the moment all frameworks post 2 are more extensions and enhancements, not base changes. Not sure about 4 though. Breakdown -> http://en.wikipedia.org/wiki/.NET_Framework[^]