Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate possibility of splitting .net assemblies #18

Open
jumpinjackie opened this issue Jan 20, 2016 · 0 comments
Open

Investigate possibility of splitting .net assemblies #18

jumpinjackie opened this issue Jan 20, 2016 · 0 comments
Labels

Comments

@jumpinjackie
Copy link
Owner

Although the original intent was to keep a monolithic assembly, it does complicate things if we want to introduce mg-desktop (that builds on top of the same common core) into the mix, which hampers our re-usability story which would be restricted down to source-compatibility.

So despite the initial rejection of preserving the split-assembly idea, we should at least try to see if it is possible at a minimum to split off the (Foundation, Geometry, PlatformBase) parts of the MapGuide API and have the (MapGuideCommon, WebSupport, WebApp) part depend on it in another assembly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant