Should I use multiple assemblies for an ASP.NET sandboxed web application?

Question

Starting with the corporate IT environment, the standard has always created a class library project for each level, business logic, data access, and sometimes greater isolation of specific types.

Now that I’m working on my own web application project, I don’t see the real need to isolate my code in this way.

I do not have several applications that need to share this logic or service. I also see no benefits for deployment scenarios.

I tend to put all artifacts in one web application, logically separated by project folders.

I wanted to know what community thoughts are.

---

Let me add more info ...

I am writing this application using the MVC 5 preview, so part of the module testing will be supported by sharing the problems inherited within the framework. I really like tests for everything!

Answer 1

Start with the simplest thing and add complexity if and when required. It looks like one build will work just fine for your business. However, be careful not to break the layers if layer A has gained access to the internal member of layer B. This will make it difficult to bring layers to separate assemblies later.

Answer 2

I would say it depends on how serious you are about testing and unit testing.

/ , , .

, -, .

, , . , - , -/ DAL.

Answer 3

- .

, , 100. , .