How to go from PHP to ASP

You have options when it comes to what language you use in ASP.NET 2.0. It doesn't make that much of a difference, but I'd probably go with c#. It will look most like php/java. I'd start here with the http://msdn.microsoft.com/practices/apptype/webapps/default.aspx. Their http://msdn2.microsoft.com/en-us/asp.net/default.aspx is pretty comprehensive too. One of my biggest frustrations with earlier versions of ASP.NET was the lack of a decent template component. Check out http://msdn2.microsoft.com/en-us/library/wtxbf3hh.aspx http://aspnet.4guysfromrolla.com/2.0/ generally have a pretty good handle on what's going on in Microsoftland. Oh, and don't forget to take your wallet with you. Microsoft provides a lot of introductory tools for free to get people to invest their time learning their new products, (all the Express versions of Visual Studio, MSDE), but for larger projects their full fledged products like Visual Studio 2005 and SQL Server 2005 cost a pretty penny compared to what you are used to getting for free in PHP/mySQL land. Have fun!

Thanks. mrbugsentry: In PHP, I use both the symfony framework and my own MVC framework, and would like to try to keep the three layers as loosely coupled as possible in ASP as well. So yes, definitely OOP. zackola: But there is a free SQL Server developer edition, AFAIK? The production servers will be the business of my (large corporate) client, which is the reason I need to learn NET in the first place. So I won't need to buy the production versions - correct?

But there is a free SQL Server developer edition, AFAIK? Yes, with limitations.

Yes, with limitations. I don't have experience with ASP.Net, but I develop C# desktop applications, and didn't run into these limitations until I needed to use Crystal Reports. I would really recommend trying the free editions, and figuring out if you really need the professional ones before upgrading. AFAIK, you really shouldn't run into limitations using the express edition of Sql Server, as the limitations are on things like the number of connections allowed, not on what the engine itself can do. Also, as far as database stuff is concerned, there isn't really any reason you can't use MySQL or PostgreSQL just like you would with PHP, as most (all?) major RDMSs have .Net data providers. The app I'm working on uses PostgreSQL. The only problem I've run into is that a lot of the automagic code-generation stuff you can do in Visual Studio is harder to do or impossible, but a lot of that stuff ends up being too simple and limiting anyway. I like http://www.thecodeproject.com for an online resource.