0
votes
1answer
101 views

When to build User Controls in ASP.NET

I am inheriting a legacy code. The legacy code has lot of web forms and each web form does not have much of functionality other than hosting a user control. My question is - Should we create a ...
5
votes
2answers
119 views

How to structure many projects that can be versioned and deployed separately

My team is in a situation where we need to create about 30 different processors. By processors I mean code that takes data from a DB and sends it to a remote service somewhere else in the world. They ...
3
votes
1answer
143 views

Code structure for multiple applications with a common core

I want to create two applications that will have a lot of common functionality. Basically, one system is a more advanced version of the other system. Let's call them Simple and Advanced. The Advanced ...
2
votes
3answers
496 views

Naming the project containing only interfaces

I've extracted interfaces from my repository classes, like ICustomerRepository, IProductRepository and so on. The project which contains the repositories is named X.DataAccessLayer. Should I call the ...
5
votes
3answers
2k views

How should I structure a solution for a long term project?

I'm about to create a do-everything dashboard for my team and am still having second thoughts about my project/solution structure. Since this could be a long ongoing project, I want to get the ...
5
votes
4answers
248 views

Should I include dependencies for which I have the source as projects in my solution?

We have various projects in source control for web and desktop applications. Invariably, many of them use third-party open source projects or even common libraries within our organization as ...