asp.netmysql.net-3.5

ASP.NET 3.5 Without Microsoft SQL Server - What do I lose?


I was just assigned to do a CMS using ASP.net 3.5 and MySQL. I am kind of new to ASP.NET development (quite sufficient with C#) and I am wondering what major ASP.NET and general .NET features I am losing when I don't have the option to use Microsoft SQL Server.

I know already from quick Googling that I lose LINQ (and I was really looking forward to using this to build my model layer!), but I am not sure what other handy features I will lose. Since I've been relying on ASP.net tutorials which assume that you use MS SQL Server, I feel a chunk of my ASP.net knowledge just become invalid.

Thanks!


Solution

  • You do not lose LINQ, you lose LINQtoSQL. LINQ itself is more generic as it can be used on anything that implements iQueryable.

    You lose the SqlDataSource, not a big deal.

    You lose some of the integration the server explorer does for you with sql server, again not a big deal.

    As far as im concerned you dont lose anything very important, and you shouldnt be losing any of your .net knowledge. Most examples use sql server as a default but they can easily be changed to use another database.

    Also there are a few open source .net CMS packages out there already that use MySql take a look at cuyahoga