To follow onto Bill's provided links, there is very little that has changed in regards to how you partition your n-tier application. The majority of the benefits (and what you should especially pay attention to in the Bill links provided) are the issues of packaging, deployment, versioning security. As you'll read, most of this you get for free just by packaging your components in assemblies.
-----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Joe Reich Sent: Wednesday, April 17, 2002 10:22 AM To: [EMAIL PROTECTED] Subject: [DOTNET] Architecture Question first off I have seven years XP with VB.6 and less than a week with DOTNET so bare that in mind when trying to filter through my question. A fatman told me about a 1 & 1/2 years ago while interviewing with him about DOTNET and how it basically replaces the concept of COM and with it, the concept of the DNA architecture. Since I don't know very much about DOTNET yet, how do/will we construct nTier applications with assemblies on multiple machines using distributed processing. I'm sure there is some very simple answer, but is this really a paradigm shift from the defacto architecture designs out there currently? Or was the fatman just hyped up on pre-release info. ------------------------------------- R. Joe Reich Software Analyst / Developer Central Transport International, Inc. [EMAIL PROTECTED] You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
