December 2003 - Posts
Chapter 6 of my new book is about Data Access with ADO.NET and ObjectSpaces.
ADO.NET is only covered with a few examples how to use it from Serviced Components. ObjectSpaces has a big part in this chapter. Mapping business objects to relational data has a great fit with serviced components. After the mapping is defined, the data access code can reduced to large extends.
The new typed dataset designer with Whidbey automatically adds table relations to the typed dataset if you drag tables from the solution explorer. It's no longer necessary to add the relations manually to the designer.
Another feature of the typed dataset is that the generated class implements the new interface System.ComponentModel.IDataLoader. This new interface defines 2 methods: LoadData and SaveData. With LoadData it is possible to get the data from the database without creating a SqlConnection and SqlDataAdapter.
SaveData is not implemented with the alpha bits.
My newest book arrived: Visual C# .NET 2003 Developer's Cookbook.
This book has a cookbook-style (as the name says). Every section starts with a "You want to...", and a how-to technique and comments that follow.
- You want to create a custom proxy to intercept method calls before they are passed to the sink.
- You want to use reflection to create a plug-in architecture for your application.
- During the installation of your control, you want to automatically add the control's icon to the Visual Studio .NET IDE toolbox.
The book has 28 chapters covering a lot of different "how to" guides.
With this book I've helped out and written just a single chapter (that's why my name is not listed on the cover).
Now I'm very busy with my next book which will have 15 chapters.
Chapter 5 of my book is about network access to serviced components. This chapter is splitted into three parts: DCOM, .NET Remoting, ASP.NET Web Services.
- DCOM is still a very useful protocol to access serviced components. This protocol is fast, contexts flow across the wire...
- Checking the SOAP services checkbox with serviced components makes use of .NET Remoting. Using .NET Remoting to access serviced components has some disadvantages, e.g. contexts don't flow. The advantage of this protocol (compared to DCOM) is that clients can be installed with no-touch deployment.
- The third option is using a facade: ASP.NET Web Services. Clients can use Web Services to access the serviced components. In the backend ASP.NET again uses DCOM to access the serviced components.
In this book I will also show Indigo, and how this relates to serviced components. This is in another chapter.
COM Interop plays an important role with .NET Enterprise Services. Chapter 4 of my new book deals with COM Interop in regard to Enterprise Services.
One part of this chapter is using COM clients (VB6, C++, Scripting) accessing serviced components, the other part is about using existing COM components sharing the same contexts with .NET components.
DCOM together with other transport options will be in chapter 5.