[mapguide-users] What is left before MGOS 4.0 RC1

[Jackie Ng]

Hi All,

Just to provide some transparency on what is left before RC1 releases.

I am currently working on getting MapGuide Portable (formerly known as
mg-desktop) bindings working under our new way of generating language
bindings. I am having some difficulty getting the new package to work due
to cryptic missing dll errors that are cryptic because:

 a) I have no idea how to even debug a DllNotFoundException in this new
.net world. In the past when everything was still legacy .net Framework 4.x
we could run fuslogvw.exe and turn on assembly binding errors and that
would tell us straight away what the missing dlls are. In this new .net
world, fuslogvw.exe doesn't seem to work anymore and I don't know what the
new "modern .net" way to diagnose assembly binding failures is. Thanks to
Microsoft's excellent track record in naming their products and
technologies, any attempts to search for this topic naturally returns
decade-old articles and blog posts that are no longer relevant to modern
.net!

 b) The dll files .net is complaining about not being able to find *are
there*, some part of the .net runtime just doesn't want to look in the
folders I've placed these dll files in (as evidenced by monitoring the
consuming application under Process Monitor)

This is not a crucial component of MapGuide (merely a supplemental part),
so I am giving myself the rest of the week to try to solve this problem. If
I can't come up with a solution, I'll park this sub-project until after the
4.0 release.

I am also working on finishing up the new API documentation experience
where instead of our current approach of documenting a C++ API and
sprinkling .net/Java/PHP sample fragments in various class/method comments
in the hopes you'll understand how to use such a C++ class or method in a
.net/Java/PHP context, we try to provide the MapGuide API docs for every
target language in that language's natively preferred API documentation
tool of choice.

 - For .net, this is docfx (https://dotnet.github.io/docfx/)
 - For Java, this is the built-in javadoc
 - For PHP, unfortunately we'll have to put a landing page that tells you
how to re-interpret the .net or Java API docs in a PHP context. PHP
unfortunately does not support overloaded methods and our PHP binding just
smushes all of these overloads into a single method whose parameters vary
based on the overload set of parameters you're trying to use. This makes it
really hard to translate C++ API documentation across, unlike .net or Java
where everything translates 1:1. Until we can find a solution to this
problem, our C++ API docs are not translatable for PHP API documentation
generation.

I'll also be doing yet another sweep of our web tier components and will be
bundling updated versions of Apache, PHP and Tomcat where required.

On the FDO front, the PostgreSQL materialized view fix is in. Nothing else
of a show-stopping nature seems to be blocking us there, so that's all
ready to go. I will formally open a FDO 4.2 svn branch before or after this
RC1 release (haven't decided yet)

- Jackie

-- 
http://themapguyde.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20250813/9a3c3048/attachment.htm>