I'm quite inexperienced with .NET as a whole and would like a bit of guidance and pointing in the right
I'm developing a new website however, based on what I've read, I'm also using LINQ to SQL and Custom Server
Controls. The basic infrastructure is this:
I'm using SPROCS to do all CRUD operations.
I've got 2 projects, the first contains 2 LINQtoSQL files which encapsulate all my SPROCS. I use 2 LINQtoSQL files
because I'm using 2 different connections (strings) to connect to 2 different DB's. The second contains all my
custom server controls (which uses the LINQtoSQL project to access the DB.).
I then have a website which uses both these 2 projects.
I however am being lead down the path of not using LINQtoSQL because we don't know:
1. How to successfully deploy the website with these two projects (.dll's) which use LINQtoSQL.
2. It is intended that the website (using these two projects (.dll's) will be deployed to multiple (physical) servers. What will be the ramifications of this? Will this make deployment and maintenance more difficult? How would that be gone about?
If anyone can point me in the right direction, that'd be highly appreciated.
View Complete Post