VS2012 Entity Framework database first, update model problem - by lawrenceling

Status : 

 


4
0
Sign in
to vote
ID 759658 Comments
Status Active Workarounds
Type Bug Repros 3
Opened 8/26/2012 3:01:36 PM
Access Restriction Public

Description

When you add a new ADO.NET entity data model in a FOLDER, you can create it fine.
but when you update model from database or delete an entity type from the model, the model mapping classes (.tt) stay unchanged.

If you put it directly under you application directory, everything is ok.
Sign in to post a comment.
Posted by Rowan [MSFT] on 12/3/2012 at 11:49 AM
Hello,
Thank you for contacting us. This is a duplicate of an existing bug (http://entityframework.codeplex.com/workitem/453). This issue is fixed in Visual Studio 2012 Update 1 - http://www.microsoft.coHello,
Thank you for contacting us. This is a duplicate of an existing bug (http://entityframework.codeplex.com/workitem/453). This issue is fixed in Visual Studio 2012 Update 1 - http://www.microsoft.com/visualstudio/eng/downloads#d-visual-studio-2012-update.
If you encounter any further issues please report them via the Entity Framework CodePlex site - http://entityframework.codeplex.com/WorkItem/Create.
~Rowan
m/visualstudio/eng/downloads#d-visual-studio-2012-update.
~Rowan
Posted by Helen [MSFT] on 8/30/2012 at 1:13 AM
Thanks for your feedback.

We are rerouting 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 Vitaly Zayko on 8/27/2012 at 12:00 PM
I got same bug. Here are steps to repro:
1. Create a C# project and create a folder in it.
2. Add an empty ADO.NET Data Model to this folder, connect to an SQL DB and import few stored procedures.
3. In Model Browser observe that procedures were imported.
4. Switch to Solution Explorer, expand <model name>.Context.tt -> <model name>.Context.cs and observe that code for these procedures were generated.
5. Now go back to Model Browser and do "Update Model from Database" option, select a SP that wasn't imported in p.2. Then repeat p.3 - new procedure is there, then p.4 - auto generated code for this procedure wasn't created and SP is not available from editor.
If you delete imported procedures from Model Browser, auto generated code remains unchanged as well.
The only workaround I was able to find is to drop the whole model from project and recreate it from scratch.
Posted by MS-Moderator07 on 8/27/2012 at 12:49 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a video of this issue so that we can conduct further research?

We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team