we are trying to move away from installing dotConnect in our production environment towards delivering the runtime assemblies packaged together with the web applications. Upgrading to a new version is a huge headache when it can affect hundreds of applications. We could use some assistance .
Following the proposed solution:
- Development machines: Full installation of the current dotConnect version including Visual Studio plugins. Including the license.licx in the projects so the license later gets compiled into the resulting assemblies by the build server. Setting "copy local" to "true", so the DLLs are packaged with the application.
- Build server: Minimal installation of multiple different relevant dotConnect versions. Removing all policy files from the GAC. The license should get compiled into the application assemblies.
- Production servers: No (or old) installation of dotConnect, relevant DLLs are deployed in the bin folder along with the application assemblies.
- Is this a possible and sensible solution for us?
- Are multiple minimal dotConnect installations on the build server even possible? It doesn't seem so, since the dotConnect setup uninstalls the previous version.
- Does dotConnect have to be installed on the build server, so the license can be compiled into the application assemblies or is there a workaround?
- Does the installed dotConnect version have to match the version used during build, so the license information in the application assemblies is valid?
- What exactly has to exist on the build server so the license information can be compiled into the application assemblies when adding a licenses.licx file to the projects?
- How else would we best manage the build server?
- "Compiling License Manually" (as described in the licensing document) ONCE for every new version
- Have the developers include the resulting .license file in all of the projects using this dotConnect version
- Manually installing all relevant dotConnect assemblies in the GAC of the build server
- Would this be a possible solution?
- Can the .license file be compiled once for every dotConnect version or does it have to be compiled once per application? That would be a problem.
- In which situations would the licenses.config file be required? If the .license file can not be added to the runtime assembly/executable? What about unit test runners and w3wp.exe?