Comments on: Using the Linq to Sql Adapter in a DotNetNuke Module http://blogs.law.harvard.edu/brandonhaynes/2008/10/14/using-the-linq-to-sql-adapter-in-a-dotnetnuke-module/ Observations about the intersection of technology, business, and intellectual property Wed, 21 Oct 2009 16:16:51 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: Brandon Haynes http://blogs.law.harvard.edu/brandonhaynes/2008/10/14/using-the-linq-to-sql-adapter-in-a-dotnetnuke-module/comment-page-1/#comment-923 Brandon Haynes Fri, 08 May 2009 12:52:17 +0000 http://blogs.law.harvard.edu/brandonhaynes/?p=29#comment-923 Hi Rex, I appreciate the feedback you've been able to provide. I actually have been considering packaging the project into a more generalized LINQ to SQL runtime model adaption engine, so I would be interested in seeing what you've done. I will be in touch. B Hi Rex,

I appreciate the feedback you’ve been able to provide. I actually have been considering packaging the project into a more generalized LINQ to SQL runtime model adaption engine, so I would be interested in seeing what you’ve done. I will be in touch.

B

]]> By: Rex Henderson http://blogs.law.harvard.edu/brandonhaynes/2008/10/14/using-the-linq-to-sql-adapter-in-a-dotnetnuke-module/comment-page-1/#comment-888 Rex Henderson Wed, 06 May 2009 23:53:41 +0000 http://blogs.law.harvard.edu/brandonhaynes/?p=29#comment-888 Hi Brandon, Fabulous bit of code you created. During testing I noticed my GetModel() call was throwing exception due to flaws in my MappingSource graph. These poor MappingSource objects were getting cache all the same. Being a static class field, you had to bump the web.config to clear it. What I did was add the MappingSource after a successful GetModel call to remove this minor obstacle. FYI - I extended the adapter down to the MemberData I use it to look up defaults from the sys.default_constraints table and set my MetaDataMember.Expression so I do not have to explicitely set values on those columns for new records. Works like a charm. The best part is, using your foundation, I do not have to touch the auto-generated dbml code AT ALL for any of my tweaking needs. Let me know if you're interested in see my additions. Thanks! Hi Brandon,
Fabulous bit of code you created.

During testing I noticed my GetModel() call was throwing exception due to flaws in my MappingSource graph. These poor MappingSource objects were getting cache all the same. Being a static class field, you had to bump the web.config to clear it. What I did was add the MappingSource after a successful GetModel call to remove this minor obstacle.

FYI – I extended the adapter down to the MemberData
I use it to look up defaults from the sys.default_constraints table and set my MetaDataMember.Expression so I do not have to explicitely set values on those columns for new records. Works like a charm.

The best part is, using your foundation, I do not have to touch the auto-generated dbml code AT ALL for any of my tweaking needs.

Let me know if you’re interested in see my additions. Thanks!

]]> By: Brandon Haynes http://blogs.law.harvard.edu/brandonhaynes/2008/10/14/using-the-linq-to-sql-adapter-in-a-dotnetnuke-module/comment-page-1/#comment-42 Brandon Haynes Wed, 18 Feb 2009 14:19:01 +0000 http://blogs.law.harvard.edu/brandonhaynes/?p=29#comment-42 Hi DaCoder, Look on the CodePlex site under the "Releases" tab for a sample installable DotNetNuke module. If you are having issues with deployment, I would use the manifest contained therein as a model for your own module. Note that it was designed for the 4.x line, so you may or may not want to tackle updating the manifest to the 5.0 version. Really the only file that is *required* to be deployed is the Linq adapting assembly BrandonHaynes.ModelAdapter.dll. But the target DotNetNuke installation must be configured to use Linq (in 5.x+ this can be performed automatically; if not, see Michael Washington's LinqPrep tool), and you must be sure to recreate the database schema with fidelity to your development environ. The error you describe may be a result of an issue with schema recreation, though it would be more helpful to see a full call stack for the exception. I am aware of a number of module deployments utilizing the model adapter, so it is indeed possible. Good luck! Hi DaCoder,

Look on the CodePlex site under the “Releases” tab for a sample installable DotNetNuke module. If you are having issues with deployment, I would use the manifest contained therein as a model for your own module. Note that it was designed for the 4.x line, so you may or may not want to tackle updating the manifest to the 5.0 version.

Really the only file that is *required* to be deployed is the Linq adapting assembly BrandonHaynes.ModelAdapter.dll. But the target DotNetNuke installation must be configured to use Linq (in 5.x+ this can be performed automatically; if not, see Michael Washington’s LinqPrep tool), and you must be sure to recreate the database schema with fidelity to your development environ.

The error you describe may be a result of an issue with schema recreation, though it would be more helpful to see a full call stack for the exception.

I am aware of a number of module deployments utilizing the model adapter, so it is indeed possible. Good luck!

]]> By: DaCoder http://blogs.law.harvard.edu/brandonhaynes/2008/10/14/using-the-linq-to-sql-adapter-in-a-dotnetnuke-module/comment-page-1/#comment-41 DaCoder Fri, 13 Feb 2009 16:46:18 +0000 http://blogs.law.harvard.edu/brandonhaynes/?p=29#comment-41 Hi Brandon Thank you for the adapter you developed. I used it for developing a module and it works fine in development. My question is, about packaging? What files should I be packaging when deploying this module ? I am getting an error like "TypeName used in LinqDataSource not found"? when trying to install this module on a new DNN installation. Thanks DaCoder Hi Brandon
Thank you for the adapter you developed. I used it for developing a module and it works fine in development.
My question is, about packaging? What files should I be packaging when deploying this module ?
I am getting an error like “TypeName used in LinqDataSource not found”? when trying to install this module on a new DNN installation.

Thanks
DaCoder

]]>