We Keep Coding

Stored procedures and functions is not updating for Entity Model

I work with database first Entity Framework & LINQ in Visual Studio 2013.
When i write stored procedures and change them, i used to update Entity Data Model from database by choosing stored procedure updating option.
It is weird that the 'import selected stored procedures and functions into the entity model' option comes disabled so I cannot choose stored procedures and functions for updating model anymore..
Can you please help me to find the problem?

You only have to import stored procedure and functions into the model when they're new. So when there are no new ones the option is disabled.
This doesn't mean that, as you seem to suspect, EF doesn't update existing stored procedures and functions. It does.

call a stored procedure multiple select query in entity framework code first and then map it to model

I am working on a project using entity framework code first approach, I have a situation where I need to call a stored procedure which returns multiple table, hence I want to map the result to my model. please tell me if its possible to do it and if yes then how can i do it.

Code First currently only supports mapping to tables. This unfortunately means
that you can’t map Code First directly to stored procedures, views, or other database
objects. If you are letting Code First generate a database, there is no way to
create these artifacts in the database, other than manually adding them once Code
First has created the database. If you are mapping to an existing database, there
are some techniques you can use to get data from non-table database artifacts.

i am also facing the same problem and not able to get any solution, so i called stored procedure using ExecuteReader and then mapped it to models using autoMapper.
Let me know if you are looking for code

How to update only dirty fields in .NET entity framework when using stored procedures for insert,update,delete?

I use .NET entity framework and mapped my database tables to it. i used stored procedures for insert,update, delete.
then I used EntityDataSource in an ASP.NET application which updates a table.
I don't change all the fields of the entity. there are some fields left unused.
the problem is that when the EntityDataSource performs Update Command. It tries to update ALL fields in the entity. so unused fields receive wrong values.
Is There any simple solution using entity framework designer ?
for example can i use original values for non-modified fields?

Don't use a stored procedure.
Unfortunately that's the only answer I have. A SP expects to get the values it's putting in, you can't tell it to only call with some of the parameters filled in.
If you're just letting EF do the updates without a SP, it should be able to handle this more intelligently.

Entity Framework Function Import when a Stored Procedure has two Result Sets

I have a stored procedure that our DBA wrote and I would like to map it to a function import in Entity Framework. This stored procedure returns two result sets. How is this handled in EF? Will I need to make the DBA write two stored procedures, one for each result set? Or is EF capable of handling this scenario?
Thanks in advance!

Doesn't work out of the box afaik, but have a look at the ADO.NET Entity Framework Extensions

Call stored procedure from LINQ (with dbcontext)

Hello everybody
With EF4, i can map a EDMX function (with "update model from database" and add a stored procedure from the list) to a linq method by using a small snippet like this
[EdmFunction("MYPROJECT.Store", "Foo")]
public Decimal Foo(Int32 Id)
{
throw new NotSupportedException("Not direct access possible, use with E-SQL or LINQ");
}
But this seems not working with EF 4.1
I see that stored procedures don't work with Code First.
I'm using DbContext, is it normal that i can't do that ?
If yes, how can i make my stored procedures working ?
Thank's by advance :-)

This is only EDMX related feature and you can't use it with DbContext API code first / fluent API without EDMX. Btw. you mean SQL function and not stored procedure because imported stored procedure results in function import and cannot be called in Linq query. Methods marked with EdmFunction states either for imported SQL functions and model defined functions.
Yes I know, SQL functions appears under the stored procedures branch in the import wizard but that is just "feature" of EDMX designer.
Because you are using database-first with DbContext API and EDMX file you should be able to use EdmFunction without any problem. I just tested it. The problem probably is that your proxy method marked with EdmFunction attribute is not static - it must be static.