Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
WwDotNetBridge
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Database:
MS SQL Server
Miscellaneous
Thread ID:
01662051
Message ID:
01664961
Views:
37
I updated my project with your latest update (version 6.22), both ww*.prg and .dll files. So, at least the DLL unblocking is now automatic.

>If you don't use lUseSsl then you can use the old non-.NET based email client that requires only wwipstuff.dll. However, these days almost all mail servers require TLS so I wouldn't recommend using the old one because even if you have a mail server that doesn't require SSL (rare) you should be using it because otherwise your logins to that server are not secure.
>
>The .NET config issue is a one time setting that is easy to make.
>
>DLL unblocking is automatic in the latest versions of the Client Tools so that won't be an issue anymore going forward and even then that's only a problem if you download a zip file of the internet rather than using a proper installer or local file copy.
>
>+++ Rick ---
>
>>Let me ask you one more question, to clarify something.
>>
>>If I do not use the SSL/TLS option (that is, I have loSmtp.lUseSsl = .F.), does object wwSmtp still uses the wwDotnetBridge.dll? Or this DLL is only used when the .lUseSsl is set to .T. ?
>>
>>TIA
>>
>>>I don't think you are running the right SMTP component? It says something about MAPI in the error message which the .NET component should not be using unless there's some special system configuration.
>>>
>>>+++ Rick ---
>>>
>>>>I just added myapp.exe.config and now I am getting a different error (please see attached image).
>>>>What do you think?
>>>>
>>>>>Naomi's issue was likely different that what you're looking at. For her it was finding the right EXE to add the .config file to (the launching EXE) that allows access of the wwDotnetBridge.dll over a network.
>>>>>
>>>>>To troubleshoot this start with the files locally (not on a network drive) and making sure the file is unblocked.
>>>>>
>>>>>There is more information in this help topic:
>>>>>
>>>>>Unable to load CLR Error in wwDotnetBridge
>>>>>
>>>>>
>>>>>+++ Rick ---
>>>>>
>>>>>>>>>In my own solution I just upgraded to the very latest version of Newtonsoft.Json.dll file which is version 11.02. However, I have lots of places where different versions of this dll are installed. I'm not sure where this particular version is coming from and what should I do to resolve this issue. Found a few threads on Stackoverlow with the same issue - sounds like I'm in the dll hell now.
>>>>>>>>
>>>>>>>>I suggest that you ask your question at https://support.west-wind.com/
>>>>>>>
>>>>>>>Thanks, Tore. Added a new question
>>>>>>>
>>>>>>>https://support.west-wind.com/Thread5AQ0B5KBT.wwt?rl=1#5AQ0B5KBU
>>>>>>>
>>>>>>>It is a big showstopper for me - I need to resolve it ASAP :(
>>>>>>
>>>>>>I saw your thread on .west-wind.com. I am having kind of the same problem with the wwDotNetBridge. But I don't use Newtonsoft.Json.dll.
>>>>>>Was your solution tied to this dll?
>>>>>>What was the solution?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
Previous
Reply
Map
View

Click here to load this message in the networking platform