Howto make MySQL & Entity Framework work with your website when your hosting company does not have Connector/Net installed

I installed MySQL’s Connector/Net v6.2 on my dev machine and used the Entity Framework to query a MySQL server without any problems.  Then I uploaded the same code to my hosting company’s server and I kept getting errors telling me “Unable to find the requested .Net Framework Data Provider”.  In order to make it work, I had to do the following:

  1. Uploaded MySql.Data.dll to my bin directory
  2. Uploaded MySql.Data.Entity.dll to my bin directory
  3. Added the following lines to my web.config file:

<?xml version=”1.0″?>
<configuration>

<system.data>

<DbProviderFactories>

<add name=”MySQL Data Provider” invariant=”MySql.Data.MySqlClient” description=”.Net Framework Data Provider for MySQL” type=”MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data, Version=6.2.0.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d” />

</DbProviderFactories>

</system.data>


</configuration>

I hope this saves someone else some headaches!

Rob

Win7 on JFL92 / PowerNotebook PowerPro P 11:15

After installing Windows 7 x64 on my PowerPro P 11:15, I still had some devices in Device Manager without drivers.  Included in this list were the following:

Base System Device

  • Hardware ID: PCI\VEN_1180&DEV_0843&SUBSYS_002514C0&REV_12
  • This is actually a “Ricoh SD/MMC Host Controller”
  • Solution: Installed setup.exe from \08.CardReader\3.51.01(WHQL).zip

Base System Device

  • Hardware ID: PCI\VEN_1180&DEV_0592&SUBSYS_002514C0&REV_12
  • This is actually a “Ricoh Memory Stick Controller”
  • Solution: Installed setup.exe from \08.CardReader\3.51.01(WHQL).zip (solving the Ricoh SD/MMC Host Contoller above will solve this simultaneously)

PCI Memory Controller

  • Hardware ID: PCI\VEN_8086&DEV_444E&SUBSYS_444E8086&REV_01
  • This is actually the “Intel Turbo Memory Controller (Robson cache)
  • I still haven’t gotten this working.

Unknown Device

Unknown Device

Equivalent Notebook Models

PowerPro P 11:15

Compal JFL92

Similar to Sager NP2090/COMPAL IFL90/PowerPro J 10:15 — these are all the same model and are lower-end than the NP2092

According to Sager, the NP2090, NP2092, FL90, and JFL92 all use the same drivers

Resellers:

Getting DotNetNuke 5 to install

Another hosting company I use has both the old ASP.NET AJAX extensions installed and the .NET Framework 3.5 installed.  In order to resolve an ambiguity between the two sets of DLLs in the GAC, I had to modify web.config according to the instructions here:

http://weblogs.asp.net/javiervillarreal/archive/2008/01/30/the-type-system-web-ui-scriptmanager-is-ambiguous-it-could-come-from-assembly.aspx

XP SP3 cannot connect to Vista Ult SP1

I could not get our Windows XP SP3 machine to connect to our Vista SP1 “server” machine.  I found the solution at:

http://www.techsupportforum.com/microsoft-support/windows-vista-support/227510-solved-vista-sp1-changed-sharing-behavior.html

Solution: The XP machine’s Local Security Policy had to be changed to enforce NTLMv2.

The user’s problem was described as follows:

I upgraded Vista Ultimate to SP1 today and after the update, I can no longer see the folder and device shares that used to be visible to another computer running XP SP2. If I try NET VIEW from the XP computer, I get “System error 58 has occurred” and no information. Priot to the upgrade, all of the network shares were visible to my XP computers. I also upgraded a laptop computer running Vista Home Premium to SP1, and it has no problem seeing the shares across the network, so the problem appears to be particular to either XP or maybe any non-Vista OS. Ideas?

And this was the solution:

I’ve solved the problem of not being able to see network shares on my Vista machine from an XP machine after installing Vista SP1. The problem was authentication level for LAN Manager. Vista defaults to NTLMv2, and my Vista machine only allowed that level. My XP machine was set for LM & NTLM, but did not deal with NTLMv2. I solved the problem by going into Local Security Policy on both machines and changing the Network security: LAN Manager authentication level to “Send LM & NTLM – use NTLMv2 session security if negotiated” on both. I had to reboot to have the change take effect, and the problem was eliminated.

Load more