ng-startup | ngbp fork for Corley AngularJs projects | Runtime Evironment library

1. Your script cannot and should not run in a crontab.

Because crontab script has no built in environment. Therefore everything need to be expressed in full/absolute path.

1. Your script should not be located in /etc/init.d . Because it is not initialized automatically by SysV service nor by systemd service.

2. Better put your script under user oracle home init folder (assuming oracle is the correct user for running Oracle RDBMS).

I've posted this question on github/aspnetcore and get the answer. https://github.com/dotnet/aspnetcore/issues/36204#event-5293269898

The issues was because I had Kestrel settings in appsettings.json as well as in Program.cs public static IHostBuilder CreateHostBuilder(string[] args) =>... and at the end only those from appsettings.json are taken, which unfortunately does not contains certificate details.

You cannot use dependency injection for the startup class. The reason for this is that the startup class is actually created before the service container is being build. If you consider what one of the two primary purposes of the startup class is, then it makes sense too: The Startup.ConfigureService method is used to configure the service container. Similarly to how you register the hosted service using the ConfigureServices method on the host builder, you can also configure it within the startup’s ConfigureServices method and it will have the same effect. Because both methods are configuring the same service container.

For that reason, it’s conceptually not possible that the Startup class could be created (and as such receive dependencies from the service container) when it is actually used to configure the service container before its creation.

If you need your Orchestrator service in your startup class, then you are likely doing something suboptimal: If you need to configure the service container using this orchestrator, consider using something like a factory instead, or configure things at runtime. Otherwise, if you need your orchestrator to affect the application pipeline, then you can just inject the type directly into the Configure method of your startup.

Finally, note the difference in your question title: “inject same dependency object for both a web host and a hosted service”. You are able to inject the dependency in both the hosted service and the web host. But the startup class is not the web host, it just configures the web host.

I found the following solution: https://bugs.mysql.com/bug.php?id=102364

MySQLWorkbench need Python3.7 Framework in /Library/Frameworks/

1. Run brew install python@3.7
2. Then, run sudo cp -r /usr/local/Cellar/python@3.7/3.7.9_3/Frameworks/Python.framework /Library/Frameworks/Python.framework
3. Finally, open MySQLWorkbench and it works.

Or you can just create a symlink to the entire file (thx to @Phillip1982)

sudo ln -s /usr/local/Cellar/python@3.7/3.7.10_1/Frameworks/Python.framework /Library/Frameworks/Python.framework

All Microsoft services follow the same Options pattern. Firstly, you could move those lambda methods to static methods, perhaps on different classes. Which seems to be what your Config example has done. You just need to make sure your static methods have the same function signature.

For example, .AddAuthentication takes an Action delegate as an argument. So any static void foo(AuthenticationOptions o) method could be passed in instead.

Or you could write services that implement IConfigureOptions and register those. This is particularly useful if you need to access other services, like a database for example, in order to configure those options types.

Just add the parameters to your attribute

So, no apparent solution for this project under Android 8+ and Xamarin 9. I have a temporary workaround by using VS2015, Xamarin 4 and targeting Android 4.4; this is fine for my own purposes since I won't be trying to use the Google Play Console just yet. At some stage (no time available at present) I will start a new 'hello world' project targeting Android 9, and gradually bring in my old code to see when/where it fails.

[later]

Well I had to cancel my holiday because of Coronavirus so I had soem time to do this. Started a new project (Android 8.1, VS2017), imported all the old code. I had to redefine some of the resources but everything now working (in the emulator at least, not tried on a device yet). So maybe this was just an annoying side effect of jumping too many Xamarin versions at once.