copy code,drag or close
Web Services must be at the root of any Transactions chain.
This article covers some aspects of how COM combined with DTS to become COM+, then COM+ was re-wrapped as EnterpriseServices. All showing Vista as an evolution.
The EnterpriseServices Namespace in ASP .NET 1.0 provided much of the same functionality of COM+ did for VB6 developers, only these additional libraries are far more programmaticly accesssible. COM+ provides connection pooling for classic ADO, but as ADO.NET provides connection pooling so there is no need for that COM+ service. COM+ provides thread pool managment, so does ASP.NET.
When MTS was introduced in 1996 it provided a form a attribute based programming services where you could effectively just tick a checkbox and decide if you wanted transactions security, synchronisation. COM+ effectively incorporated these services as does the .NET framework via the WebMethodAttribute.
In reality they are the same COM+ services presented in a new programming model.
The namespaces (object method and event names) are new. Initially learning where things are is a little difficult.
Put simply from the programmers perspective it's a bit like going into a supermarket and finding most things not only moved but renamed. So a bit painful at first. As someone that started with the Visual Studio Beta release back in November 2000 adoption of .NET has seemed slow.
Its understandable why the Microsoft programming community has been a little slow in adopting .NET wholsale. It's a bit difficult to know what you are buying into until you get it home and open it.
For a long time the reality is that Microsoft is a big company made up of a number of many smaller companies working "fairly close together", so they took a while to all "get it together". Different teams did things differently
Whilst .NET 1.0 was the first major stage many of the product teams faced the tasks of re-presenting their API's in the new programming model. They found ways of re-nameing existing models so that they fit into the new framework namespaces. This process continued for years with the goal of exposing access to every part of every product through the .NET framework / programming model.
Whilst the Interoperability Namespace still appears to be essential for many applications it seems as though Vista may represent a true new opportunity to fully realise the now mature .NET code platform, lets hope so.