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
|
Hi, I'm evaluating Lightspeed Express and came across the following bug. I re-installed with the latest nightly build and the problem still occurs. FYI I'm using VS2008 but have an (unused) VS2010 trial on my machine. I've reproduced this in the latest nightly build, and am building using VS2008. My project no longer compiles when I my entities' Visibility is set to "Internal". The problem is in the code generated by light speed, specifically the extension methods used for working with DTOs (e.g. CopyTo, AsDto): error CS0051: Inconsistent accessibility: parameter type 'MyNamespace.MyClass' is less accessible than method 'MyNamespace.Contracts.Data.BlahDtoExtensions.AsDto(MyNamespace.MyClass)' The work-around for now is pretty simple: simply set the entities' Visibility to "Public". Thanks!
|
|
|
|
|
Thanks for alerting us to this issue. I've committed a fix which will be included in nightly builds dated 10 July 2010 and above, available from about 1500 GMT. Please let us know if you still see problems! |
|
|
|
|
Thanks, Ivan. I installed the July 16th build but cannot test for this problem due to another (probably unrelated) problem. The designer fails to re-generate the C# code with a "value does not fall within expected range" error, and ultimately causes the project to not build because the generated C# code is in a bad state (specifically it's the ProjectUOW class is not defined, if that helps out the diagnosis). While I've seen this error before (the codeGenerations attribute on the model element), I removed that attribute and the problem went away. However after the latest install the warning/error does not point to a particular attribute or element in the lsmodel file, but rather just the top of the file. I examined every property and attribute in the XML and there wasn't anything that "looked" out of place (like bad enum values). I re-installed the previous build and the problem goes away. Thanks again,
|
|
|
|
|
We'd like to reproduce this issue -- could you provide us with the .lsmodel file that caused the problem? Thanks! |
|
|
|
|
Never mind -- I've found a repro and will try to get this fixed for you. |
|
|
|
|
I've committed a candidate fix for the "out of range of expected values" error and this will be included in the 20 July nightly, available from about 1500 GMT. Apologies for the inconvenience. |
|
|
|
