Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RevitTestFramework Fails to Run If an Addin is encoded in UTF-16 #70

Open
spitznagel opened this issue Apr 27, 2017 · 0 comments
Open

Comments

@spitznagel
Copy link

RevitTestFramework fails to Run If an Addin manifest is encoded in UTF-16. When run from the console using RevitTestFrameworkConsole.exe, the error message is "There is no Unicode byte order mark. Cannot switch to Unicode." There is no error message shown in the GUI.

This can be replicated by using the Autodesk.Revit2RobotConnector.Application.addin (text written below):

<?xml version="1.0" encoding="UTF-16" standalone="no"?>
<RevitAddIns>
  <AddIn Type="Application">
    <Assembly>c:\Program Files\Common Files\Autodesk Shared\Extensions 2017\Modules\RSA\Revit2RobotConnector\Revit2RobotConnector.dll</Assembly>
    <Text>Revit2RobotConnector UI Application</Text>
    <ClientId>D9AC7590-0F0C-4D41-8915-EDA2EDED1B44</ClientId>
    <Name>Revit2RobotConnector</Name>
    <FullClassName>Autodesk.Revit.UI.Revit2RobotConnector.Revit2RobotConnectorApplication</FullClassName>
    <VendorId>ADSK</VendorId>
    <VendorDescription>Autodesk, www.autodesk.com</VendorDescription>
  </AddIn>
</RevitAddIns>

I'll be submitting a pull request shortly with a proposed fix based on this StackOverflow post:

http://stackoverflow.com/questions/4568811/loading-xml-with-encoding-utf-16-using-xdocument

spitznagel pushed a commit to spitznagel/RevitTestFramework that referenced this issue Apr 27, 2017
"RevitTestFramework fails to Run If an Addin manifest is encoded in UTF-16. When run from the console using RevitTestFrameworkConsole.exe, the error message is "There is no Unicode byte order mark. Cannot switch to Unicode." There is no error message shown in the GUI."
@spitznagel spitznagel reopened this Apr 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant