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
|
We would like to use LightSpeed under the .NET Framework Client Profile, but it depends on System.Web and System.Data.OracleClient, which aren't currently installed with the client profile. (See http://blogs.msdn.com/bclteam/archive/2008/05/21/net-framework-client-profile-justin-van-patten.aspx for a list of assemblies.) Would it be possible to provide a build that is compatible with the client profile, or perhaps to move incompatible types into a separate optional assembly? (The client profile hasn't shipped yet, but we're using the beta for testing purposes.) |
|
|
We have been doing a little bit of testing with this and our impression is that LightSpeed will run under the Client Profile, provided of course that you do not invoke the specific features which are not supported there. E.g. the absence of the Oracle DLL isn't an issue unless you specify the Oracle provider; and the lack of System.Web isn't an issue unless you specify caching using the HTTP cache provider. The only problem we noted was that the compiler raised warnings about the LightSpeed dependencies when targeting the Client Profile. Granted, this is annoying, and I'm sure that you, like us, prefer to have "treat warnings as errors" switched on; but in this case the warnings are somewhat spurious. Would it be an option for you to exclude this specific warning? If so, then at runtime LightSpeed should have no problem running in your Client Profile apps, again subject to the caveats above. I admit my testing was extremely rudimentary -- a simple WPF app that connected to a SQL Server database and did a single Find -- so I may very well have missed some areas where LightSpeed does run into issues. We would therefore be keen to hear what problems have arisen in your testing. (This is not to rule out producing a build that targets the Client Profile. I have logged a request for this; we just want to understand the nature and scope of the issues so that we can prioritise that request appropriately.) |
|
|
Sorry about that -- you are absolutely correct. Our actual problem turned out to be that we didn't specify the client profile in our app's .config file: <startup> Since LightSpeed doesn't fail unless the missing types are actually used, my interest in a separate build has declined dramatically. Thanks for your response! |
|