문제

I googled this a little but couldn't find a good result.

Right now I'm building a web site and I'm trying to make it as correct as possible from a design point of view from the beginning.

The problem I'm now facing is that when deciding to start with logging I needed a project to place this code in. As I could not find a suitable place in my currect projects I thought: hey, why not a logging class library?

Is there a general guideline on how many projects you should have? I know this would be a rather small project but it would be nice to entirely get it out of my way!

Any hints are appreciated :)

도움이 되었습니까?

해결책

HasMany(x => x.AddressLines).Element("AddressLine").Cascade.AllDeleteOrphan();
.

다른 팁

I'd go for a three-tier architecture for a small project.

This would include:

  1. Application Layer
  2. Business Layer
  3. Data Layer

but if you want to add logging, it would be best to create another project. This would also help you so that if you want to add logging to another application, you can just include the logging project.

Either way would work, if you are concerned about project limit in a solutions. Don't be.

I myself would put it in a separate project or a utility project.

SharePoint는 이슈 추적 목록 템플릿을 제공합니다.이 목록을 버그 추적 시스템으로 사용할 수 있습니다.요구 사항을 기반으로 목록에 열을 추가 할 수 있습니다.우리는 프로젝트 중 하나에 대해 SharePoint에서 문제 추적 목록을 꽤 성공적으로 사용했습니다.

기술적으로 이것은 발표 , 당신을 억제하지 않으면 -이 하이브 공급자의 샘플 w / - 클라우드 스토리지

Put a logging into a separate project is perfectly fine.However it really depends on the scope of your project.I normally setup my project like this

YourProject.Web(web project)

YourProject.Core(all the business logic)

YourProject.Web.Tests(Watin tests)

YourProject.Web.Core.UnitTests(Unit tests)

YourProject.Web.Core.IntegrationTests(Integration tests)

I suggest you to download some open source Project from asp.net to see how the project have been organized.

라이센스 : CC-BY-SA ~와 함께 속성
제휴하지 않습니다 StackOverflow
scroll top