After setting up Windows 8 and SQL Server 2012 my ASP.NET applications were not able to access my SQL databases.
Whenever I have to setup a PC in the future, I don't want to waste my time (again) to figure out how I have to configure the users correctly. Here is what I did:
Recently I was asked to implement a reusable filtering mechanism in an ASP.NET MVC application. To be more concrete: A website shows a grid containing arbitrary data. The user should be able to enter a filter for each grid column.
The filters should be generated based on the type of the displayed objects. With that functionality, it is possible to filter every grid in the application with very little effort. Moreover I added a possibility to add custom search criteria.
About one year ago a created a blog engine which was based on ASP.NET MVC 1. Since then technologies have evolved. When ASP.NET MVC 3 was released, I decided to update my blog engine to use the new RazorViewEngine. Instead of MSSQL Express I use Microsoft SQL Server Compact 4.0 together with the new Entity Framework 'Code First' approach.
The most important advantage of Feedburner is the subscriber count. But Feedburner is not an option for everyone, since the address of your feed changes if you move it to Feedburner.
You could redirect requests to your feed to the new address, the disadvantage though is that when someone opens the URL in his browser the browser will show the new address.
In this post I will show an approach how you can get a subscriber count, without moving your feed to Feedburner.
When your use forms on your website, spammers will very soon be trying to inform your visitors about their "great" products. In this post I will show you how to protect your website by using a simple timestamp.
A few weeks ago I decided to start blogging. Since my website existed for some years I chose to write my own blog engine and integrate it into the existing layout. With Oxite an open source engine built on ASP.NET MVC already exists, but it has many features I do not need, thus I started to implement a more lightweight variant.
The intention of the MVCSampleApplication was to build a sample application using the latest .NET technologies.
The ASP.NET MVC application provides a simple guestbook, where users can register and post comments. Administrators may additionally edit and delete comments. Moreover a WPF based client is included, using the same services as the web application.
This article describes the key implementation aspects and overall architecture of the application. It does not contain a step-by-step tutorial explaining every detail, as you find many blog posts discussing all the technologies being used by this project on the internet. The goal here was to put all these technologies together in one application.
When you convert an existing ASP.NET application to ASP.NET MVC you will sooner or later want to handle legacy URLs.
Imagine an ASP.NET application containing the page "YourPage.aspx".
Now you want to redirect request to that legacy URL to the new MVC Action: "Home/YourPage".
I have looked at several implementations on the internet, but none of them was really simple.
Thus I implemented another solution which is really easy to configure.
