-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No "Is Identity" setting when adding a new entity property (version 4.2.44) #63
Comments
I also see the same problem, for now my workaround is to create a code-1st entity and drag it to designer which make the "is Identity" along with key Icon show, then I can copy-paste that entity inside the designer to create more entities. |
+1 I'm also geting this behaviour. For the moment i had to reverto the previous version that functions correctly |
Please try the same with "Guid" type as primary key - if you still won't be able to reproduce I'll send you an .efmodel file. |
I found (and corrected) an issue where the default identity properties weren't being created when a new entity is dragged on to the design surface, but still can't repro the exact issue you've posted. It's possible that something else fixed the problem earlier and it hasn't made it out yet. I'll be posting a build of v4.2.5 to GitHub here shortly. If you would be kind enough to give that a go and see if it resolves your problem, I'd be most appreciative. It won't go out to the Marketplace yet, but can be installed manually by downloading and "executing" the vsix. |
I'm having the same problem. Revisited a dataset I haven't touched in a few months, and went to add a new entity via dragging from toolbox. It didn't automatically create the Id column like it use to with the default Int64 type and Primary key. Adding the Id column manually, didn't have the property available "Is Identity" for me to set. I compared to an existing entity in the designer, and walked down the two Id columns to make them pretty much identically, but nothing triggered the Is Identity column to appear so I could set it. I can however, copy an existing entity in the designer, edit it and get that column back. |
I believe I have the problem diagnosed. My thanks to all for your patience and my apologies for the problem existing. Should be resolved soon. |
Appreciate all your efforts.
Something else happened I think it was last month. Updated to latest extension version, and it caused all the code to regenerated when I went to change a column max string length. That's expected. But I didn't expect it to change literally all the entity constructors to make them require additional parameters. It broke everything. I had to revert everything and manually look for the expected change and include that in the migration.
Not sure if that has been resolved but I'm afraid to touch that database now and haven't checked on it to see if it still will do that sans odd behavior.
Have you encountered that?
Craig
…________________________________
From: Michael Sawczyn ***@***.***>
Sent: Thursday, July 20, 2023 5:50:58 AM
To: msawczyn/EFDesigner2022 ***@***.***>
Cc: Craig ***@***.***>; Comment ***@***.***>
Subject: Re: [msawczyn/EFDesigner2022] No "Is Identity" setting when adding a new entity property (version 4.2.44) (Issue #63)
I believe I have the problem diagnosed. My thanks to all for your patience and my apologies for the problem existing. Should be resolved soon.
—
Reply to this email directly, view it on GitHub<#63 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AK6SED3B3NFSJU6GZVMCFCDXRESTFANCNFSM6AAAAAAYMUUMH4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Thank you very much for fixing this and other reported bugs. I use EF Designer practically every day, so it's an important tool for me. |
When adding a new entity, then a new property, there is no "Is Identity" setting available for that property. The type is Int64, and Indexed and Indexed Unique are set, but "Is Identity" doesn't appear.
The text was updated successfully, but these errors were encountered: