All code written by using the .NET Framework tools and designed to run under the Common Language Runtime (CLR).Other applications that run on the Windows/COM platform, such as COM components and Visual Basic 6 applications, are known as unmanaged code.
When this object is passed between components, a proxy object is created in the caller’s process. This object shows the client the same interface as the remote object and enables the client code to make method calls as though it were calling a local object. When the caller makes method calls on the proxy object, the .NET Remoting infrastructure passes those calls to the remote server, and the call is carried out in the server’s process.
A Marshal-by-Value object is passed between components, by serializing a complete copy of the object and passing it through the remoting channel to the caller.
A project that packages assemblies that might be shared by other setup projects. When this project is built, it will generate an .msm file that can be added to other setup projects. The .msm file contains all the files, Registry settings, and setup configuration for installing the assemblies. They must be used from within a setup project and cannot be run alone.
A feature of Windows Component Services that enables applications to make asynchronous calls on components. The information about the call is placed into a message queue (persistent storage) on the server, and the component processes each message when it is available. This is useful for making calls on an application on a remote server that might not always be online or for balancing peak workloads. Messages wait in the queue until the server component is connected and is able to process them. Also called queued components.
A set-up file that will install by using theWindows Installer (msiexec.exe). This is the customary way to package and install a Windows application on Windows; you can also use it to package and deploy an ASP.NET application to a web server or group of web servers. MSI files can also be published to Add or Remove Programs in the Control Panel console and deployed by using Active Directory Software Deployment Policies.
In a three-tier application design, code is separated into a user interface tier, a business logic tier, and a data access tier. The middle-tier components provide the business logic of your application.
Test data that is used to ensure that those items that vary from culture to culture, such as dates, currency, and separator characters in numbers are interpreted correctly by your application.
A property of the System.EnterpriseServices.ContextUtil class that indicates the object’s “vote” (commit or roll back) on the transaction status.
A name that describes the .NET Framework capabilities to interoperate with COM components and to take advantage of the features of Windows Component Services.
This security mechanism, based on COM+, is provided for compatibility with pre-.NET code, as well as to provide an easy way to implement role-based security when roles are not defined as Windows groups. This feature of Windows Component Services that enables you to define which groups of users (roles) are allowed to make calls on a component, class, or method. You can apply role-based security in source code through properties and methods of the System.EnterpriseServices.ServicedComponent base class; you can apply a SecurityRoleAttribute to your class; or you can assign roles administratively through the Component Services management console.
See regasm.exe.
See InstallUtil.exe.
See regsvcs.exe.
Objects that enable application developers to use a familiar object reference approach when making interprocess communication between two applications.
An object that is used to validate against password-based authentication schemes such as basic, digest, NTLM, and Kerberos authentication.
One of the base classes in the System.Xml namespace, this collection holds groups of related element nodes.
An in-memory construction of code and data that can be created from a class.
A feature of Windows Component Services that helps to improve performance and scalability by maintaining a defined number of objects in memory at all times, ready to be activated when a calling application makes a request. You can tune application performance by adjusting the minimum and maximum number of objects to be maintained by the pool.
This ADO.NET class enables you to create a connection to databases such as Access, Oracle, or DB2 by using an OLEDB provider. Use this class for accessing older versions of Microsoft SQL Server (version 6.5 or earlier).
This ADO.NET class enables you to connect to a data source and execute a query to return records and fill a DataSet. If the user makes changes to the data in the DataSet, the DataAdapter is also responsible for sending the appropriate insert, update, and delete statements to the database.
This ADO.NET class enables you to process a forward-only, read-only resultset that is returned from a database query.
This ADO.NET object contains one error message that has been returned from the database server. Error objects are accessed through the Exception object’s Errors collection.
This ADO.NET object represents a specific type of exception that is thrown when an error occurs during database access.
This ADO.NET object holds information about a parameter sent to a stored procedure.
This ADO.NET object ensures that two or more database commands are executed successfully before the changes are committed permanently to the database. If any of the commands fail, all intermediate results are rolled back.
A method of the .NET Framework ServiceBase class (the class that all Windows service applications inherit from). You can add code to this event procedure to determine what happens when the service is started up.
A method of the .NET Framework ServiceBase class (the class that all Windows service applications inherit from). You can add code to this event procedure to determine what happens when the service is stopped.
OPENXML provides a rowset representation of the data in an XML Document, which can be used anywhere in a SQL Server 2000 query that tables or views would normally be used. This clause enables SQL Server to load XML data into database tables.