I think System.EnterpriseServices is the .NET framework name that is a
wrapper around the COM+ functionality.
You have many questions, and may find some answers here
http://www.msdn.microsoft.com/architecture/
Also you may want to search on MSDN website for Distributed Applications.
[quoted text, click to view] "Grzegorz Sakowski" <grzegorz.sakowski@mcm.pl> wrote in message
news:#F8LsaH$DHA.4060@TK2MSFTNGP10.phx.gbl...
> HI
>
>
> Preliminary conditions:
>
> Three-tier application
>
> Database: MS SQL Server 2000
>
> Business tier (application) works on MS Windows Server 2000
>
> User interface: windows forms and/or internet browser
>
>
>
> Used tools:
>
> VS.NET 2003 Prof (C# preferred)
>
> Visual FoxPro 8.0
>
> Access 2002
>
>
>
> Our questions:
>
>
>
> 1.. Which of the programming languages and solutions are preferred by
> Microsoft to develop multi-tier apps (working good on MS SQL7.0, SQL 2000,
> Windows server 2000 and 2003 ) ?
> 2.. Is it possible to create COM+ Server components working properly on
> Windows 2000 Server, using C#.NET as a programming language?
> 3.. Should we use COM+ technology (COM+ server-side object + Application
> Proxy on the client computer) or .NET Remoting or any other solution to
> connect UI to middle-tier ?
> 4.. Is it a good idea to create application's User Interface in Access
> 2002, or it will cause serious limitations to the application? Are there
any
> known problems with such a solution?
> 5.. Is it possible to create ADO.Recordset inside the VFP 8.0
server-side
> COM+ component and pass the recordset between tiers?
> 6.. Are Multithreaded DLLs created in VFP8.0 really multithreaded?
(After
> registering in COM+ they are featured as "Single Threaded Apartment")
> 7.. We would like to keep one data row locked during the time It's
edited
> by the user. Which locking strategy should we use? Should we "physically"
> lock records inside a transaction or create additional table and lock them
> "logically" using our own application's locking mechanism?
> Sakowski Grzegorz
>
>