I'm having trouble getting my commands exposed in a CONNECT vb .net addin. In V8, I would use ustnxom.exe to validate the dll file, is there anything comparable in CONNECT?
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Answer Verified By: Mike Robertson
Rod WingSenior Systems Analyst
Is there anything special I need to do to the project except modify the vbproj file after embedding the commands.xml file?
My xml file is called "Commands.xml" and here is my vbproj text:
<ItemGroup>
<EmbeddedResource Include="Commands.xml">
<SubType>Designer</SubType>
<LogicalName>CommandTable.xml</LogicalName>
</EmbeddedResource>
</ItemGroup>
My dll loads but the commands do not register, the keyin window shows no commands for my addin.
Hello,
I guess that Mike wanted to validate the add-in. The ustnxom tool recognized errors within the file commands.xml. As one has to write that manually it might happen that a simple spelling mistake leads to the result that the add-in is successfully compiling but doesn't work in MSTN.
Thats why a connect edition version of ustnxom is or would be highly appreciated. I can't understand why such an important tool has not been ported to connect edition. Are there any plans to provide a mechanism in order to avoid creating add-ins that will never work in MSTN?
Kind regards
Marc Schüller
Marc Sch?ller said:A CONNECT edition version of ustnxom is or would be highly appreciated
I agree — it remains easy to get things wrong because of minor spelling errors.
However, this thread was marked as answered several years ago. I've created a new Idea: visit the Ideas Forum and vote!
Regards, Jon Summers LA Solutions