Stored procedure returns int instead of result set

I had a Stored Procedure created in Azure Sql DB and wanted to use it in Entity Framework. Stored Procedures was returning a data set in Sql Server Management Studio but when updated my edmx file and tried to call it from C# code, it was returning a int instead of the result set I was expecting. I found number of users were facing this issue and most of the solutions on net were not working. After spending some 30 minutes I found the solution. In this post I will try to explain the solution steps by step.
Step 1: We need to add SET FMTONLY OFF; as first line of our stored procedure. It will help Entity Framework to find our the list of column Stored Procedure returns.
Step 2: Move to your .edmx and At Model Browser Window/Function Imports find your procedure then double click it. A window will open as shown below

Step 3: Change the return type to complex type and then click on generate complete type button. It will generate a class which will represent the return type of stored procedure.
Now we will be able to use the stored produce and it will return a a list of POCO class which was generated in step 3.

Comments

gcAllowVeryLargeObjects Element

There are numerous new features coming with .NET 4.5 and here, on this blog, you can find several posts about it. But the feature we are goint to talk about today is very exciting, because we were waiting for it more than 10 years. Since .NET 1.0 the memory limit of .NET object is 2GB. This means you cannot for example create array which contains elements with more than 2GB in total. If try to create such array, you will get the OutOfMemoryException. Let’s see an example how to produce OutOfMemoryException. Before that Open Visual Studio 2012, and create C# Console Application, like picture below. First lets create simple struct with two double members like example below: 1 2 3 4 5 6 7 8 9 10 11 12 public struct ComplexNumber { public double Re; public double Im; public ComplexNumber( double re, double im) { ...

Support for debugging lambda expressions with Visual Studio 2015

Anyone who uses LINQ (or lambdas in general) and the debugger will quickly discover the dreaded message “Expression cannot contain lambda expressions”. Lack of lambda support has been a limitation of the Visual Studio Debugger ever since Lambdas were added to C# and Visual Basic. With visual studio 2015 Microsoft has added support for debugging lambda expressions. Let’s first look at an example, and then I’ll walk you through current limitations. Example To try this yourself, create a new C# Console app with this code: using System.Diagnostics; using System.Linq; class Program { static void Main() { float[] values = Enumerable.Range(0, 100).Select(i => (float)i / 10).ToArray(); Debugger.Break(); } } Then compile, start debugging, and add “values.Where(v => (int)v == 3).ToArray()” in the Watch window. You’ll be happy to see the same as what the screenshot above shows you. I am using Visual Studio 2015 Preview and it has some limitati...

An Introduction to Windows Azure Table Storage

Windows Azure Tables are a non-relational, key-value-pair, storage system suitable for storing massive amounts of unstructured data. Whereas relational stores such as SQL Server, with highly normalized designs, are optimized for storing data so that queries are easy to produce, the non-relational stores like Table Storage are optimized for simple retrieval and fast inserts. This article will cover the very basics of Windows Azure Table storage and provide you with resources and suggested topics to continue your learning. Some people, when first learning about the Windows Azure platform, find it hard to understand the purpose of the Table Storage feature. This is especially true of those who are familiar with developing applications using highly relational data. To get a good understanding of how a Key-Value Pair system differs from a traditional relational database you can read Buck Woody’s article on the topic in his continuing series:...

Dot Net Deewane

Search This Blog