Changes between Version 34 and Version 35 of MapGuideRfc68


Ignore:
Timestamp:
09/08/09 18:06:02 (15 years ago)
Author:
leaf
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc68

    v34 v35  
    6464Previously, we change the old MapGuide .NET assembly into an assembly with five netmodules. It has the following issues.
    6565
    66 * 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.
     66* 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.
    6767
    68 * 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.
     68* 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.
    6969
    70 * The solution that Microsoft recommends to keep backward compatibility of API is to use TypeForwardedTo attribute instead of netmodule.
     70* The solution that Microsoft recommends to keep backward compatibility of API is to use !TypeForwardedTo attribute instead of netmodule.
    7171
    72 So we use TypeForwardedTo attribute to keep backward compatibility of API too. I tied it. I works and resolves all of issues above.
     72So we use !TypeForwardedTo attribute to keep backward compatibility of API too. I tied it. I works and resolves all of issues above.
    7373