ClickOnce was designed to deploy managed assemblies, at a time when "managed" meant .Net Framework.
However, that only applies to the application entry point. It is capable of deploying any kinds of file, including native DLLs and .Net Core assemblies. The only requirement is that the entry point targets netfx.
This leads to the possibilty that native and netcore "entry" points can be accomodated by using a netfx launcher app.
Ideally, the entry point should be examined to see if it's netfx. If not, a simple launcher app should be emitted which uses Process.Create to spawn the actual entry point. This requires and imples full tust,
mansellan
commented
4 years ago
ClickOnce was designed to deploy managed assemblies, at a time when "managed" meant .Net Framework.
However, that only applies to the application entry point. It is capable of deploying any kinds of file, including native DLLs and .Net Core assemblies. The only requirement is that the entry point targets netfx.
This leads to the possibilty that native and netcore "entry" points can be accomodated by using a netfx launcher app.
Ideally, the entry point should be examined to see if it's netfx. If not, a simple launcher app should be emitted which uses
Process.Createto spawn the actual entry point. This requires and imples full tust,