There are some crippled version of the .Net 4 framework out there that won't work.
I don't know how you've implemented your WW stuff (I'm using 6.x of Rick's WW Client Tools) but I was also running into issues where the framework wasn't present. I use it for SMTP and FTP. One thing I changed relatively recently, based on Rick's recommendation, was to load the framework on application startup. Previously I was invoking it when firing up an email object or ftp form. According to Rick, the instance of the framework object is scoped to the application so any attempts to create another one will just refer back to the original instance. Also, based on his samples I added this to my app startup:
TRY LOCAL m.loBridge AS [wwDotnetBridge] DO wwDotnetBridge m.loBridge=CREATEOBJECT([wwDotnetBridge],[V4]) CATCH TO m.loError40 TRY m.loBridge=CREATEOBJECT([wwDotnetBridge],[V2]) CATCH TO m.loError20 FINALLY ENDTRY FINALLY IF VARTYPE(m.loError40)<>[O] AND VARTYPE(m.loError20)<>[O] DEBUGOUT m.loBridge.GetDotnetVersion() ELSE IF _vfp.StartMode=0 MESSAGEBOX([dotnet CLR error],MB_OK+MB_ICONEXCLAMATION,[My Really Cool VFP Application]) ENDIF ENDIF RELEASE m.loBridge ENDTRY
So now when that XP or other ancient version of Windows runs my app, the user gets a little message. Obscure to them but I know right away that they need to install the full version of the framework.
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: Thursday, November 09, 2017 12:37 PM To: profoxtech@leafe.com Subject: Re: WestWind Web ClrHost and wwDotNetBridge error on Win2K3 Server
On 2017-11-09 05:35, Alan Bourke wrote:
See
Client tells me they've had DotNet runtimes version v4.0.30319 since August on that server. They can't go beyond that. (Why, I don't know.)
_______________________________________________