Opened 9 years ago

Closed 8 years ago

#2521 closed task (wontfix)

Improve the .net SWIG generated PINVOKE code for better ASP.net vNext support

Reported by: jng Owned by: jng
Priority: low Milestone:
Component: Web API Version:
Severity: trivial Keywords:
Cc: External ID:

Description (last modified by jng)

A cursory play-through of the current ASP.net vNext (5.0) bits suggests that it is possible to have the .net MapGuide API working on this new platform provided a few tweaks are made to the existing SWIG generated code.

To open the possibility of ASP.net vNext Core CLR support for the .net MapGuide API wrapper, we should tweak the SWIG-generated PINVOKE code as follows:

  • Use generic Dictionary instead of Hashtable for class maps
  • #if guard .net type resolution code when throwing a .net exception or creating a .net proxy
  • Stub various classes and namespaces that are not supported in the ASP.net vNext profile. #if guard these stubs so they are skipped over when targeting the regular .net Framework.
  • Add project.json files to the DotNetApi component directories to allow easy building of aspnetcore50 targeted assemblies via kpm build

This is a forward-looking measure. Actual ASP.net 5.0 support is not in the plans for the 3.0 release.

Change History (2)

comment:1 by jng, 9 years ago

Description: modified (diff)

comment:2 by jng, 8 years ago

Resolution: → wontfix
Status: new → closed

Such work continues here: ​https://github.com/jumpinjackie/mapguide-api-bindings

Note: See TracTickets for help on using tickets.