LINQtoSQL with a modular application

[MReigler]

We are in the process of designing an application in which some
customers may purchase addition add in modules on top of the core
modules that everyone would get. All modules will connect to a single
database using LINQtoSQL. Originally we where thinking that each
module should have it's own datacontext which would map to a database
schema, but we haven't found anything to really support this concept.
So my question is, is this a good idea or should we create a single
datacontext class for all modules to use.

 

[Cowboy \(Gregory A. Beamer\)]

Read this (read below first):
http://bit.ly/JXfj

The problem domain does not have anything specific to what you are doing,
but it is using LINQ to SQL with multiple contexts via a factory. The blog
entry does not show it, but you can see how I have a switch to pull a
context via a Type. I am going to have this so it can map via a config file
at some time. If you opt for something like this, the database bits can be
installed when the person purchases the module and you simply update the
'config' file. Or, you leave the full config file, if you wish. Just compile
it and obfuscate so it is unreadable and nobody knows the schema changes in
store when the purchase another module.

Peace and Grace,

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

********************************************************
| Think outside the box! |
********************************************************