Messages
Reply
Edit
Delete11:08 pm
3P21DLO9M
| From: | Stein Goering |
| To: | Rick Strahl |
I'm not saying that there isn't a problem, but I'd like to try and pin this down whatever it is...
The problem that I have is that it's working for me here in all scenarios I'm trying with and it appears that it's also working for most of your installs. There's gotta be something that's triggering the different behavior - from all that I can think of it sounds like a network share issue where one or more of the depencies are not on the local machine.
It's hard for me to see how this could be an issue - we always install our app and all its supporting files on a single box.
Have you tried putting in yourapp.exe.config file with the network override options in it (only works if .NET 3.5 and forward is installed on the machine though).
Nothing really has changed in wwDotnetBridge or wwSmtp that should have any effect. The only changes have been in wwIPStuff - mainly that I now use Visual Studio 2012 to compile the project. But behind the scenes this uses the same compiler and C runtimes as VS2010 did so I'm not sure this should really make a difference and this compiler has been used since aroun 5.60.
What does:
do wwDotNetBridgeLOCAL loBridge as wwDotNetBridge loBridge = CreateObject("wwDotNetBridge") ? loBridge.GetDotnetversion()
return on these machines, or do you even get that far? Could it be that you're loading wwDotnetBridge with other versions? What version are you expecting to load? Maybe try using "V2" (or V4) explicitly at the beginning of your app to force the desired runtime into your application.
I think it does create the oBridge object - at least in some scenarios. I'll try adding code to log the above.
I have no expectation of a version to be loaded - my code always calls wwDotNetBridge without the V parameter. Maybe I can add a startup parameter to force using V2 or V4 and see what happens.
--stein
