You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a placeholder for a longer conversation. There's starting to be more and more boilerplate code for bootstrapping both a headless application or a web application with both Wolverine and Marten -- plus the overhead of registering "do this in development" vs "do this in production mode".
I'd like to maybe consider some kind of customized ApplicationHostBuilder and/or WebHostBuilder that's a bit customized for using the two tools. I'd like to drop the WolverineOptions and Marten's StoreOptions on the actual builder too. Maybe separate "hive" properties for Development vs Production.
I'm also concerned about some of the dev vs prod settings like codegen or the application assembly location where both tools have the same settings. It would be nice to centralize some of that as well.
Of course, this could be beaten with just a new AddCritterStack(opts => ) where the opts let you configure both Marten & Wolverine at one time.
I kind of like a var builder = CritterStackHost.CreateApplicationBuilder() and/or a var builder = CritterStackWebHost.****()
The text was updated successfully, but these errors were encountered:
This is a placeholder for a longer conversation. There's starting to be more and more boilerplate code for bootstrapping both a headless application or a web application with both Wolverine and Marten -- plus the overhead of registering "do this in development" vs "do this in production mode".
I'd like to maybe consider some kind of customized
ApplicationHostBuilder
and/orWebHostBuilder
that's a bit customized for using the two tools. I'd like to drop theWolverineOptions
and Marten'sStoreOptions
on the actual builder too. Maybe separate "hive" properties for Development vs Production.I'm also concerned about some of the dev vs prod settings like codegen or the application assembly location where both tools have the same settings. It would be nice to centralize some of that as well.
Of course, this could be beaten with just a new
AddCritterStack(opts => )
where the opts let you configure both Marten & Wolverine at one time.I kind of like a
var builder = CritterStackHost.CreateApplicationBuilder()
and/or avar builder = CritterStackWebHost.****()
The text was updated successfully, but these errors were encountered: