Hi together,
I implemented in the last week the wwdotnetbridge to look whether I can easier execute .net code instead of asking my colleagues to program a .net exe that I must run. Local I can initiate all and it runs. Also it is running on another server from a shared path.
When try to run on a third windows 2016 server I have the following problems.
The assembly and the bridge object seems to be successful created (no error), but if I tell to "CreateInstance" the class will not find and the class object will not created with the error "Type not loaded. Please load call LoadAssembly first". I implemented the myapp.exe.config with the config written in the documentation. The GETDOTNETVERSION returns the following.
What does it mean "Calling a Service where the Class Name is different than the Service Name"
Thanks in advanced
Buss Data GmbH Swen Kleinau
There are a number of reasons this might fail, but the most common is access restrictions.
Start here:
+++ Rick ---
Hi Rick,
the solution was to install .NET Framework (latest) via web again on the Server. Normally we update and install the .NET Framework via Roles ins the Server Manager and it seems that on this way your necessary registry key will not create. After installing the .NET Framework and restart the server everything is running smoothly.
Thanks for your quick answer.
Swen
P.S. Nice to hear and again from you
Hmmm... if you used the Web Server roles to install .NET and you have an older version of server you probably have .NET 4.0 rather than 4.5 which won't work with the newest wwDotnetBridge.dll
unless you use the wwdotnetbridge_xp.dll
(which in turn does not work with .NET 4.5 assemblies).
At this point the current version of wwDotnetBridge requires .NET 4.5 and at least Windows 7 or Server 2008 R2 in order to work. Windows 7 and Server 2008 require updates to the latest .NET Runtime 4.x to work, while later versions install at least .NET 4.5 from the OS installer.
+++ Rick ---