|
|
VC7.1 and VC8 both have good C++ compilers and STL. VC8 has the advantage of allowing me to develop native apps for WinCE, but I find it very slow.
I'm hoping that VS2005 SP1 will speed it up.
|
|
|
|
|
TomM wrote: I'm hoping that VS2005 SP1 will speed it up.
Ah.. refreshing. An optimist in the crowd!
--
Painstakingly Drawn Before a Live Audience
|
|
|
|
|
At my work we port all our applications but we get some trouble with VS2005 and after found and apply some hotfixs we preffer to still use the VS2003 for some time and wait for the promised SP1.
... and not only the SP1 of the VS2005 ... we need the SP1 for the .NET framework 2.0 too.
Just for the records:
Some time ago when I convince my boss to use VS2005 because it was more productive I don't know how to explain he why I was restarting VS all the time because the Edit and continue or the inherited forms don't work fine in that release. So I lost the confidence of my boss and that is now fun.
And now, the last surprise, they call the complements of the .NET 2.0 for windows vista: .NET 3.0 .. This is too much for me !!! I can't belive that if the release use the CLR 2.0 how they can call it .NET 3.0.
I can't found any article that said that this one was a good decition. The community hate this idea and MS only move forward and forget the most important part of their success HEAR THEIR USERS
Cheers
Marcos
|
|
|
|
|
|
hahaha ;)
Great news !!!
Cheers
|
|
|
|
|
|
LOL.
Nice.
-----------------------------
"I don't know half of you half as well as I should like; and I like less than half of you half as well as you deserve" - Bilbo Baggins
|
|
|
|
|
For my part, I prefer working with VS 2005 than 2003: I didn't run into any trouble with 2005 (maybe I will) and I really appreciate the Windows Forms designer being more stable or at least providing valuable trace when a problem occurs.
But I too agree with the fact .NET 3.0 is a bad idea. Basically, it's just new apis exposed through regular CLR 2.0 ; why didn't MS keep the WinFX name? It sounded quite good.
When people like me (and like I think you are), ie interested in latest MS products, get informated, it's really hard to remember that such a product or an api is not new but has just seen its name changed twice or three times (Indigo, Avalon becoming WCF, WPF part of WinFX then .NET 3.0)...
-- modified at 14:54 Tuesday 25th July, 2006
I was wondering, do you use VB.NET? C# editing experience is far more stable than th VB one (mainly due to the background compilation continuously occuring behind the scene, but that existed with VS2003).
|
|
|
|
|
Yes Olivier I agree with you about the designer and all the features =) I think that is the best IDE in the world... I Know that they need to finish the WinVista and all that stuff (in what I preffer to not think now) but they MUST release the HotFix and SP1 now to all the users !!
I´m using VB.NET and the EDIT and CONTINUE simplly only work 1 of 4 times, so i can't use that Excellent feature because it don't work. For the custom controls and a lot of others framework projects I use C# and you are right is a lot more stable and the Intellisense is a lot superior.
Cheers
Marcos
|
|
|
|
|
Marcos Meli wrote: only work 1 of 4 times, so i can't use that Excellent feature because it don't work.
Oh boy. A "feature" that works as reliably as rolling the dice.
How exactly can you determine that the feature is excellent if it doesn't work.
|
|
|
|
|
If they wanted to use the .NET name with WinFX just call it WinFX.NET and make it an add on like atlas. .NET 3.0 is just confusing.
|
|
|
|
|
I am using .NET 2.0, but not VS 2005. As a side contractor my development budget is fairly small so I have been using SharpDevelop for all my .Net development, which is yet to be a problem.
|
|
|
|
|
diilbert wrote: so I have been using SharpDevelop for all my .Net development, which is yet to be a problem.
I like its support for Boo[^].
|
|
|
|
|
Nemanja Trifunovic wrote: I like its support for Boo
Boo looks nice. Not scary at all.
Thanks,
Alvaro
The bible was written when people were even more stupid than they are today. Can you imagine that? - David Cross
|
|
|
|
|
Why can't you use the VS 2005 Express edition, which is free?
|
|
|
|
|
It would be great if all old applications where migrated to new tecnologies. But thatas not what happens. All companies have their budgets and migrating its not priority ..
If the old app still works , then its never migrated.
Thats why we still have apps in COBOL and some ohter old languages.Thats why .net 1.1 will never die.
Microsoft Certifed Professional
|
|
|
|
|
Well, until they figure out they can save tons of money in the long run by getting rid of the boat anchers.
It costs quite a bit to get a programmer for that old system. Also, to maintain an enviroment where old apps can run (because everything breaks eventually) is no easy chore, try getting parts for your old Modal A...
|
|
|
|
|
Yes, until your boos figure out that the ported application fails a lot more than the old one because the Framework is buggy (What cost more so ?)
And you must know how hard is to explain to your users or your boss that the problem is not your, is a Microsft bug. Maybe be a bit more conservative is not a bad choice (I change my philosophy about this after port a really big application from .NET 1.1 to 2.0)
Best Regards
Marcos
|
|
|
|
|
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.
|
|
|
|