question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error parsing EntityName from nuspec file

See original GitHub issue

Hey,

I’m getting the following error when trying to build an installer…

[START] Electron Winstaller
  electron-windows-installer:main Using Mono: 'mono' +0ms
  electron-windows-installer:main Using Wine: 'wine' +3ms
  electron-windows-installer:main Created NuSpec file:
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
  <metadata>
    <id>wmail</id>
    <title>wmail</title>
    <version>1.2.4</version>
    <authors>Thomas Beverley</authors>
    <owners>Thomas Beverley</owners>
    <iconUrl>https://raw.githubusercontent.com/atom/electron/master/atom/browser/resources/win/atom.ico</iconUrl>
    <requireLicenseAcceptance>false</requireLicenseAcceptance>
    <description>The missing desktop client for Gmail &amp; Google Inbox</description>
    <copyright>Copyright © 2016 Thomas Beverley</copyright>
  </metadata>
  <files>
    <file src="locales/**" target="lib/net45/locales" />
    <file src="resources/**" target="lib/net45/resources" />
    <file src="*.bin" target="lib/net45" />
    <file src="*.dll" target="lib/net45" />
    <file src="*.pak" target="lib/net45" />
    <file src="Update.exe" target="lib/net45/squirrel.exe" />
    <file src="icudtl.dat" target="lib/net45/icudtl.dat" />
    <file src="LICENSE" target="lib/net45/LICENSE" />
    <file src="wmail.exe" target="lib/net45/wmail.exe" />
  </files>
</package>
 +7s
[Error: Failed with exit code: 1
Output:
Attempting to build package from 'wmail.nuspec'.
An error occurred while parsing EntityName. Line 1, position 39.
]

Has anyone else seen this? I’m using el-capitan with mono 4.2.3

Issue Analytics

  • State:open
  • Created 7 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
Bratkartofflcommented, Jun 16, 2016

It’s working for me now. Had an “&” in my package.json “description”. Removed it and everything works fine now.

1reaction
develarcommented, Jun 16, 2016

Don’t use & in the name. This issue will be fixed in electron-builder — https://github.com/electron-userland/electron-builder/issues/517

Read more comments on GitHub >

github_iconTop Results From Across the Web

NuGet: An error occurred while parsing EntityName.
Packing files from 'D:\Projects\Company\Web\bin\Release'. Using 'Web.nuspec' for metadata. An error occurred while parsing EntityName.
Read more >
Nuget feed fails to load | General Discussion Forums
[Syncfusion] An error occurred while parsing EntityName. ... Nuget.Config file which is available in the below location.
Read more >
an error occurred while parsing entity name : line 5 position 51 ...
I have tried to remove some entities in the web.config file; reinstall IIS. tried to log for event viewer log files and iis...
Read more >
An error occurred while parsing EntityName. Line 2, position 69.
You project uses some xml file, and the file has an xml error. The file is probably one that the computer has created....
Read more >
Access to Https://msblox.visualstudio.com
[MSBlox VisualStudio] An error occurred while parsing EntityName. Line 28, position 56." error when I choose that NuGet source. Azure DevOpsAzure DevOps.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found