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 All, I have just come across a minor annoyance. I have an enity that has two links to to another enity, so I had to rename the relationships and objects, no problems there. However, I changed one of the fields Generation property from Default to FieldOnly so I could override the implementation in a partial class. When I did this, the model appeared to re-load and re-set the variable names that I had just changed for the two links as well as the two get methods. It's not a biggie really, just thought I'd point it out.
|
|
|
|
|
Oh, and I also forgot that when I fixed the relationships so they had unique names,rebuilt and got a Rebuild All succeeded and everything ran fine, I still got an error in the error list that "Enitity xxxx has multiple properties/associations named 'blah'" in File Model.lsmodel This went away when I closed and re-opened VS. |
|
|
|
|
Arrggh.It's Friday. My brain is mush. Just realised the error above is becasue I changed the names in the generated code directly, not via the model, although I would have thought it would have stopped me running. |
|
|
|
|
Hello Paul, This may be a dumb question, when you say you "renamed the relationships and objects," did you rename them on the design surface or in the generated code? If the former, then this is a designer bug and we will investigate. If the latter, then this is expected behaviour: the generated code is overwritten whenever you save the model, so you should never edit it directly. (If there's a reason you need to edit the generated code because you can't get the effect you want by editing the model, let us know!) |
|
|
|
|
Yup, I renamed them directly in the code, then made the change to the property in the model. Doh ! It's been a long week {:o) |
|
|
|
