Search

StoreGeneratedPattern does not saved properly into EDMX (Entity Framework 4.0) by Oleg Aksenov

Closed
as Fixed Help for as Fixed

18
0
Sign in
to vote
Type: Bug
ID: 611665
Opened: 10/7/2010 11:40:42 PM
Access Restriction: Public
1
Workaround(s)
6
User(s) can reproduce this bug
After you modified StoreGeneratedPattern value (like "Computed" from "None"), you don't get the expected behavior - values not obtained from database.
This is because the Model Designer don't save this attribute into "SSDL Content" section (only into "CSDL Content").
Details (expand)

Visual Studio/Silverlight/Tooling version

Visual Studio 2010

What category (if any) best represents this feedback?

Reliability

Steps to reproduce

1) Add model (edmx) with any simple entity with at least one property.
2) Save model.
3) Modify StoreGeneratedPattern value for a property.

Product Language

English

Operating System

Windows Server 2008

Operating System Language

English (US)

Actual results

"SSDL Content" section does not contains modified StoreGeneratedPattern value. As a result, any code which use such properties will produce incorrect results.

Expected results

"SSDL Content" section contains modified StoreGeneratedPattern value.
OR
Modifying StoreGeneratedPattern value does not allowed by model designer (if you cannot handle it properly for any reason).
File Attachments
0 attachments
Sign in to post a comment.
Posted by sarahmcd on 8/16/2011 at 2:08 PM
Hi all,
The released hotfix for this issue is now available for you to download!

MSConnect: http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=37957
Code Gallery: http://archive.msdn.microsoft.com/KB2561001

Thank you,
Sarah McDevitt
Program Manager
SQL Server Data Tools
Posted by Microsoft on 6/21/2011 at 2:09 PM
We are actively working on a solution to the issue that this was not fully fixed with SP1.
See duplicate here with more information: https://connect.microsoft.com/VisualStudio/feedback/details/505178/storegeneratedpattern-property-in-ado-net-entity-model-designer-sets-cdsl-annotation-but-not-ssdl-attribute

Thank you,
Sarah McDevitt
Program Manager
sarahmcd@microsoft.com
Posted by Brian lagunas on 4/19/2011 at 1:32 PM
This is not fixed in SP1. Can you please provide feedback on when this will be fixed.
Posted by Terry Stanfield on 3/11/2011 at 8:42 AM
This has been fixed for StoreGeneratedPattern values "Computed" and "None", but it still exists for "Identity" in Service Pack 1.
Posted by Microsoft on 12/9/2010 at 8:37 AM
This bug has been fixed in the first Service Pack for Visual Studio 2010. Thank you for reporting this issue to us.
Posted by Oleg Aksenov on 12/7/2010 at 12:10 AM
> This issue seems to be a duplicate of issue [skipped]
Yes, but this is bug and not fixed, actually. I hope my description and details of this fact is more simple and clear.
Posted by labate on 11/8/2010 at 1:50 AM
This issue seems to be a duplicate of issue "StoreGeneratedPattern Property in ADO.NET Entity Model Designer sets CDSL annotation but not SSDL attribute", bug id 505178 (https://connect.microsoft.com/VisualStudio/feedback/details/505178/storegeneratedpattern-property-in-ado-net-entity-model-designer-sets-cdsl-annotation-but-not-ssdl-attribute).
This other issue was marked as Closed fixed.
Posted by Microsoft on 10/8/2010 at 2:16 AM
Thanks for your feedback. We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 10/8/2010 at 12:00 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by Oleg Aksenov on 10/7/2010 at 11:43 PM
You can modify StoreGeneratedPattern value manually in the "SSDL Content" section too (you could open edmx file with XML Editor). After code generation (run Custom Tool from Solution Explorer or switch to designer, make some changes and save model) you get the expected behavior.