com
-
Well, i would like to get into com, but now with the CLR and c#, is it wise to spend some time learning it? is com in the way out or is just getting behind the scenes, as it happens in vb? thanks Gabriel dont worry, drink happy
-
Well, i would like to get into com, but now with the CLR and c#, is it wise to spend some time learning it? is com in the way out or is just getting behind the scenes, as it happens in vb? thanks Gabriel dont worry, drink happy
How could I *not* reply to someone calling themselves Lemmy. Yeah !!!! I am persoanlly finally taking the time to learn ATL. I believe that it will take time for people to move to the .Net way of doing things, and people will still use COM. I'm keen for anyone who has knowledge to tell me otherwise, but it seems to me that the worst that can happen is that I'll have another skill, and it's likely that any .Net info on whatever they use to replaced COM will be presented in terms of COM, so I'll find it easier to understand ;0 Christian #include "std_disclaimer.h" People who love sausage and respect the law should never watch either one being made. The things that come to those who wait are usually the things left by those who got there first.
-
How could I *not* reply to someone calling themselves Lemmy. Yeah !!!! I am persoanlly finally taking the time to learn ATL. I believe that it will take time for people to move to the .Net way of doing things, and people will still use COM. I'm keen for anyone who has knowledge to tell me otherwise, but it seems to me that the worst that can happen is that I'll have another skill, and it's likely that any .Net info on whatever they use to replaced COM will be presented in terms of COM, so I'll find it easier to understand ;0 Christian #include "std_disclaimer.h" People who love sausage and respect the law should never watch either one being made. The things that come to those who wait are usually the things left by those who got there first.
I think that COM will lose some of its glory in .NET world .. I tried to think of those situations where i will go back and implement *classical* COM and then deploy it in .NET application: 1- For real-time application when i need ultra-fast execution 2- Provide a means to deal with the legacy code that i am not willing to port to .NET Developers who seek performance will find themselves working with ATL, STL, WTL ..(not MFC of course)so, i expect a long life for those template-based libraries :suss: Well, you are right, people will take time to move to .NET .. but learning COM\ATL takes time too and you need to think which is better for you: studying .NET stuff which needs a lot of time to master or COM\ATL now and then go for .NET later when it is released !? Rafik
-
I think that COM will lose some of its glory in .NET world .. I tried to think of those situations where i will go back and implement *classical* COM and then deploy it in .NET application: 1- For real-time application when i need ultra-fast execution 2- Provide a means to deal with the legacy code that i am not willing to port to .NET Developers who seek performance will find themselves working with ATL, STL, WTL ..(not MFC of course)so, i expect a long life for those template-based libraries :suss: Well, you are right, people will take time to move to .NET .. but learning COM\ATL takes time too and you need to think which is better for you: studying .NET stuff which needs a lot of time to master or COM\ATL now and then go for .NET later when it is released !? Rafik
Your statements assume that .NET will be embraced by many companies. I'm not saying that I don't think .NET will take off, but "software as a service" sounds similar to the business models of ASPs (Application Service Providers). ASPs were hyped up about a year ago, but many didn't survive due to lack of customers. I'm taking a wait and see approach before investing too much time in the .NET SDK, although I'm going to be playing with it a bit to become familar with it in case .NET does hit a home run.
-
Your statements assume that .NET will be embraced by many companies. I'm not saying that I don't think .NET will take off, but "software as a service" sounds similar to the business models of ASPs (Application Service Providers). ASPs were hyped up about a year ago, but many didn't survive due to lack of customers. I'm taking a wait and see approach before investing too much time in the .NET SDK, although I'm going to be playing with it a bit to become familar with it in case .NET does hit a home run.
My thoughts exactly. I know of a couple of companies locally doing n teired apps with VB on the presentation layer and ATL for the rest - they are still training people in ATL and not planning on moving to .Net. Why should they discard their investment in ATL when it still does what they want ? It may become a compelling argument in time, it won't happen overnight though. Christian #include "std_disclaimer.h" People who love sausage and respect the law should never watch either one being made. The things that come to those who wait are usually the things left by those who got there first.