That might explain why the behavior seemed inconsistent.
I originally built this with the 4.0 framework - then recompiled under 3.5 - so that may also have confused the issue. I verified that I do have 3.5 on this system.
Easy enough to do that on my system, I'd prefer not to have to force it on customers.
Will do, thanks.
--stein
+++ Rick ---
I built a small assembly and am trying to load it with dotnetbridge - but am having trouble with the .NET version issue. Sometimes it runs but sometimes I get:
Could not load file or assembly 'file:///f:\wconnect\hasher.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
...even though the project's targeted framework is .NET 3.5 which should match the 3.5 runtimes loaded on my system. My bridge object shows its .NET version as 2.0.50727.5456. I see there is an Init parameter to set the version but only for V2 or V4. (And it still shows the same 2.0 even after passing in V4.) How do I get it to consistently run with my 3.5 runtimes?
Or should I just upgrade to the 4.0 runtimes? Easy to do here, but that would mean my clients would also need 4.0, right?
--stein