As always, I backup 3 files before I install any addon sceneries to insure that nothing gets "missing"...
Although PHNL v1.0 installed correct, I noticed this one minor "issue" in the "dll.xml" file:
There's no "issue", at all.
I really don't know why you continue to fear our installer might do something "wrong" to your XML files. The current version of the installer use the STANDARD, OFFICIAL Microsoft XML parser to check the syntax, and to remove and add sections.
It doesn't use any code of its own so, you can be 100% sure that, if your file wasn't corrupted before, it will NOT be corrupted after. If it was corrupted before, you'll get an error message about it. Again, the error will be generated by the official MS XML parser. In this case, the file will NOT be touched.
The result of this, is that the Addon Manager section will always end up last AND, there will be not "pretty formatting" like we use to do before because, they don't have any meaning, as per official XML specification. A file doesn't need indents or lined up space to be valid. This is how the official MS handler works.
This way, we shouldn't end up in issues like having problem when trying to modify an XML that OTHER addons have formatted strangely, or by users that hand edited it in strange (although legal) ways.
Does FSX recognize the file ? Of course it does, otherwise it wouldn't load ANY addon module.
as one continues statement (string); ie. missing all the indents and carriage returns etc. So, I manually added them. Not a problem for me, but thought I should mention it in case its not suppose to be doing that.
Doesn't happen here, of course. I see correct indentation and spacing just fine, before and after installation.
But it wouldn't make any difference in any case because, as I've said, these do not matter at all in an XML file. Formatting with or without spaces/carriage returns, doesn't make the slightest difference to an XML file, the only issue it might happen, is that OTHER addons installers might get confused by this (which, as I've said, doesn't happen here).
Our installer can't be confused anymore because, by using the official MS XML parser, it should be able to add the Addon Manager section to any XML file, regardless of how funky formatted it is, as long as it's a legal one.
Note that, this is NOT a modification we introduced with PHNL installer: it's has been online in ALL installers since start of this year, and nobody had any problems with it so far. In fact, it's exactly the opposite: I find far less XML problem reports, since we changed all the installers which, as I've said, was done before PHNL release.