System.TypeLoadException at runtime

System.TypeLoadException at runtime

ollikat
Collaborator Collaborator
3,734 Views
4 Replies
Message 1 of 5

System.TypeLoadException at runtime

ollikat
Collaborator
Collaborator

Hello all!

 

Has anyone ever faced similar issue? Add-in fails to load certain type and TypeLoadException is thrown.

 

What makes this particular error quite strange is the fact that according to the exception details, the type is tried to be loaded from totally wrong assembly.

 

It says like this:

Could not load type 'namespaceXXX.ClassXXX' from assembly 'Autodesk.Bcg, Version=1.7.3.0, Culture=neutral, PublicKeyToken=d672471c03b2c408'

 

...and I can assure you that Autodesk.Bcg is not the assembly where it should find the type.

Also within same journal, a following error is logged:

 

System.TypeLoadException exception(Could not load type 'REX.ApplicationServices.RevitApplicationService' from assembly 'Autodesk.Bcg, Version=1.7.3.0, Culture=neutral, PublicKeyToken=d672471c03b2c408'.) was thrown from a handler of ApplicationInitialized event. The API event handler was registered by application AREXRevitStart (c0566ed7-4309-4082-b3ba-ea6b7b4d292a). Changes made by this handler are going to be discarded.

 

So something else also seems to be failing because of similar reason.


I'm suspecting that some 3rd party add-in has changed something and causing the behaviour. For example the Revit config file contains something related to Microsoft.Practices.Unity assemblies...not sure whether it has some effects.


This doesn't happen in my own machine, so that I could reproduce and test stuff...unfortunatelly.

 

 

Any ideas?

 

 

0 Likes
Accepted solutions (1)
3,735 Views
4 Replies
Replies (4)
Message 2 of 5

ollikat
Collaborator
Collaborator
And just a minor additional note. My add-in is loading perfectly well. This happens only in certain scenario where additional assembly/type should be loaded at run time.
0 Likes
Message 3 of 5

Anonymous
Not applicable
Accepted solution

This is very similar to the problems created with Collaboration For Revit v6 for 2015 and v2 for 2016.

 

http://knowledge.autodesk.com/support/revit-products/troubleshooting/caas/sfdcarticles/sfdcarticles/...

 

Have you checked that?

Message 4 of 5

ollikat
Collaborator
Collaborator

Thanks Peter.

 

I haven noticed that one. We need to check it out. Thanks. I'll tell you when I known whether this is related or not.

0 Likes
Message 5 of 5

ollikat
Collaborator
Collaborator

Seems that the issue provided by Peter is related. At least everything seems to be working since our customer updated the Collaboration for Revit.

Hope we don't hear anything from this anymore :-). Thank you very much!

0 Likes