The startup class is created as part of the application, to configure the app via code.
I would suggest either create a "base startup"-class that you can inherit from, or more commonly create extension methods that you call in your startup to configure your app as needed.
Moving Owin Startup class to seperate class library project
Dear All,
I have implemented Owin startup class which has combination of frontend and BackOffice authentication with Azure AD.
I don't want to repeat the logic and hence to make re-usable code I want to move the classes to separate class project.
Is it possible to move owin startup class to separate class library object ? and load it as dependency injection or something else ?
Hi Anand,
The startup class is created as part of the application, to configure the app via code.
I would suggest either create a "base startup"-class that you can inherit from, or more commonly create extension methods that you call in your startup to configure your app as needed.
HTH :)
is working on a reply...