Changes between Version 36 and Version 37 of MapGuideRfc68

Timestamp:

Sep 8, 2009, 6:22:01 PM (15 years ago)

Author:

leaf

Comment:

--

MapGuideRfc68

@@ -64 +64 @@
 Previously, we change the old MapGuide .NET assembly into an assembly with five netmodules. It has the following issues.
 
-* Generally, the assembly with multiple netmodules is applied to the assembly whose netmodules has no dependencies. In MapGuide, Geometry netmodule depends on Foundation netmodule and !PlatformBase netmodule depends on Foundation and Geometry netmodules.
+ * Generally, the assembly with multiple netmodules is applied to the assembly whose netmodules has no dependencies. In MapGuide, Geometry netmodule depends on Foundation netmodule and !PlatformBase netmodule depends on Foundation and Geometry netmodules.
 
-* If the applications based on MapGuide .NET API want to do some changes to their API and they use !TypeForwardedTo attribute to keep backward compatibility of their .NET API, it will not work because there is one bug in .NET framework 2.0. This bug results in !TypeForwardedTo functionality doesn't work with assebmly with multiple netmodules. There is no public document for this bug. However, I already got confirmation from Microsoft.
+ * If the applications based on MapGuide .NET API want to do some changes to their API and they use !TypeForwardedTo attribute to keep backward compatibility of their .NET API, it will not work because there is one bug in .NET framework 2.0. This bug results in !TypeForwardedTo functionality doesn't work with assebmly with multiple netmodules. There is no public document for this bug. However, I already got confirmation from Microsoft.
 
-* The solution that Microsoft recommends to keep backward compatibility of API is to use !TypeForwardedTo attribute instead of netmodule.
+ * The solution that Microsoft recommends to keep backward compatibility of API is to use !TypeForwardedTo attribute instead of netmodule.
 
 So we want to use !TypeForwardedTo attribute to keep backward compatibility of MapGuide .NET API too. I tied it. I works and resolves all of issues above.