ansaurus

Question

SOLVED: deploying applications that use LINQ to Entities.

Answer 1

+2 A:

Check your app.config file the entity model connection has to point to the right server, the server must be accessible (i.e. your security settings have to be correct and your network set up right). We need more information about your environment. Right now I can only assume you don't know how to connect to a server from your Windows application.

Update: Does this solve your problem? http://www.devart.com/forums/viewtopic.php?t=13286

Richard Hein 2010-03-12 15:39:18

I am doing this to MySql, all my projects currently use datasets, the server is visible and security settings ar OK.

Luiscencio 2010-03-12 15:41:11

Are there any compiler warnings or errors (and yet it completes compilation) at all when you build, or during design time of your entity model? This is just to exclude one possibility.

Richard Hein 2010-03-12 15:49:13

That it is targeting MySql is probably significant....

Richard Hein 2010-03-12 15:50:00

how 'significant'? no there are no warnings about this, only unreachable code...

Luiscencio 2010-03-12 15:53:00

I'm thinking on your dev boxes you have the MySQL assemblies registered in the GAC or otherwise easily found by the CLR, but on your other machines you'll have to ensure those assemblies are loaded correctly. You configuration file must have some section that is pointing to an assembly that it cannot find. Did you try stepping through the code with Debug - Exceptions - CLR Exceptions Thrown checked? Then see if there's an internal file not found exception or something like that.

Richard Hein 2010-03-12 15:56:47

Note that often in app.config files when something is incorrect, i.e. a public key token or whatever, it will end up saying the configuration is invalid, but not bubble up the file not found exception.

Richard Hein 2010-03-12 15:57:49

Also, if you debug on the machine where it works, break right where the exception would be thrown, and check Debug - Windows - Modules and check the paths/versions/tokens on all the MySql related dlls. Make sure they exist in corresponding locations on the machines you are deploying too.

Richard Hein 2010-03-12 15:59:36

It also may be as simple as setting Copy Local = true for CoreLab.MySql.Entity.dll, like the guy ends up doing in the link I provided.

Richard Hein 2010-03-12 16:00:49

I am not using corelab, I am using ADO

Luiscencio 2010-03-12 16:04:13

Same principle, same problem. Instead of Corelab.MySql.Entity.dll, look for MySql.Data and MySql.Data.Entity.dll, in the stack trace in your question, there is only MySql.Data, and it's in your LocalSettings folder. It's not deployed properly. Set copy local = true for both those assemblies in your project. If that doesn't work then there must be an installation required for the provider (which will probably put it in the GAC).

Richard Hein 2010-03-12 16:13:44

do you think that installing the connector on user machines will solve this?

Luiscencio 2010-03-12 16:19:54

Most definitely, but you may not have to install it, you might just have to use copy local = true and ensure they are deployed (i.e. if you have a setup project, make sure those MySql dlls get in there and target the GAC installation folder). If it's faster for you to install the connector, try that, and at least you'll know that the dlls are missing/in the wrong place etc....

Richard Hein 2010-03-12 16:27:10

nope, maybe I need to add the provider to the app.config, can you help me out with this? the dlls are deploying correctly.

Luiscencio 2010-03-12 16:44:14

Your app.config is completely missing everything to do with the provider ... check the app.config you have in your project, it must be different. I am not familiar with all the specific sections. Your deployed app.config file must be totally different than your project app.config.

Richard Hein 2010-03-12 17:44:31

Try this but make sure the key token/version etc... is correct, I am just copying this from some place else .... <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.2.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d" /> </DbProviderFactories> </system.data>

Richard Hein 2010-03-12 17:51:53

thanks, I tried this but maybe I missed something, I just copied it, put the version and token... it works... I love you... not really.. still you deserve half my rep...

Luiscencio 2010-03-12 18:00:44

LOL, well that's good. Cheers!

Richard Hein 2010-03-12 18:25:24

Answer 2

A:

Hey,

Entity Framework uses a custom formatted connection string, so you have to ensure it points to the correct database. The machines also have .NET 3.5 SP 1 installed too, right?

What kind of database are you targeting?

Brian 2010-03-12 15:40:37

I am doing this to MySql, all my projects currently use datasets, the server is visible and security settings ar OK.

Luiscencio 2010-03-12 15:43:49

yes they do have .net 3.5 sp1

Luiscencio 2010-03-12 15:47:03

ansaurus

tags:

views:

answers:

SOLVED: deploying applications that use LINQ to Entities.

related questions