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 have two linked model files. One of the models does not have any entities on it. When I try compile the app I get the following error: "Partial declarations of 'MyNamespace.Model.CoreUnitOfWork' have conflicting accessibility modifiers" This seems to be because the CoreUnitOfWork class has a public definition in the one model but the empty model has a it's partial declaration scoped as internal. I can easily get around this by adding a dummy enitity but if I change that entity's scope to internal I would probably have the same issue again. |
|
|
|
|
Thanks for letting us know about this. I've committed a fix which will be included in the 15 July nightly build, available from about 1500 GMT. Please let us know if you still see the problem. |
|
|
|
|
Thanks. I have downloaded the latest nightly build (20100716) but I still see the problem.
The empy model generates :
internal partial class CoreUnitOfWork : Mindscape.LightSpeed.UnitOfWork
and the other model (that has a entity) generates :
public partial class CoreUnitOfWork : Mindscape.LightSpeed.UnitOfWork
I fixed it on my side by changing the template to not generate a UnitOfWork class if no entities exist in the model. This does not work though if all the enities in 1 model are interal and then public in the other model. |
|
|
|
|
This looks like you might not have Is Linked Child set to true on the empty model. Is that possible? I have double-checked and we no longer emit an access modifier on linked child models. Also don't forget you will need to make a change to the empty model to force it to regenerate code -- dragging an entity on and immediately deleting it should do. |
|
|
|
|
I'm seeing this same behavior when I have a model that only has 2 stored procedures on it. Not a big deal, just letting you know. I'm on 4.0.1177.19892 |
|
|
|
