From 443ead2fb3da3fa13136446c6608843dcd320c61 Mon Sep 17 00:00:00 2001 From: vwheeler Date: Thu, 10 Apr 2014 21:05:39 +0000 Subject: [PATCH] Correcting grammar errors and unclear expression. Author:vwheeler Date:2014-04-10T21:05:39.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1293 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../eiffelcom-wizard/com-and-eiffel/component-location.wiki | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/component-location.wiki b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/component-location.wiki index 685c4b50..487011df 100644 --- a/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/component-location.wiki +++ b/documentation/current/platform-specifics/microsoft-windows/com/eiffelcom-wizard/com-and-eiffel/component-location.wiki @@ -3,8 +3,7 @@ [[Property:uuid|083c0120-2eda-9353-ceae-f63e7f407341]]
==Types of Components== -Certainly you've heard of ActiveX, DirectX, OCX, COM+, ADO+, ASP, and other Microsoft technologies. These are all technologies that use the COM standard. This paragraph will focus on categorizing COM components according to their own properties as well as the context in which they are used. The categorization will define how the EiffelCOM wizard should be used to wrap or create a component. -The first criterion that defines the type of component is its origin: will the component be loaded in the client process (in-process) or will the component be a remote server for a distributed application (out-of-process)? In the former case, the component is compiled as a Dynamic Link Libraries (DLL) while in the latter case it is a standard executable. +Certainly you've heard of ActiveX, DirectX, OCX, COM+, ADO+, ASP, and other Microsoft technologies. These are all technologies that use the COM standard. This section focuses on categorizing COM components according to their properties as well as the context in which they are used. The categorization will define how the EiffelCOM wizard should be used to wrap or create a component. The first criterion that defines the type of component is its location at run time: will the component be loaded in the client process (in-process) or will the component be a remote server for a distributed application (out-of-process)? In the former case, the component is compiled as a Dynamic Link Libraries (DLL) while in the latter case it is a standard executable. ==In-process Components==