Profile Picture

Toolname ArgumentNullException after update

Posted By usyber 5 Years Ago
Author
Message
usyber
Problem Posted 5 Years Ago
View Quick Profile
Junior Member

Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)

Group: Forum Members
Last Active: 5 Years Ago
Posts: 10, Visits: 106
Dear Nevron forum,

after updating from v14 to v15 and entering the new desktop license key the code throws a ArgumentNullException for the tool names. 
Is this a license key problem or an assembly problem?

There is also a problem to get the existing tool by the name. The following expression returns null although the tool exists (The name is null).

var textTool = nDrawingView.Controller.Tools.GetToolByName(NDWFR.ToolCreateText);

Best regards,
Uli


Attachments
ToolNameArgumentNullException.png (676 views, 44.00 KB)
usyber
This post has been flagged as an answer
Posted 5 Years Ago
View Quick Profile
Junior Member

Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)Junior Member (16 reputation)

Group: Forum Members
Last Active: 5 Years Ago
Posts: 10, Visits: 106
I have solved the issue by recreating my control forms from ground up new. The problem maybe occurs due to mixture of used diagram assemblies after updating from v14 to v15. Rebuild does not solve the issue.

The deserialization statement then had a problem where all tool names within the NDiagramView.Controller.Tool collection are unnamed  (Name property = null). Every time when I opened the VS designer the Form.resx was changed and after that the tool names were invalid.

this.nDrawingView.DesignTimeState = ((Nevron.Diagram.NBinaryState)(resources.GetObject("nDrawingView.DesignTimeState"))); 


By the way.
The Nevron support was really fast and highly committed to solve the issue! Thank you, therefore.

best regards,
Uli





Similar Topics


Reading This Topic