Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have multiple C# projects in a Visual Studio solution right now that will all use the same SQL Server database.
What is the proper way to share LINQ-to-SQL classes between projects?
I’m considering just copying the dmbl files into each project, but I think that may be too redundant. Is there a better way to approach this?
I suppose you need to share database access code between projects not linq-2-sql classes as they are.
Build Data Access Library (DAL) that expose operations over database that are implemented via linq-2-sql classes rather then expose classes.
I’d suggest to use Repository Pattern
Refer DAL library from projects you want.