I’ve noticed in https://docs.particular.net/nservicebus/upgrades/host-7to8 that NSB.Host is being deprecated.
I’m currently planning an upgrade from NSB4.7/.Net4/mvc4/ef6 to NSB6.3/net452/aspnetcore/efcore.
Attemping to do so with netcore sdk libraries and aspnetcore but targeting net452. To ensure that my upgrades to netstandard post NSB6 will work easier. Surprisingly it’s going well.
I’ve had to drastically change all my endpointconfigs and ensure that everything is running. I’m now considering standardising even further to netcore configuration, logging and dependency injection libraries.
Now that I’ve noticed that NSB.Host is on the way out, can I use selfhost for all services under NSB6.3 and install as windows services? Is there any downsides to this over the current topshelf host?
Is topshelf now gone from NSB Ecosystem?
This will mean that all my webapps, nsb services, console apps all have a program.cs and a similar NSB startup process. But also i can standardise my configuration in all projects into the appsettings.json format. I’m considering implementing a custom instance-mapping.xml into appSettings.json.
Using the conventions in Startup.cs to invoke :
public Startup(IHostingEnvironment env, ILoggerFactory loggerFactory) public IServiceProvider ConfigureServices(IServiceCollection services)would allow a nice experience to onboard my team into the netcore world and I’m already this far in with so many breaking changes?
Does anybody currently use selfhost exclusively? I have current console apps and webapps that self host, but i’ve never used selfhost and windows services together.