Why a new DbProviderFactory for SQL Compact Edition Error Log?

[GoogleCodeExporter]

Don't get me wrong, this is an excellent piece of work!

I'm just wondering why the Nuget package for SQL Compact removes the 
System.Data.SqlServerCe.4.0 provider and then recreates it with a different 
name.

As far as I can see removing that part (and add the default 
providerName="System.Data.SqlServerCe.4.0" to the created connection string) 
appears to work just as well.

Let me know if you require more information.

Original issue reported on code.google.com by fjtdegr...@gmail.com on 30 Jul 2011 at 10:30

[GoogleCodeExporter]

Sorry, this appears to be an issue between the SQL CE package installed by the 
Web Platform Installer and the SQL CE Nuget package that the Elmah SQL CE 
package depends upon.

Original comment by fjtdegr...@gmail.com on 30 Jul 2011 at 11:16

[GoogleCodeExporter]

Original comment by azizatif on 1 Aug 2011 at 3:03

[GoogleCodeExporter]

Assume this is what you refer to:
  <system.data>
    <DbProviderFactories>
      <remove invariant="System.Data.SqlServerCe.4.0" />
      <add name="Microsoft SQL Server Compact Data Provider 4.0" invariant="System.Data.SqlServerCe.4.0" description=".NET Framework Data Provider for Microsoft SQL Server Compact" type="System.Data.SqlServerCe.SqlCeProviderFactory, System.Data.SqlServerCe, Version=4.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" />
    </DbProviderFactories>
  </system.data>

But I see the exact same entry in both a web.config (that has the 
SQLServerCompact NuGet package) and my machine.config !?

Original comment by ejls...@hotmail.com on 1 Aug 2011 at 3:45

[GoogleCodeExporter]

(Sorry for the late reply)
Yeah, that's the section I was referring to.
I guess it assumes SQL CE was not installed with the WPI into the GAC. Perhaps 
they could make the NuGet package smarter to not update the web.config when SQL 
CE is already installed using WPI into the GAC and machine.config. But I guess 
they didn't bother.

If NuGet dependencies could be set to either the SQL CE WPI installer or the 
NuGet SQL CE package that would be a little more efficient, but I don't think 
that is possible.

Original comment by fjtdegr...@gmail.com on 19 Aug 2011 at 10:43

[GoogleCodeExporter]

I understand where you are coming from, but I think this is really more of an 
issue for the NuGet team. Perhaps you could raise an issue there and 
cross-reference it here so that we can follow its progress??

We need to have a dependency on the SQL CE NuGet package, and that lies well 
outside our control!

Original comment by jamesdriscoll71 on 19 Aug 2011 at 10:58

• Changed state: WontFix

[GoogleCodeExporter]

Yeah, that was what I was trying to say earlier, sorry for the confusion.

Original comment by fjtdegr...@gmail.com on 20 Aug 2011 at 11:02