|
I doubt the framework is that buggy. I call that fear of change
And porting between .NET 1.1 and .NET 2.0 is easy: Recompile the app on the new framework, fix the warnings and recompile again. Now you're up and running on the new framework
WM.
What about weapons of mass-construction?
|
|
|
|
|
mmm, are you completely sure that the framework is not buggy ???
And about the por of an application of .NET 1.1 to 2.0:
- How many lines has your application (at work we port an application with more than 100.000 lines of code, some ones generated with CodeSmith)
- Your applications use multiple threads and catching
- Your applications are ASP.NET or Winforms (we are dealing with a big WinForm app here)
- Do you use inherited forms ?
- Do you use your custom controls ?
- And, how I said before, we finish to port the app (this is not fear to change ) and the bugs beggin to appear
I want to change the .NET 2.0, I love the new features, I was who convince to my boss to use it, and know I must said that is buggy until today.
Best Regards
Marcos
|
|
|
|
|
In your Company .net 1.1 will never die, because it never lived here. The same as MS Java, J#, .net 2.0 and other Buzzwords from Redmond.
I believe we stick to MFC as long as we can debug.
In Germany the actual offical retirement age for me will be 67, but I think 'inflation' will get to 70.
Greetings from Germany
|
|
|
|
|
rodrigo diniz wrote: All companies have their budgets and migrating its not priority
True, I work on a 280,000-line project in VC6 & MFC in a team of one - there's no way I can spend time to port it, but any new code will be written in VS2005, probably in C++ as I'm reluctant to go to C#.
PS - I really hate the deep and non-aligned indentation in code generated automatically by the VS2005 IDE.
Asynes yw brassa ages kwilkynyow.
|
|
|
|
|
I disagree.
My native (polish) poet once asked us "not to bury the altars of the past". Unfortunately in this job you have to disobey this rule many times. Literally, you sometimes should bury, step on and disregard old techniques. I'm currently working on a project that aims to build a bridge between present data interchange formats and those, that were used 20 years ago. I encountered many peculiarities and bizzare things when I first saw those formats. They reflect programming spirit of eighties. Lack of standardisation, no things like unicode etc. Thats obvious, you can say. My point is, what world would look like if all programmers would use their own standards and old techniques. World should evolve constantly and I personally see a giant leap in .net 2.0.
Greetings from Poland
Felin
|
|
|
|
|
I'm now fully using .NET 2 and VS2005.
No more messing about with the older technologies. .NET 2 has too many advantages to not use it for all development going forward.
|
|
|
|
|
There are quite a few application which I build using .NET 1.1, I still need to support those.
Some of them are already available for .NET 2.0, some of them will be soon. But I think I will leave some on the old version of the framework. These apps are not worth the effort of upgrading the code.
But I will start using .NET 2.0 for all new apps I create
WM.
What about weapons of mass-construction?
|
|
|
|
|
What about the computer you use with VS2005? I mean I've installed it in P4 with 512 Mb RAM and the IDE is quite slow. I've also read that with 1Gb it's not enough.
Marc.
... she said you are the perfect stranger she said baby let's keep it like this... Dire Straits
|
|
|
|
|
I'm using VS2005 on a 2Ghz Pentium-M laptop with 2Gb of ram myself and it runs and compiles a lot faster than any of the other IDE's installed on my system. Maybe I'll take one of the sticks of ram out of my laptop and see if it has any major problems with the speed as I've read a lot of people have said it was slow.
|
|
|
|
|
Ok thanks. I'll look for the 2Gig RAM because it seems is the most important thing in this case.
Marc
... she said you are the perfect stranger she said baby let's keep it like this... Dire Straits
|
|
|
|
|
marcdev wrote: 've installed it in P4 with 512 Mb RAM and the IDE is quite slow. I've also read that with 1Gb it's not enough.
That is correct. I have it on my laptop with 512 MB and on my desktop with 1Gb. Neither are fast enough. 2Gb would be comfortable I gather.
Kevin
|
|
|
|
|
marcdev wrote: I mean I've installed it in P4 with 512 Mb RAM and the IDE is quite slow.
Just get a decent machine like this one[^] (preferably with at least 32 processors and 128GB RAM but 64 CPU/256 GB RAM would be better) and enjoy 21st century - the time when runtime speed doesn't matter - it is all about programmers' productivity.
|
|
|
|
|
Nemanja Trifunovic wrote: Just get a decent machine like this one[^]
Does it come in a desktop model?
You may be right I may be crazy -- Billy Joel --
Within you lies the power for good, use it!!!
|
|
|
|
|
It depends on how big your desktop is...
--
This Episode Has Been Modified To Fit Your Primitive Screen
|
|
|
|
|
Ok. With this one it'll be enough ... I'lll order it
... she said you are the perfect stranger she said baby let's keep it like this... Dire Straits
|
|
|
|
|
Use 2005 Exclusivly now.
Running on 3.4 ghz P4, 550J Prescot with 2 Gigs of memory.
It still slows every once in awhile, all MS products are resource hogs.
Matthew Hazlett
Sometimes I miss the simpler DOS days of Borland Turbo Pascal (but not very often).
|
|
|
|
|
I had that problem too, changed my computer by adding more memory.
but 1 GB isn't much of a problem, I even run VS2005 on my notebook a Pentium M 1.7 with 512MB memory.
WM.
What about weapons of mass-construction?
|
|
|
|
|
On this Pentium D 950 with 4GB RAM and Windows XP x64, VS2005 runs as responsive as Notepad.
The only problem is you get so used to it being so responsive that when you are forced to use it on a less powerful machine then all the little performance annoyances drive you mad.
|
|
|
|
|
Nice box !!! I'd like to have one like this, even though I get disappointed when using other computers.
... she said you are the perfect stranger she said baby let's keep it like this... Dire Straits
|
|
|
|
|
Michael P Butler wrote: No more messing about with the older technologies. .NET 2 has too many advantages to not use it for all development going forward.
Don't forget the bugs in the framework and VS2005 this is a good reason to keep using the VS2003 and .NET 1.1
I love 2.0 but I must wait to the SP1 to use it at work.
Cheers
|
|
|
|
|
Marcos Meli wrote: Don't forget the bugs in the framework and VS2005 this is a good reason to keep using the VS2003 and .NET 1.1
I haven't found anything that break anything I need. Okay, VS2005 can be a little unstable at times but I've learnt to work round its quirks.
The excellent Enterprise Library 2.0, Smart Client Software Factory and the Composite UI Application block more than make up for the shortcomings of VS2005 pre-servicepack.
|
|
|
|
|
Michael:
We have a lot of trouble with inherited win forms, some thread code, for example some days ago I found in a blog that there is a bug in the string.IsEmptyOrNull of the .NET 2.0. Do you think that this is not buggy. BTW I love .NET 2.0, I only want and need the SP1 !!! In my dialy work we don't need atlas, WPF, WCF .NET 3.0 at all. We only need the SP1 to release our bussines app in the company we are still using .NET 1.1.
Some time ago when we release the ported version, time by time the application hang ups and shows an screen with an error and a "SEND TO MICROSOFT" button... WTF !!! send to MS ?? is our program !!, we are using Application.ThreadException why this append ?. In the previous version all the errors pass for the seted handler. We can't accept it at all.
Our application has more than 100.000 lines of code we can debug it again and found that there is a problem in the framework.
Best Regards
Marcos
|
|
|
|
|
I couldn't agree more !!!
generics, anonymous methods, refreshed remoting and ADO.NET are truly useful, those are not just cheap slogans.
Dotnet 3.0 will be even more powerfull. I've seen demo version and can't wait to see final one.
Felin
|
|
|
|