|
I hate the convention and the schedules of the Service Packs for VS2005 and .NET 2.0 we are using .NET 1.1 and every time that we try to port it to 2.0 we get some extrange conditions, and after search a bit, we found that are errors that M$ publish in the KB but they don't release the hot fixs, so you need to talk 3 times a week to ask for each path. Incredible !!!!!!
Here is a petition to MS to name back the name of the framework, I know that at this time they don't change it back, but when they lose the support of the community in the future maybe can fire some marketers based on the petition  ;P
http://www.petitiononline.com/winfx/petition.html[^]
Cheers
Marcos
|
|
|
|
|
Well as for me net 1.1, theres so much to learn still before i feel comfortable moving over to the dark side. which is .net 2.0 and 3.0
Well mainly because i dont have money for vs 2005.
Other than that .net 1.1 still rocks baby !
|
|
|
|
|
Trance Junkie wrote: Well mainly because i dont have money for vs 2005.
The Express Editions[^] are for free.
Regards
Thomas
Disclaimer:
Because of heavy processing requirements, we are currently using some of your unused brain capacity for backup processing. Please ignore any hallucinations, voices or unusual dreams you may experience. Please avoid concentration-intensive tasks until further notice. Thank you.
|
|
|
|
|
Thanks for the tip but i have Express Editions,
|
|
|
|
|
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.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Well im getting my copy of vs 2005 soon
|
|
|
|
|
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
