April 30, 2011
Tired of developing ASP.NET web sites with the ASP.NET Development Server (Cassini) or the IIS version that was installed along with your Windows operating system?
Cassini works great in most cases, but sometimes you want to test some functionality (SSL,…) that it cannot handle and you have to go through the hassle of hosting your site in IIS.
Let’s quickly setup IIS Express…
April 25, 2010
Converting one development environment to another can be a painstaking process. You’ve got to take all the code that took months, years to write, test, tweak…etc. and rewrite it in another language. Hopefully after you are done the new code base will pass all of the testcases.
Wouldn’t it be handy if your new development environment provided a way so that you could utilize libraries, components written in the old language? This way you can leverage the power of these existing parts while you rewrite other parts of the application. As time goes by and releases are build you can phase out these parts.
Using the old libraries for certain aspects of the application, you can cut down on costs and development time. Management likes to see progress periodically, especially after you’ve decided to move to a new development environment. And you can gradually ease the transition for the development team as they acquire new skills while still utilizing their existing knowledge.
Let’s make a test case, showing you how to ease the transition from ColdFusion to .NET.
April 10, 2010
This article quickly details the steps you need to perform in order to enable support for the Windows Workflow Foundation (WF) in ASP.NET (classic or MVC). Let’s use a very small demo application to show you how you can do this.
Integrating WF in ASP.NET is something I had to do in the last few projects I worked on. So I thought I’d build a small sample application that shows you the bare minimum of code required in order to achieve this. Let’s build a sample application step by step…
Remark: This article is not a primer on WF. Some basic understanding of WF is required.
April 8, 2010
You are building an e-commerce web application and you need to support several payment methods (Visa, Mastercard…etc.) so that your customers can easily pay their orders. Rather than implementing this yourself you decide to rely on a trusted third-party provider to provide these services for you.
A well-known company from Belgium that provides payment services is Ogone. They provide over 40 international and local payment methods. They handle the payment transactions between your customers, your online shop and the providers of payment methods (e.g. Visa).
Ofcourse you have to pay a small sum for each transaction handled by Ogone, but that buys you integrated fraud protection, security, tools to manage your payments…and much more. The cost of implementing all of this yourself is far greater.
So you signup for an Ogone account and decide to integrate their system into your web application.
How can we realize this? Let’s find out…
October 24, 2009
The ASP.NET membership feature reduces the amount of code you have to write to authenticate users and store their credentials. To quote MSDN:
“The ASP.NET membership gives you a built-in way to validate and store user credentials. You use the ASP.NET membership with Forms authentication and / or with the ASP.NET login controls for authenticating users.”
The membership provider needs to be specified in the Web.config configuration file. You can use your own custom provider or one of the default providers that ships with the .NET Framework, such as the SqlMembershipProvider provider.
All of the user related data is stored in a set of tables used by the ASP.NET membership system. In most cases you’ll use one set of tables per web application. However you can also reuse the same set to store the user credentials of multiple web applications. This effectively enables you to create one web application that acts as a portal allowing you to log in to one of these “virtual” applications.
However this isn’t possible out of the box. You have some work ahead of you, before you can support such dynamic applications.
Let’s get started…
February 21, 2009
It’s been a good two months since the last post. Today I finally found some spare time to write a new article about .NET. This will be the first article on this blog focusing solely on the Entity Framework. More in particular about using the Entity Framework in different environments such as Windows Applications and in an ASP.NET environment.
The Entity Framework has some drawbacks that will hopefully be addressed in the second release, but in its current state it’s already a really useful technology to use for database access.
This article will not discuss every feature of the Entity Framework as that would entail writing an entire book. The primary focus is on how to deal with the ObjectContext in different environments such as a regular Windows Application and a Web Application (ASP.NET). Let’s get started…
December 14, 2008
Last week I was reading some articles about using WCF, the Entity Framework and how to transport entities across the service boundary. One of the articles I encountered included a demo project that made use of the Model View Presenter (MVP) pattern.
Having explored the demo project I thought it might be interesting to write an article about this pattern. Your favorite search engine will happily supply you with a plethora of links to other articles that explain this pattern thoroughly.
For this article I’ve decided to supply a concrete implemention and to focus less on the theory behind the pattern.