I'm moving our app to a new server and get this error when going to the URL for the app.

I've got the modules in the Bin folder that's inside the web folder. Where do you specify where the Bin folder is located?

.NET 4 is installed, and the App Pool is set correctly.

Since I don't do this every day, I've forgotten some of the nuances of setting up a Web Connect app.

I used the MYAPP.EXE CONFIG and the other automated config options, but I'm still missing something.

Any help would be appreciated.

Phil

.

Check if this is helpful: https://support.west-wind.com/Thread4KZ0OJAN9.wwt

The Bin folder is automatically mapped in a .NET application. So if the file is there and your Application Pool identity has read permissions in that folder it should find webconectionmodule.dll.

If that's not happening I would suspect either that the path to the application is not correct, or there is some sort of permission issue with the Application Pool or path. Double check.

Also make sure that you have Microsoft.WebSockets.dll in the folder as that is a dependency that's required in recent versions. This might cause a dependency problem with the DLL not loading but I believe you'd get a different error for that.

+++ Rick ---

Make sure you have the latest WebConnectionModule.dll. The WebConnectionModule class is a somewhat recent addition (in 7.0) that deals with Web Socket handling for live reload and HTML injection of the LiveReload script. That module class didn't exist in older versions, so most likely your DLL is not a 7.x version.

Check the version of WebConnectionModule.dll (in Explorer|Properties|Details) and it should be 7.28 (if you're using the latest).

+++ Rick ---

It shows I've got 7.28.1.0

I do have other versions on the server. How does it know which Bin folder to pull from?

Any chance you have a parent application that's perhaps also has a bin folder with Web Connection?

Best way to check is by going into the IIS admin console and look at the Handler list - it should show what's loaded and from where. Make sure that it says Local for the Web Connection Module handler references - not Inherit.

It should look like this:

If that's not it then I'm not sure what would cause that error. Do make sure the Microsoft.Websockets.dll assembly is in the bin folder in addition to WebConnectionModule.dll. Without that dependency it won't load.

Also make sure the Application Pool identity has rights to read the files (ie. not ApplicationPoolIdentity user).

+++ Rick ---

It was the Microsoft.Websockets.dll file missing.

Thanks!

Guess you didn't read my original reply 😄

+++ Rick ---

Evidently not. ha ha