changing acad.exe.config to support dot net 4 breaks Vault add-in (2011)

[steve_emery]

We're in the process of rolling out an in-house application part of which is an add-in which gets netload()'d into AutoCAD 2011 in order to do some of the heavy lifting creating geometry and all that. Its been working ok on my (developer) machine, then we started to migrate everything to dot net 4, and it began failing to load into AutoCAD. Found a solution to that, which is to uncomment the below from the acad.exe.config file:

  <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0"/>
  </startup>

..and development continued in C# dot net 4, VS 2010. All was great until came to deploy it to the users: our app works, but Vault 2011 is now broken!

Any Vault command gave a non-descript dialog titled "Vault Add-In Error" saying "An error occurred during Vault operation".

Had me and our support people puzzled until we figured out that the only machine that wasn't working had the modified config file.

Question is: now what? I'd really rather not go back to the dot net 3.5 framework, that'd be a real pain; is there some other fix for getting Vault and dot net 4 to work together? Is there something missing from the config file?

All suggestions appreciated!

Steve

[caddzone]

Well, you have to go back to the supported runtime version.

In addition to Vault, there are probably other managed components

included with AutoCAD that are dependent on .NET 3.5, that'll also

fail when run on 4.0.

[steve_emery]

Bah what happened to backward compatibility and side-by-side in process stuff like talked about here

http://msdn.microsoft.com/en-us/magazine/ee819091.aspx ?

I can see a whole heap of work to get this back on 3.5; any idea how far off until framework 4 is supported?

thanks,

Steve.

[caddzone]

I have no idea when they're moving to .NET 4.0