C# 3.0 in a Nutshell
C# 3.0 in a Nutshell, Third Edition A Desktop Quick Reference

By Joseph Albahari, Ben Albahari
Price: $49.99 USD
£30.99 GBP

Cover | Table of Contents | Forum


Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
Using Custom Datacontext In Linqpad
rekna
post Mar 20 2008, 05:26 PM
Post #1


New Member
*

Group: Members
Posts: 1
Joined: 20-March 08
Member No.: 158



How to use a custom datacontext in LinqPad : http://rekna1.spaces.live.com/blog/cns!...7!133.entry
Go to the top of the page
 
+Quote Post
Terry Aney
post Mar 25 2008, 09:40 PM
Post #2


Active Member
**

Group: Members
Posts: 10
Joined: 25-March 08
Member No.: 169



Without having to create a custom context for all the auto generated DB Schemas LINQPad provides (connections in tree navigator), is there a way to switch between contexts from within same query window?

I guess I just need to know the object types that are created/used by LINQPad by default when connecting to a SQL Server database.
Go to the top of the page
 
+Quote Post
Joseph Albahari
post Mar 26 2008, 10:31 AM
Post #3


Active Member
**

Group: Members
Posts: 20
Joined: 16-February 08
Member No.: 90



QUOTE (Terry Aney @ Mar 26 2008, 06:40 AM) *
Without having to create a custom context for all the auto generated DB Schemas LINQPad provides (connections in tree navigator), is there a way to switch between contexts from within same query window?


If you want to access multiple autogenerated DataContexts from within the same query, the answer is no.

You can interactively change the (single) DataContext for a query via the Database combo at the top.

Regards
Go to the top of the page
 
+Quote Post
Terry Aney
post Mar 26 2008, 08:34 PM
Post #4


Active Member
**

Group: Members
Posts: 10
Joined: 25-March 08
Member No.: 169



Feature, feature, feature? Please?

Don't know if it's of any use to anyone else, but would be great addition for me. Trying to eliminate all the little *.sql 'utility files' I had to do things and changing the DB context would be of great use.

As a temporary work around, I've made 'utility' stored procedures in one DB that access another (eeew)...but that'll only work as long as the DBs are on same box.
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

RSS Lo-Fi Version Time is now: 16th May 2008 - 11:04 AM