Comments on: ASP vs ASP.NET: Databases http://grantpalin.com/2006/01/16/asp-vs-aspnet-databases/ Code, photos, books, and anything else Thu, 16 Oct 2008 01:58:14 +0000 http://wordpress.org/?v=2.6.2 By: Grant Palin http://grantpalin.com/2006/01/16/asp-vs-aspnet-databases/#comment-170 Grant Palin Tue, 24 Jan 2006 16:58:24 +0000 http://www.grantpalin.com/?p=55#comment-170 That's a good tip. I had mentioned something about the MySQL/.NET connector in the Making Connections section. Installation is not an issue for me on my own computer, but that could indeed be an issue on remote webservers. And of course .NET sites would typically use SQL Server or Access, but still...In fact, I've been working on a project recently which needed to be able to use different database systems (SQL Server, Access, MySQL, Oracle)...The majority of users will have an Access database, but we need to have the option of other databases as well. Although, the source I found the MySQL/.NET information from has the following note: <blockquote cite="http://www.15seconds.com/issue/050407.htm">Note: Even though I selected the option to register Connector/NET in the Global Assembly Cache and when I checked it later I found that it actually was installed there, until I copied the MySql.Data.dll file to my application's /bin folder I couldn't get the import statement to find the Connector/NET's namespace. The exact error message was: BC30466: Namespace or type specified in the Imports 'MySql.Data.MySqlClient' cannot be found. I'm not sure what the problem was/is, but I looked around and it seems some others are having the same issue. So, for the time being, placing another copy of the file from it's installed location (ie. C:\Program Files\MySQL\MySQL Connector Net 1.0.4\bin\.NET 1.1\) to your application's /bin folder (ie. C:\Inetpub\wwwroot\bin\) should resolve the issue.</blockquote> So by simply having the MySQL.Data.dll file in your app's \bin directory seems to work. That's the nice thing about .NET: if you need some library or another, simply put it in your project's \bin folder, and you have access to that library. It works for me anyway. It might or might not work on a remote server. That’s a good tip. I had mentioned something about the MySQL/.NET connector in the Making Connections section. Installation is not an issue for me on my own computer, but that could indeed be an issue on remote webservers. And of course .NET sites would typically use SQL Server or Access, but still…In fact, I’ve been working on a project recently which needed to be able to use different database systems (SQL Server, Access, MySQL, Oracle)…The majority of users will have an Access database, but we need to have the option of other databases as well.

Although, the source I found the MySQL/.NET information from has the following note:

Note: Even though I selected the option to register Connector/NET in the Global Assembly Cache and when I checked it later I found that it actually was installed there, until I copied the MySql.Data.dll file to my application’s /bin folder I couldn’t get the import statement to find the Connector/NET’s namespace. The exact error message was:

BC30466: Namespace or type specified in the Imports ‘MySql.Data.MySqlClient’ cannot be found.

I’m not sure what the problem was/is, but I looked around and it seems some others are having the same issue. So, for the time being, placing another copy of the file from it’s installed location (IE. C:\Program Files\MySQL\MySQL Connector Net 1.0.4\bin\.NET 1.1\) to your application’s /bin folder (IE. C:\Inetpub\wwwroot\bin\) should resolve the issue.

So by simply having the MySQL.Data.dll file in your app’s \bin directory seems to work. That’s the nice thing about .NET: if you need some library or another, simply put it in your project’s \bin folder, and you have access to that library. It works for me anyway. It might or might not work on a remote server.

]]> By: Kevin http://grantpalin.com/2006/01/16/asp-vs-aspnet-databases/#comment-169 Kevin Tue, 24 Jan 2006 07:39:00 +0000 http://www.grantpalin.com/?p=55#comment-169 It should also be noted that if you are using MySQL databases with ASP.NET (Or any other form of the .NET framework) MySQL publishes <a href="http://dev.mysql.com/doc/refman/5.0/en/connector-net.html" rel="nofollow">their own database objects</a> for use with .NET. Of course if you are using .NET on the web you'll probably not be able to install them on the server unless you run it and usually Windows web servers with IIS usually use MsSQL or Access for database. However I still thought I'd mention it. It should also be noted that if you are using MySQL databases with ASP.NET (Or any other form of the .NET framework) MySQL publishes their own database objects for use with .NET. Of course if you are using .NET on the web you’ll probably not be able to install them on the server unless you run it and usually Windows web servers with IIS usually use MsSQL or Access for database. However I still thought I’d mention it.

]]>