You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Including a compiled DLL as a resource without mentioning its source for verification and/or including the code from which it can be compiled independently is poor form. I would love to use this in production, but I can't trust that DLL without further details.
Looking in the DLL, it seems it originally came from Gauffin Telecom, which I assume is https://github.com/jgauffin/Griffin.WebServer. But, including info on how to compile your changes would be greatly appreciated.
As a side note, it's hard to tell since we don't know which license applies to the version of HTTPServer.dll included, but this could be a violation.
The text was updated successfully, but these errors were encountered:
Further diagnostics lead me to believe that HTTPServer.dll comes from Gauffin's initial project at (https://archive.codeplex.com/?p=webserver). The duplicati project includes a slightly modified version of this. Compiling that and replacing your HTTPServer.dll seems to work pretty well, so I'm assuming this is the source of your DLL. I will use my compiled versions of both ZetaIPC AND HTTPServer until you get this sorted.
Regardless, thanks for ZetaIPC. It's exactly what the doctor ordered in my case.
Including a compiled DLL as a resource without mentioning its source for verification and/or including the code from which it can be compiled independently is poor form. I would love to use this in production, but I can't trust that DLL without further details.
Looking in the DLL, it seems it originally came from Gauffin Telecom, which I assume is https://github.com/jgauffin/Griffin.WebServer. But, including info on how to compile your changes would be greatly appreciated.
As a side note, it's hard to tell since we don't know which license applies to the version of HTTPServer.dll included, but this could be a violation.
The text was updated successfully, but these errors were encountered: