Delphi, whert arth thou?
Just been to a 4 days course on C# last week. It was fun but at the same time frustrating. Fun in the sense that Microsoft is really putting all energy on developing it's developers tools like Visual C# which is the tool used on the course. Frustrating in the sense that it feels like on today's stand on "Code Gear", it would like be another "Inprise"-case. And this is sad since i have been following Delphi and became such a "disciple" that it's quite hard to abandone a well mastered masterpiece.
I am not a hard core fanatic on a special language on a professional point of view but like others i have my favorites. I worked with Microsoft's Visual C++ before with MFC in version 4.0 and at that time it felt endless working with GUI and all the Ctrl+W keyboard strokes. Microsoft has really gone far with the GUI thing since then. With .NET 2.0 controls, it has gone even better--- at first glance anyway. And .NET 3.0 is on it's way...
Then i'm wondering, how would "Code Gear" cope up with this? Anxiously after the course, I rush onto my comp and started D2005 and tried to create all the exercises on D2005 WinForms part--- but to my disappointment, D2005 does not support .NET 2.0 ( i don't find any patch anyway --- the latest update i have is 3.0 and this couldn't be old ). I encountered this un-informative error message. If you find a solution to this error, please don't hesistate to send me some tips.
My point is, as a developer, if i don't get the right tool then i certainly switch to another which gives me the result i want to achieve. And if "Code Gear"'s solution to this is D2006, then it's a tough decision 'cause Microsoft's strategy is opening it's dev tools to the public with the release of the express solutions.
Anyway, let's just take it this way, it's good to have a lot into your luggage than nothing at all.
I am not a hard core fanatic on a special language on a professional point of view but like others i have my favorites. I worked with Microsoft's Visual C++ before with MFC in version 4.0 and at that time it felt endless working with GUI and all the Ctrl+W keyboard strokes. Microsoft has really gone far with the GUI thing since then. With .NET 2.0 controls, it has gone even better--- at first glance anyway. And .NET 3.0 is on it's way...
Then i'm wondering, how would "Code Gear" cope up with this? Anxiously after the course, I rush onto my comp and started D2005 and tried to create all the exercises on D2005 WinForms part--- but to my disappointment, D2005 does not support .NET 2.0 ( i don't find any patch anyway --- the latest update i have is 3.0 and this couldn't be old ). I encountered this un-informative error message. If you find a solution to this error, please don't hesistate to send me some tips.
My point is, as a developer, if i don't get the right tool then i certainly switch to another which gives me the result i want to achieve. And if "Code Gear"'s solution to this is D2006, then it's a tough decision 'cause Microsoft's strategy is opening it's dev tools to the public with the release of the express solutions.
Anyway, let's just take it this way, it's good to have a lot into your luggage than nothing at all.
Kommentarer