StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4538453
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-12-27T11:50:41.663
FavoriteCount
0
LastActivityDate
2010-12-27T11:52:52.977
LastEditDate
2010-12-27T11:52:52.977
LastEditorUserId
139300
OwnerUserId
510804
ParentId
4531044
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
We have developed similar ASP.NET web portals based on strong modular principles. Tax we pay is lots of Visual Studio projects. There is a single master solution with all modules, web-sites, unit-tests and so on but this solution is usually infeasible to work with on day-by-day basis on computers with small amount of RAM (<= 4 GB). We have common infrastructure code (~ 10 projects) and business module projects. A single business module is composed of all projects dealing with some aspect of business requirements, e.g. Orders, Customer management, Distribution... The business module typically has: <ul> <li>ASP.NET web application project (which becomes a sub-web of the Shell module web-site),</li> <li>domain model assembly (class library with no dependencies) + interface assembly,</li> <li>OR/M adapter for domain model (we use Entity Framework and NHibernate),</li> <li>front-end assembly with presenters, controllers, view models, ...,</li> <li>back-end assembly with module business services and DTOs + interface assembly, </li> <li>unit test assemblies,</li> <li>other assemblies (like Silverlight components, MSQM DTOs, etc.).</li> </ul> We use SLNTools Filter (<a href="http://slntools.codeplex.com/" rel="nofollow">http://slntools.codeplex.com/</a>) to filter out single business module VS solutions from the master solution. So we have solutions OrdersModule.sln, CustomersModule.sln etc. Each such solution has common infrastructure projects (~10) and the module projects (~10-15). SLNTools Filter automatically includes all dependent projects so it's very easy to create a new filtered solution.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMultiple Solution Layout for ASP.NET Web Portal?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCD..
UserOwnerUserId
1. USondrejsv
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMultiple Solution Layout for ASP.NET Web Portal?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.