Hi Rick,

Another thing I'm noticing is that the DLLs in the wconnect\web\bin folders are not the same as the DLLs in the root wconnect folder.

The Web/bin folder shouldn't have any of the client DLLs in them. No wwDotnetBridge or Newtonsoft. Not sure why they are there on your's but they shouldn't be there.

The only ones needed are webconnectionModule.dll or wc.dll and Microsoft.WebSockets.dll. The sample adds the MetaWebLog.dll for the dll.

+++ Rick ---

Probably cruft from a pre-7 install?

So no other DLLs or other files in that BIN folder including INI or XML, etc correct?

And as long as I'm asking silly questions, application specific DLLs like wwDotNetBridge should be in the application deploy folder, yes?

Those other files should have never been in that folder. If they are that was by accident.

The Web Libraries (webconnectionmodule.dll and wc.dll) are free standing and have no dependencies on any of the WWWC client libraries. wc.dll is pretty much deprecated at this point anyway - it's basically just provided for backwards compatibility. Still works, but it hasn't been updated in a long time and doesn't support some of the new admin features.

I think next major update wc.dll and the Apache module files will get removed so only webconnection.dll and the Web Connection Web Server will ship in the box. The others will still work but only for backwards compatibility.

+++ Rick ---