Recent changes introduced a change in DLL location to default to where the application DLLs live. Because this means the DLL will automatically be loaded on startup changing the DLL becomes impossible in development without a re-run. We need to change compilation to support:
[x] In-memory for testing purposes and potentially even dev cycle
[x] Off-probe compilation. This may be the default for development environments. This allows Blueprint control of the compilation and loading
[x] NO compilation if an existing DLL has already been loaded by the runtime, which will be used in the case of a pre-compiled DLL (i.e. as part of publish deployment where we expect NO compilation to occur on the deployed servers and instead the DLL is part of the "normal" lifecycle of DLL loading)
This requires a few things:
[x] Change how we determine where to load and compile to
[x] An earlier check for existing pipelines
[ ] Pre-compilation support as part of a publish action. A NuGet package that can add the required MSBuild targets to support this
Recent changes introduced a change in DLL location to default to where the application DLLs live. Because this means the DLL will automatically be loaded on startup changing the DLL becomes impossible in development without a re-run. We need to change compilation to support:
This requires a few things: