This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Is LightSpeed able to run inside DotNetNuke? I'm thinking of using LightSpeed as my OR/M tool for building custom DotNetNuke modules. The main questions are:
If you're not familiar with the "objectqualifier" feature of DNN, it's essentially a prefix that can be put on the database table names, and it can be different across different DNN installs. So, on my DNN install the db table might be named "Products", but on someone else's it coudl be named "dnn_Products" or something like that. The value for the "objectqualifier" is stored in the web.config file for the DNN site. |
|
|
|
|
I'm not familiar with DNN, so I can't offer general advice, but: Medium Trust: Yes, LightSpeed works in medium trust, but it needs to be told that it is a medium trust environment (because some things have to be done differently in MT). See http://www.mindscape.co.nz/blog/index.php/2009/02/15/running-lightspeed-under-medium-trust/ for how to do this (note you must set the option separately on the LightSpeedContext and the designer model). The blog post is slightly out of date: on the plus side, LINQ now works under medium trust, but on the minus side, it appears that there's a bug in .NET 4.0 which prevents LightSpeed from running in medium trust in 4.0 environments. Object qualifier: You can address this by implementing the INamingStrategy interface (specifically the GetTableName method), and assigning LightSpeedContext.NamingStrategy (or setting namingStrategyClass in the web.config). See "Conventions" in the help file for more info. |
|
|
|
