ASP.NET & MYSQL

[Guest]

Hi all,

Is using ASP.NET with MYSQL a plausible option??

Do you loose a lot of functionality???

Is it combersome?? Buggy??

My company is considering migrating to .NET and MYSQL may very well be the
backend they go for, so i am wondering is this combination worth while?

I prefer SQL Server, and think it is the best option personally, but there
is a bit of resistance from our IT department in adopting it...

Cheers,
Adam

 

[Gef.Mongoose]

Hi all,

Is using ASP.NET with MYSQL a plausible option??

Do you loose a lot of functionality???

Is it combersome?? Buggy??

My company is considering migrating to .NET and MYSQL may very well be the
backend they go for, so i am wondering is this combination worth while?

I prefer SQL Server, and think it is the best option personally, but there
is a bit of resistance from our IT department in adopting it...

Cheers,
Adam

The place I am currently contracting at are running some pretty big
portals (100's-1000's of users) written in ASP with a MySQL backend. As
far as I can see there are no performance problems or issues with this
setup, and there have been no true incompatibility issues between ASP
and MySQL, at worst I think some of the providers were re-written to
accommodate MySQL.

 

[Juan T. Llibre]

Yes, it is.

See :

http://www.codeproject.com/aspnet/MySQLMembershipProvider.asp
for sample access code to MySql using ASP.NET 2.0.

 

[Mark Rae]

Is using ASP.NET with MYSQL a plausible option??
Yes.

Do you lose a lot of functionality???

http://www.mysql.com/why-mysql/

All RDBMS do pretty much the same thing at the most basic level. All support
some features that at least one of the others doesn't. E.g. if you need your
RDBMS to run on UNIX, no point evaluating SQL Server...

Only you can decide whether MySQL satisfies all your requirements.

Is it combersome?? Buggy??
No.

My company is considering migrating to .NET and MYSQL may very well be
the
backend they go for, so i am wondering is this combination worth while?

MySQL certainly can't be beaten in terms of cost...

I prefer SQL Server, and think it is the best option personally, but there
is a bit of resistance from our IT department in adopting it...

Well, there's no doubt at all that .NET 2 and SQL Server 2005 were "made for
each other"...

 

[Jacob]

Obviously .NET and MSSQL are tighter integrated, but I have never had
problems using mySQL. Note that stored procedures are not the same and
integration with Visual Studio is MSSQL only unless you buy third party
tools.