topic Re: AutoCAD 2020 removed useLegacyV2RuntimeActivationPolicy in acad.exe.config in .NET Forum

AutoCAD 2020 removed useLegacyV2RuntimeActivationPolicy in acad.exe.config

hierholzer — Tue, 14 Jan 2020 12:09:49 GMT

Hello,

I noticed an System.TypeInitializationException in one of our dlls from our AutoCAD extension.

The error message is:

TypeInitializationException: The type initializer for 'xxx' threw an exception. Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.

I found out that the entry

in the acad.exe.config file has been removed with AutoCAD 2020. If I add these lines again into the acad.exe.config I get no error message and everything works like before.

What is the reason that this has been removed?

Can I add this entry again without causing problems?

Thank you for your help.

Best regards,

Alex

Re: AutoCAD 2020 removed useLegacyV2RuntimeActivationPolicy in acad.exe.config

norman.yuan — Tue, 14 Jan 2020 15:17:56 GMT

The reason of that <startup useLegacy.... /> being removed is the latest versions of AutoCAD .NET API are all built on .NET Framework 4.xx, which implement different code activation policies, especially the code execution security policy.

If your DLL is quite old (built on .NET 2.xx) and requires to use legacy policy, then you need to add that into acad.exe.config (as you already did and it worked). But you need to be aware, it might compromise AutoCAD security. In spite of the saying of "if it is not broken, do not fix it", possible security breach itself is considered "broken". So, you may want to rebuild the DLL with AutoCAD matching .NET framework (4.xx), if you have the code.

Re: AutoCAD 2020 removed useLegacyV2RuntimeActivationPolicy in acad.exe.config

hierholzer — Wed, 15 Jan 2020 06:29:23 GMT

Thank you very much for your help and clarification.

Unfortunately we don't have the code for the affected assemblies. But maybe we can obtain an updated version from the respective distributors. As long as this process runs we have to use the legacy policy in acad.exe.config.

Thank you once more.

Best regards,

Alex