I\'m working on a project that at can end up with multiple UI versions / variants, but so far I\'ve got two subprojects in my solution Web - containing Web interface with A
You would need a mechanism to call the Database.SetInitializer method before the very first usage of the DbContext. That is why its usually called in the Global.asax file.
You can create a class with an initialization method in your tm.Service project and call it in the Application_Start method and put the Database.SetInitializer in that initialization method.
Its OK to supply the connection string from a setting file.