Error during loading my plugin in Revit 2017 after Ofuscator use

Error during loading my plugin in Revit 2017 after Ofuscator use

Anonymous
Not applicable
598 Views
1 Reply
Message 1 of 2

Error during loading my plugin in Revit 2017 after Ofuscator use

Anonymous
Not applicable

Dear Jeremy,

 

First of all, thanks a lot your great help in this forum.

 

Please, let me expose to you my actual problem.

 

I created a plugin for Revit 2017 in C# with visual studio 2015.

After building the project in VS, and launching it in Revit, everything is OK.

 

BUT, when I try to use the DotOfuscator of Visual Studio to ofuscate my Dll Library project and loading it in Revit, I get the following error (see attached file).

 

I notice that I use basic ofuscator method (without signing).

 

Is it mandatory to sign my dll before trying to load it in revit, knowing I use RevitAPI(2016) and RevitAPIUI(2016) x64 signed by autodesk in sha1 ?

 

Is it mandatory to sign my dll to use correctly your API's during loading time in Revit ?

 

 

I tried, others ofuscators software but I get the same error.

 

 

Thanks a lot for your help.

 

Regards,

Albert

 

 

 

0 Likes
Accepted solutions (1)
599 Views
1 Reply
Reply (1)
Message 2 of 2

jeremytammik
Autodesk
Autodesk
Accepted solution

Dear Albert,

 

Please address your question to all, not just to me personally.

 

I hope that other people will answer as well.

 

It is not mandatory to sign your DLL. For more information on that, please read the thread on code signing:

 

http://forums.autodesk.com/t5/revit-api/code-signing-of-revit-addins/m-p/5981560

 

You know that the obfuscator renames all your classes, methods and properties, don't you?

 

Well, it looks to me as if the obfuscator renamed your main external application class as well.

 

Therefore, no class named 'App' exists anymore.

 

Therefore, it cannot be found. 

 

It no longer exists.

 

You can probably provide a list of classes and methods that the obfuscator should leave untouched.

 

Maybe you should read more aboout the basics (and dangers) of obfuscating before proceeding any further.

 

Cheers,

 

Jeremy



Jeremy Tammik
Developer Technical Services
Autodesk Developer Network, ADN Open
The Building Coder