Proper way to build a data Repository in ASP.NET MVC

I'm working on using the Repository methodology in my App and I have a very fundamental question.

When I build my Model, I have a Data.dbml file and then I'm putting my Repositories in the same folder with it.... IE:

Data.dbml

IUserRepository.cs

UserRepository.cs

My question is simple. Is it better to build the folder structure like tha开发者_Go百科t above, or is it ok to simply put my Interface in with the UserRepository.cs?

Data.dbml

UserRepository.cs              which contains both the interface and the class

Just looking for "best practices" here. Thanks in advance.

General best practice is to have one class or one interface per file.

Here's the more generic discussion, which I think applies to your case: One class per file rule in .NET?

As a developer new to your project, I would appreciate knowing that IUserRepository exists--without having to fish through your UserRepository.cs file.

Do whatever makes sense to you.

Personally I find browsing solutions for anything painful so I have hot keyed Goto Definition/Implementation and Resharpers FindUsages Go to Type, Go to File so I never have to click anything.

Combining interfaces and classes in one file makes sense if the class or interfaces are small.

Also if your following the Liskov substitution principal / a dependency injection strategy and general good design practices you would rarely be interacting with actual implementations anyway. Repositories should almost never be referred to by their concrete implementation.