>Its nothing big or fancy, just a small ASP.NET app that connects to the data in our VFP app. And I didn't write, John Herring (works for me) wrote it, but thats pretty much how I'd advise starting to work with .NET. Pick out something small and just work through it to get the concepts down. If that app sucks (and ours doesn't, but we are still trying to figure out teh best ways to do certain things), no big loss.

Just the ticket!
I got a request yesterday at work to do a very small app for our intranet. It is a small query app to some data in SQL Server 2000 and an admin page or two to upload a monthly flat file into SQL Server. Nothing fancy and I have two weeks to do it.

I also got approval to install the .Net framework in a test IIS Server from our Info Security office (we're kind o AR at work on information security issues as you can imagine).

The short of it is that I was requested to do this small app in ASP. Period.

As soon as it is in production and I have some spare time I'd like to re-write it using ASP .Net to teach meself then show the differences and advantages to get the ASP .Net ball rolling at work.

Q: In short, what would be the best way to design the original ASP app to make it easier to later rewrite (and very possibly) replace it with ASP .Net?