RavenDB not starting if .NET runtime 5.0.8 is not installed

[RVink]

RavenDB not starting if .NET runtime 5.0.8 is not installed

[RVink]

The Windows update policy at my company keeps installing the latest .NET runtime as part of a security patch.
We decided to temporarily disable the Augurk publish step in our build pipeline as reinstalling .NET 5.0.8 every day is not a viable solution in the long run.

It's really appreciated if this can be resolved :).

[jmezach]

I've build a non self-contained version of our latest preview and deployed that in our environment and it is working again now. I'll cherry-pick the pipeline change to master so that we'll publish runtime dependent going forward. Unfortunately our master pipeline is currently broken.

[jmezach]

This is due to the fact that we deploy Augurk as a self-contained application, which includes the .NET Runtime at the time of building. But we also start up an instance of RavenDB as our embedded server and while starting it we pass along the version of the .NET runtime Augurk itself was started with. But RavenDB depends on the machine installed runtime, which in this case didn't match the version of Augurk.

So I guess we'll either have to stop publishing Augurk as a self-contained application and require our users to install a .NET runtime, or we'll need to stop publishing Augurk as an installable all together and focus our attention on running it in containers.

[jmezach]

I guess we could build a non-self contained version of Augurk to resolve this issue, then at least we would use the same runtime for both Augurk and RavenDB.

[marktaling]

I guess we could build a non-self contained version of Augurk to resolve this issue, then at least we would use the same runtime for both Augurk and RavenDB.

I think that would be the best solution for now. At the very least it can be used on the locations where this issue arises. A self-contained container might be preferable in the future, but also poses different demands of the current users.
Perhaps we want to provide both options in the future? Starting with the non-self contained version first now, adding the container with the next feature release?