Changes between Version 31 and Version 32 of MapGuideRfc68

Timestamp:

Sep 8, 2009, 5:38:02 PM (15 years ago)

Author:

leaf

Comment:

--

MapGuideRfc68

@@ -32 +32 @@
 == Proposed Solution ==
 
-In order to make backward compatible with the existing MapGuide applications, !MapGuieDotNetApi.dll still exists. However, it becomes an assembly with multiple files. The primary idea is single compiling and muliple linking.
+In order to make backward compatible with the existing MapGuide applications, the old assembly!MapGuieDotNetApi.dll still exists. However, it contains some TypeForwardedTo attributes only. TypeForwardedTo attribute allows you to move a type to another assembly without having to recompile applications that use the original assembly. This is solution that Microsoft recommend to keep backward compatibility of .NET API. You can get more information about TypeForwardedTo attribute from MSDN.
 
-(a) Create the following netmodule files.
- * OSGeo.!MapGuide.Foundation.netmodule
- * OSGeo.!MapGuide.Geometry.netmodule
- * OSGeo.!MapGuide.!PlatformBase.netmodule
- * OSGeo.!MapGuide.!MapGuideCommon.netmodule
- * OSGeo.!MapGuide.Web.netmodule
+http://msdn.microsoft.com/en-us/library/ms404275.aspx
 
-(b) Create an assembly for each netmodule file in step (a). Then the following files will be created.
+(a) Create the following new assemblies.
  * OSGeo.!MapGuide.Foundation.dll: contains API in Foundation component.
  * OSGeo.!MapGuide.Geometry.dll: contains API in Geometry compoent.
@@ -48 +43 @@
  * OSGeo.!MapGuide.Web.dll: contains API in !WebApp and !HttpHandler components.
 
-(c) Create an assembly for all netmodule files in step (a). The following file will be created.
+(b) Create the following assembly by adding the reference to five assemblies above and some TypeForwardedTo attribute. For example, [assembly: TpeForwardedTo(typeof(OSGeo.MapGuide.MgFeatureService))].
  * !MapGuideDotNetApi.dll
 
@@ -62 +57 @@
 
 Supplied by Autodesk.
+
+== Addendum, Sept. 09, 2009 ==
+