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
|
Hello, I would like to use .NET 4 client profile for my application. I've tried swithing the framework to .NET 4 client profile but I get errors when trying to compile (I'm just using Lightspeed with VistaDB). Why is that? I read a previous post on your forum but it wasn't very clear to me. Can I just compile on the .NET 4 and have the software properly run on the Client Profile? I just want to test things properly. I got errors on the ValidatePresenceAttribute, ValidateLengthAttribute, TransientAttribute and more. Thanks. Andrea |
|
|
The errors are kind of bogus -- Visual Studio is actually objecting to LightSpeed's references to things like System.Data.OracleClient and System.Web, not to the specific LightSpeed classes you mention. As far as I know you should be able to compile an application with LightSpeed against the full .NET Framework and then run it against the Client Profile, provided you don't do anything that requires the full profile. The bad news is that by compiling against the full framework you won't get compiler errors if you do accidentally do something that requires the full profile. I think you would also need to update the manifest/app.config after compilation to indicate that the app requires only the Client Profile (i.e. you would build with app.config indicating full profile but test and ship with app.config indicating client profile). However please be aware that we have not tested this scenario so I would strongly advise doing a quick test run (using a trivial test application) before putting any effort into this approach. |
|