Hi Bill, Good news for you: Microsoft is adressing both of your needs.
The COM+ "replacement" is called Indigo - it will be available with Longhorn (next version of Windows), Windows Server 2003 and Windows XP. You can read more about it at http://msdn.microsoft.com/Longhorn/understanding/pillars/Indigo/default.aspx . The second, the O/R Mapper, is called ObjectSpaces and - if I remember correctly - will be available with Whidbey (next version of the .NET Framework). You can read more at http://longhorn.msdn.microsoft.com/lhsdk/ndp/daconworkingwithobjectspacesarc hitecture.aspx Cheers, -Ingo Independent .NET and Web Services Consultant. Microsoft Regional Director - Austria. Author of "Advanced .NET Remoting". http://www.ingorammer.com Subscribe to Ingo Rammer's Architecture Briefings at http://www.ingorammer.com/NL -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Bill Bassler Sent: Monday, February 09, 2004 1:26 PM To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] Microsoft's future plans for Component Services and ORM I've been developing applications using Microsoft products for many years and with the .Net framework for 2+ years now. I've been keeping an eye on the features that are supposed to be included in Longhorn, VS.Net and the framework. It's what is don't see mentioned that disturbs me. IMO, there are some noticable gaps/oversights in what MS is promising in the near future that will affect my decision to use keep using their development tools. 1.A replacement for COM+ services. It seems to me that a first-class, .Net- based not COM-based, highly-scalable set of component services is very much needed to build applications on a par to that which can be created in other frameworks (namely Java). In order to create these OO applications we need a comprehensive set of top-notch object services (not an ADO.Net Transaction object in a Data Access block or a wrapper around COM services). 2. .Net is all about OO application designs. However, this paradigm really falls apart when it gets to the data tier because, again, a first-class Object Relational Mapper is not available out-of-box. I know that there are 3rd party solutions for this, free and not free but, come on, a company with Microsoft's $$ should at least supply a very decent ORM. They can jack up the price of VS.Net Enterprise if they did this and I doubt anyone would care. I realize that ObjectSpaces is intented to fill this obvious gap but what I've read about so far it seems like another somewhat hokey attempt to give us "something" but nothing really useful. 3. If Microsoft doesn't want to undertake these development efforts let 3rd parties do it. Why doesn't Microsoft create specifications/open up parts of the framework so that 3rd parties can create, pluggable components to fill these obvious gaps ASAP. Then at least we'll have choices as developers. I realize that no development platform is perfect. Does anyone have any hints as to if Microsoft realizes that there are problems in the tools they are providing/not providing and what they are planning to do about it? I can't believe that they don't. Opinions? =================================== This list is hosted by DevelopMentorR http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
