1

Resolved

Non XML issue with BOM

description

Hello,

We've recently looked at using ConfigGen to generate Environment.cmd files, using the remove root element option.

However we've noticed that the files get saved down with a BOM (byte order mark) which when executed in command prompt throws a fit, as it tries to execute the BOM, setting the error level 9009.

Can you add an option to specify encoding/remove this BOM please?

Thanks,

Vince

comments

rob_levine wrote Jul 21, 2014 at 5:27 PM

Hi Vince,

I've just checked in a change that should let you specify the output encoding when using --remove-root-element.

Just use: --output-encoding <encoding>

where <encoding> is:
A : ASCII
U8 : UTF-8
U16 : UTF-16 (LE).

In your case, using "A" should work.

I haven't prepped this as a release yet, as I wanted to get your feedback on if it works.
If you get the latest code, as of commit cef31deb54d2 and build it in Visual Studio 2010 or higher, you should be able to test this change out.

Thanks,

Rob

niventc wrote Jul 22, 2014 at 12:06 PM

Hello,

Just gave it a whirl and it worked.

Let me know once the release is ready and we'll start using it.

Thanks very much,

Vince

rob_levine wrote Jul 28, 2014 at 9:10 PM

Hi Vince,

Apologies for the delay - I haven't forgotten that I need to package a new release for you, but I'm waiting on confirmation that another bug has been fixed.

Cheers,

Rob

rob_levine wrote Jul 29, 2014 at 7:57 AM

Hi Vince,

This has now been packaged as a release: v1.0.7. It is available for download from the "Downloads" page here on CodePlex, or via NuGet.

Kind Regards,

Rob