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
In terms of how a typical asp.net core app starts up, it typically uses something like this:
public class Program
{
public static void Main(string[] args)
{
CreateHostBuilder(args).Build().Run();
}
public static IHostBuilder CreateHostBuilder(string[] args) =>
Host.CreateDefaultBuilder(args)
.ConfigureWebHostDefaults(webBuilder =>
{
webBuilder.UseStartup<Startup>();
});
}
Note that this uses a single startup class to configure services and middleware for the entire application.
Could dotnettency offer a support library to improve this for multitenancy? I.e perhaps allowing you to implement your per tenant startup in a seperate class to the application startup class?
Think about this.
The text was updated successfully, but these errors were encountered:
In terms of how a typical asp.net core app starts up, it typically uses something like this:
Note that this uses a single startup class to configure services and middleware for the entire application.
Could dotnettency offer a support library to improve this for multitenancy? I.e perhaps allowing you to implement your per tenant startup in a seperate class to the application startup class?
Think about this.
The text was updated successfully, but these errors were encountered: