Hi.
I plan to create two (at least) Blazor Server projects that will have completely different functionality, but at the same time use the same database.
In this case, it is quite logical to create a separate project first, which will include (to put it simply) the contents of the Data and Models directories, and then make other projects use it.
Well, I can do it now. But there is one very big inconvenience - you have to manually change the names of classes in a lot of files .cs and .razor.
I think it would be very cool if there was an opportunity to do like this:
Furthermore, the ability to create a separate 'server tier' for each datasource and then attach to that in another project (via swagger or OData) could be expanded so that relationships between separate datasources can be defined and enforced. Like mashup Customers from CRM with Salespersons in MSGraph and Tickets in ZenDesk.
