Update-Mono generates invalid [Content-Types].xml

[fasterthanlime]

[Content_Types].xml

<?xml version="1.0" encoding="utf-8"?>
<Types xmlns="http://schemas.openxmlformats.org/package/2006/content-types">
  <Default ContentType="application/vnd.openxmlformats-package.relationships+xml" Extension="rels" />
  <Default ContentType="application/octet" Extension="nuspec" />
  <Default ContentType="application/octet" Extension="bin" />
  <Default ContentType="application/octet" Extension="dll" />
  <Default ContentType="application/octet" Extension="pak" />
  <Default ContentType="application/octet" Extension="exe" />
  <Default ContentType="application/octet" Extension="dat" />
  <Default ContentType="application/octet" Extension="" />
  <Default ContentType="application/vnd.openxmlformats-package.core-properties+xml" Extension="psmdcp" />
  <Default Extension="diff" ContentType="application/octet" />
  <Default Extension="bsdiff" ContentType="application/octet" />
  <Default Extension="shasum" ContentType="text/plain" />
</Types>

See this gist for full stack trace, it's the System.Xml package complaining, while Nuget is trying to ensure we have a valid manifest.

I have no idea how it's generated, if someone knows, all help is appreciated, otherwise I'll probably keep digging tomorrow.

(My instinct is that this line (the one after 'dat') should probably just not get generated at all?)

[fasterthanlime]

Disclaimer: I've built my Update-Mono on OSX (with Xamarin Studio), had to call ILRepack by hand, entirely possible that I messed something up, so, probably a good idea to reproduce with official Update-Mono.exe whenever #519 lands

[fasterthanlime]

Found a similar issue: cronofy/cronofy-csharp#2

[fasterthanlime]

This doesn't look like a Squirrel.Windows issue, rather it's a combination of Nuget's behavior on Windows, and grunt-electron-installer's default template.nuspec which includes extension-less files like LICENSE.

Closing to avoid clogging Squirrel.Windows issues