Entity Framework is an ORM layer for .NET applications. Sometimes, we import data from a flat file. Technically, this boils down to: Delete all records from the table. And insert new records into the table.
Below is the first cut of code that I wrote. A logical use of Entity framework. But unexpectedly, yields very poor performance.
// delete data foreach(Employee emp in context.Employees)…
ASP.NET Web API is the framework for creating HTTP services or RESTful services in the Microsoft platform. It super-cedes the WCF framework. Browsers in desktops, tablets or mobiles can access the Web API.
In this post, we create a Web API for Comments. Create a new MVC application. Create a controller called CommentController. It is an API controller with CRUD methods and integrates with Entity Framework.…
Sometimes, a controller action trigger a long running background process. For example, the user clicks a link in the page. Generate a word document in the background. Show the properties of the document in the subsequent page. Generation of word documents take anywhere between 3 seconds to 30 seconds. During this time, the user needs some feedback about the progress of the operation.…
ASP.NET MVC offers TempData. TempData, as the name implies, is a temporary storage. It retains the data between two user requests but no more. By default, it uses the SessionState for storing data. A web farm has multiple servers having the application. Subsequent requests do not go to the same server. So, using session for storing TempData is not a viable solution.…
jQuery UI has an AutoComplete widget. The widget is quite nice and straight forward to use. In this post, we will see how to integrate the widget with an ASP.NET MVC application.
The first step is to add the jQuery scripts and styles into bundles. There is a script bundle for jQuery. And another script bundle for jQuery UI.…
How is Entity Framework different from LINQ to SQL? There is already a question in StackOverflow. Both technologies are somewhat similar. They provide an ORM framework. But, there are some important differences. LINQ to SQL has several limitations.
LINQ to SQL works only with SQL Server, especially SQL 2005 and above. It works in a limited way with SQL 2000.…
Consider the following code which has a CheckBox and a submit button:
@using (Html.BeginForm())
{
<input type="checkbox" name="Select" />
<input type="submit" value="Submit" />
}
Submit the form. The request body has the form data with name-value pairs. If the user checks the checkbox, the form data has Select=on. If the user clears the checkbox, the form data does not contain Select.…
Consider a GridView with a checkbox column. We want to select all checkboxes or clear all checkboxes within this column using a Select All checkbox in the header row.
The GridView has a template column. Template defines the header row as well as the item row. In the header row, we have the Select All checkbox. And within in the item row, we have a checkbox to select an item.…
I have posted earlier on moving items from one ListBox to another. We use jQuery to do that. Listbox posts only the selected values to the server. In our case, we are not making any selections. But rather moving the Listbox options. We need a way for the server to know that the options have changed. So, I have come up with a solution in this post.…
A data-tier application (.dacpac) creates or updates database schema for SQL Server. Usually, database administrators deploy the application in SQL Server using Management Studio (SSMS). Sometimes, we have to deploy the application programatically. This post explains how to deploy a data-tier application to SQL Azure using .NET.
While deploying using a program, we use a background task, typically a worker role in Azure.…