The Dll and DllReference plugins allow the code to be split in multiple bundles in a way the bundles can be compiled independently.
It is possible to build "vendor" scripts in a library that does not need to be compiled often (ex: React, jQuery, Bootstrap, Fontawesome...) and reference it in your app bundle that will need those scripts.
The application bundle, the one that is constantly going to be changed, will be in a separate configuration just referencing a already built "vendor" bundle.
You may have seen several websites that will show how to create an ISAPI extension project but none of them will demonstrate how to migrate the existing legacy ISAPI extension (VS2005) project to VS2015. I had faced similar issue while I was working on one of such requirement. This article demonstrates the experimental waythat I had took to solve my issue.
In short, a DLL is a collection of small executable code, which can be called upon when needed by a program that's running. The DLL lets the executable communicate with a specific device such as a printer or may contain code to do any number of particular functions. As there are several methods of implementations to do this, in this topic I'll be showing you how to register and unregister any DLL that your application calls for; and we'll be doing so using the
RegSrv32.exe command line.