All geek questions in one place

ASP.NET 3.5 Without Microsoft SQL Server - What Am I Losing?

I was just assigned a CMS using ASP.net 3.5 and MySQL. I'm partly new to ASP.NET development (enough with C #) and I wonder what basic ASP.NET and general .NET features I lose when I can't use Microsoft SQL Server.

I already know that from Quick Googling I lost LINQ (and I really looked forward to using this to create my model layer!), But I'm not sure what other convenient features I will lose. Because I relied on ASP.net tutorials that assume you are using MS SQL Server, I feel that part of my ASP.net knowledge has simply become invalid.

Thanks!

+4
source share
5 answers

You will not lose LINQ, you will lose LINQtoSQL. LINQ itself is more general, as it can be used in everything that implements iQueryable.

You are losing the SqlDataSource, not the big deal.

You lose the part of the integration that the server explorer does for you with the sql server, again, it doesn't matter.

As far as I'm interested, you are not losing anything very important, and you should not lose any of your .net knowledge. Most examples use the default sql server, but you can easily modify them to use a different database.

There are also some open source .net CMS packages that are already using MySql to watch cuyahoga

+2
source

You can use MySql in several ORMs, one of which is NHibernate. For the most part, you can view it as if you were running SQL Server or Oracle. And with Linq2NHibernate you can get good LINQ syntax.

You will lose the SqlDataSource control, but some claim that it will actually be a blessing :)

And, of course, you lose Linq2SQL. EntityFramework will have third-party adapters MySql, Oracle, and several others shortly after release.

+7
source

As a result of the loss of notification services, you also lose SqlCacheDependency

+2
source

for linq take a look at this.

has mysql linq explorer. http://code2code.net/DB_Linq/

+2
source

Some things that come to mind:

  • asp.net has a nice "automatic" user management (authentication) system. I think this only happens with SQL Server, but there may be a way to make it work with other databases. The tutorials assume that SQL Server is usually (or an embedded database for development)
  • Not applicable to asp.net, but useful for any SQLCLR project, which I find a great addition to sql server. Allows you to delegate the logic that you write at the business level (supporting dll or classes) to the sql server in a package from SP, but SP is written in vb.net/C#
  • Notification Services
0
source

Source: https://habr.com/ru/post/1276606/

More articles:


All Articles