How to make db context reachable in the whole project, when using EF connection string built at runtime.

Samio

How to make db context reachable in the whole project, when using EF connection string built at runtime ?

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Vulpes14y ago
Accepted answer
The compiler treats:

using (var ctx = new Entities(conn))

as though it were written:

using (Entities ctx = new Entities(conn))

As 'var' can't be used when declaring fields (only local variables), just use the type name instead:

public static Entities ctx;

There is no performance implication in doing so.

I suppose you could say that a public global variable is less secure than a local variable because it can be accessed by any other code within the application but, as this is what you're wanting to achieve anyway, I wouldn't worry about it.
Samio14y ago
Many thanks my friend.
Samio14y ago
Hi Jaish,
In my connection form I have this:

using (EntityConnection conn = new EntityConnection(Global.Cnx))
{
conn.Open();
using (var ctx = new Entities(conn))
{
var qry = ...
}
conn.Close();
}
I need to use ctx in the whole project, how can I declare it as Global since public static var is not accepted.

it is there a disadvantage in terms of safety and performance if it is used in this way.
Jaish Mathews14y ago
Scope of DB Context to be inside your DAL only. So providing it's access to the whole application, making the usage of EF meaning less. You need to add EF Ref. to each proj or you create a custom DB Context class deriving from DBContext in side a separate library to give REf. to whole proj.