|
Chris Maunder wrote: Oh, let it go. Just walk away from 1.1 like it's a bad dream and open your eyes to trees and flowers and sunshine and all things happy with 2.0.
And all the new bugs in the VS2k5 IDE, on top of the old leftover bugs from VS2k3 that never got fixed.
*grumble*
Grim (aka Toby) MCDBA, MCSD, MCP+SB
SELECT * FROM users WHERE clue IS NOT NULL
GO
(0 row(s) affected)
|
|
|
|
|
I still have a bit of legacy 1.1 stuff but everything new is now done in .NET 2.
Generics is just too big of a draw to stick with 1.1. The toolkits such as the Smart Client Software Factory and Enterprise Library 2.0 make .NET 2 very attractive, despite the obvious flaws in VS2005.
|
|
|
|
|
I wish my "legacy" apps were 1.1; We still have a lot of VB6 floating around.
|
|
|
|
|
.net 1.1 Can't be labeled as legacy yet Surely 
I class VB5 as legacy
a fool will not learn from a wise man, but a wise man will learn from a fool
|
|
|
|
|
obvious flaws?
I've been working on VS 2005 for quuite sometime... I honestly HOPE that Microsoft keeps this standard with their next releases! But then again, maybe I haven't discovered what you did. Can you point some out please?
Cheers
Steve
Got a coding problem? Hand it to the CodeDevil!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
