Linqpad supports EF DbContext using Devart Oracle provider
Posted: Thu 07 Apr 2011 13:33
All,
Just thought I'd share my findings here. I was testing the new Linqpad beta that supports EF DbContext (CTP5 first and now EF 4.1 RC). And it works with the Devart dotConnect for Oracle provider! Simply point Linqpad to your assembly containing your DbContext derived class, tell it to use the constructor that accepts a string and specify the name of the connection in your web.config / app.config (it does not work if you pass in the connection string itself instead of the name of the connection and it also does not work if you tell it to use the parameterless constructor) and also point Linqpad to your web.config / app.config and it works! Writing linq queries in Linqpad connecting to your Oracle database using the Devart dotConnect for Oracle provider. Isn't it great when it all just works together?
kind regards
Remco
Just thought I'd share my findings here. I was testing the new Linqpad beta that supports EF DbContext (CTP5 first and now EF 4.1 RC). And it works with the Devart dotConnect for Oracle provider! Simply point Linqpad to your assembly containing your DbContext derived class, tell it to use the constructor that accepts a string and specify the name of the connection in your web.config / app.config (it does not work if you pass in the connection string itself instead of the name of the connection and it also does not work if you tell it to use the parameterless constructor) and also point Linqpad to your web.config / app.config and it works! Writing linq queries in Linqpad connecting to your Oracle database using the Devart dotConnect for Oracle provider. Isn't it great when it all just works together?
kind regards
Remco