-
Notifications
You must be signed in to change notification settings - Fork 60
outputDirectory lost on reload (override non functional) #144
Comments
Glad to hear I can make a contribution to you and your team's lives being a little easier. But regarding what you're seeing ... hard to say. What you describe (and you've dug deeper than I normally hope for in a problem report) shouldn't be able to happen. If you get a moment, you might try 2.0RC1 to see if it exhibits the same behavior. Note that, as of this release, it won't work with VS2017 so, if that's your environment, it won't be something that will help. I have yet to update the docs, so the new features aren't fully described, but they're pretty self-explanatory and listed in the changelog in the main readme both here and on the Marketplace. |
I'm going to take it from the thumbs-up that the 2.0RC1 release worked for you. Unless I hear otherwise, I'll close this within the next day. |
can confirm:
However since it's only me, I have to assume it's environmental. |
Have the is same issue when (I think) one of our devs updated from 1.3.0.11 to 1.3.0.12. The outputdirectory field is suddenly empty, all generated files have been moved to default directory as specified in the efmodel file. When using 1.3.0.12 myself, if I fill in the OutputDirectory for an entity and let it generate the code, no change, the file is still in the default directory... Working on VS2019 Enterprise edition, v16.4.4. Using a .NET Core 3.0 project. |
Thank you both; I've got a bead on this one and it'll be fixed in the upcoming release. I owe you a beer! |
<3 |
Not sure if it's just me. I'll check on a separate PC tonight to verify and report back.
But on latest version from nuget I'm no longer able to override the default directory.
Sequence is as follows:
It seems reloading the efmodel causes the outputDirectory property to be physically deleted from the table's serialized properties in xml. And the save operation does not produce the file properly.
Furthermore the xml file indicates a
isOutputDirectoryTracking
value offalse
, which based on source code grep scan for assignment, appears to indicate that the string value is NULL during serialization. Which may explain why it's dropped when deserialized back to C#.Guessing here, but not sure why it would be null, and yet present in the xml serialized output?
Anyone else experiencing this as well by chance?
Edit:
Can confirm:
Doesn't appear to be asymptomatic, but not sure what's wrong. Let me know any thoughts, and thank you!!! This product makes a major difference in the projects my team works on
The text was updated successfully, but these errors were encountered: