So which string does it use if you set it to "use application config" AND
you set a config setting in the dbml designer? I was thinking it uses
web.config in preference.
Anyway, i've gone down the route of setting the connection string in the
constructor of the DataContext partial class, although I can see Steve's
point about passing in the string and not using the default constructor at
all. I'll probably go that way in the end.
This is weird tho. If I press F5 and debug my Silverlight application
(keeping on topic here ;) it can connect to the database. If I publish the
web site to a local website and run it from a browser it CANT connect to the
database. I tried attaching to the process and debugging it but it's not
hitting any of my breakpoints anywhere. Not sure what's up with that. I
guess the good news is I've managed to duplicate the issue locally, should
make it a bit easier I hope.
cheers,
Stephen
On Thu, Aug 28, 2008 at 9:51 AM, .net noobie <[EMAIL PROTECTED]> wrote:
> so basically you have the two modes...
>
> Mode="ConnectionString", to use the connection string in your .dbml file
>
> or
>
> Mode="WebSettings", it's going to load from the web.config....
>
>
>
>
> On 8/28/08, .net noobie <[EMAIL PROTECTED]> wrote:
>>
>> if you navigate to the folder in windows explorer where the .dbml file
>> is.... then open the .dbml file in not pad you will see it is a xml file...
>>
>> it has things set in there that tell it where to find and which connection
>> string to use
>>
>> On 8/28/08, Stephen Price <[EMAIL PROTECTED]> wrote:
>>>
>>> Have the Serialization Mode set correctly, I knew about that one. I
>>> didn't realise you could remove the connection string from there. That would
>>> possibly help make things clearer. If I know there's only one connection
>>> string it can use then I'll feel happier it's using it. Will give that a
>>> try...
>>>
>>> So how does it know which connections string in the Application config
>>> file to use? and which config file? The one belonging to the assembly or the
>>> web.config? My understanding of how this works is that the assembly has a
>>> nameofassembly.config which is used for things such as Unit tests etc, and
>>> then if you deploy it with a webapp and it has a web.config then the
>>> web.config overrides the assembly's config (does it just ignore it or does
>>> it load one value from assembly config then the same value is over written
>>> when the web.config is loaded?)
>>>
>>> On Thu, Aug 28, 2008 at 8:34 AM, .net noobie <[EMAIL PROTECTED]>wrote:
>>>
>>>> you can also just set it in the properties dialog for the .dbml
>>>>
>>>> and also note (just in case you did not already know) that you should
>>>> set the
>>>>
>>>> "*Serialization Mode*" = *"Unidirectional*"
>>>>
>>>> if you want to send data from the LinqToSql .dbml via a WCF service to a
>>>> Silverlight Application
>>>>
>>>> i attached a pic incase I am not being clear...
>>>>
>>>>
>>>>
>>>> On 8/28/08, Steven Nagy <[EMAIL PROTECTED]> wrote:
>>>>>
>>>>> >> This way you can explicitly control your connection string
>>>>>
>>>>>
>>>>>
>>>>> Or you can just set the connection string to the right one when you
>>>>> instantiate your data context???
>>>>>
>>>>> var db = new MainDataDataContext(SomeHelperClass.DefaultConnectionString);
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *From:* [EMAIL PROTECTED] [mailto:
>>>>> [EMAIL PROTECTED] *On Behalf Of *Jordan Knight
>>>>> *Sent:* Thursday, 28 August 2008 8:37 AM
>>>>> *To:* listserver@ozSilverlight.com
>>>>> *Subject:* RE: [OzSilverlight] Linq to sql
>>>>>
>>>>>
>>>>>
>>>>> Hi Stephen,
>>>>>
>>>>>
>>>>>
>>>>> You are having a tricky few days J
>>>>>
>>>>>
>>>>>
>>>>> Sometimes LINQ to SQL config issues can arise when you have your LINQ
>>>>> classes in another assembly...
>>>>>
>>>>>
>>>>>
>>>>> If this is the case you may be able to get around it by following these
>>>>> steps:
>>>>>
>>>>>
>>>>>
>>>>> · In you LINQ to SQL designer (on the dbml file) – go to
>>>>> Properties and remove the Connection field.
>>>>>
>>>>> · This re-creates the LINQ class with a new constructor that
>>>>> wasn't there before you can utilise to override connection strings
>>>>>
>>>>> · Create a new cs file to house a partial class:
>>>>>
>>>>> public partial class MainDataDataContext
>>>>>
>>>>> {
>>>>>
>>>>> public MainDataDataContext() :
>>>>>
>>>>> base(System.Configuration.ConfigurationManager
>>>>> .ConnectionStrings["someConnSring"].ConnectionString, mappingSource)
>>>>>
>>>>> {
>>>>>
>>>>> OnCreated();
>>>>>
>>>>> }
>>>>>
>>>>> }
>>>>>
>>>>>
>>>>>
>>>>> MainDataDataContext is the same class that was created by the LINQ
>>>>> designer. This way you can explicitly control your connection string.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> *Jordan Knight*
>>>>> Readify - Senior Developer
>>>>>
>>>>> Suite 206 Nolan Tower | 29 Rakaia Way | Docklands | VIC 3008 |
>>>>> Australia
>>>>> M: +61 403 532 404 | E: [EMAIL PROTECTED] | W: www.readify.net
>>>>>
>>>>>
>>>>>
>>>>> *From:* [EMAIL PROTECTED] [mailto:
>>>>> [EMAIL PROTECTED] *On Behalf Of *Stephen Price
>>>>> *Sent:* Wednesday, 27 August 2008 11:17 PM
>>>>> *To:* listserver@ozsilverlight.com
>>>>> *Subject:* [OzSilverlight] Linq to sql
>>>>>
>>>>>
>>>>>
>>>>> Hey all,
>>>>>
>>>>>
>>>>>
>>>>> I was having a problem with my WCF web service talking to the database.
>>>>> I'm using Linq to SQL, and discovered that it stores the connection
>>>>> strings
>>>>> in settings in the project. If the string in the web.config is not found
>>>>> then it falls back to the connection string in the dll. (from settings).
>>>>> That's where I discovered my string seems to be an old string. Anyway I
>>>>> have
>>>>> gotten it talking to my webhost's database again (they moved the SQL
>>>>> server
>>>>> and it stopped working!).
>>>>>
>>>>>
>>>>>
>>>>> The problem i'm having now is that on the server i'm trying to deploy
>>>>> my app to it's got a similar problem, it can't connect to the database. I
>>>>> wrote a command line app to make calls to the same assembly the webservice
>>>>> uses to call the database, and it has no problems connecting.
>>>>>
>>>>> The connection string in the command's config and the string in the
>>>>> web.config is the same. I've tried changing it from (local) to
>>>>> 127.0.0.1 to the subnet ip address and all seem to fail. I see no hits
>>>>> on the database using SQL profiler. It has to be a connection string issue
>>>>> but I can't see it for looking. Any ideas anyone? oh, I've set up my local
>>>>> machine in a similar manner and it works (using (local)) so putting that
>>>>> up
>>>>> on the server you'd think it would work. Could be a cross domain thing but
>>>>> the webservice is working its just the database calls by the webservice
>>>>> are
>>>>> failing.
>>>>>
>>>>>
>>>>>
>>>>> thanks!
>>>>>
>>>>> Stephen
>>>>>
>>>>> p.s. this was the problem I was trying to solve when I hit the other
>>>>> problem I posted earlier today. tough day!
>>>>>
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> OzSilverlight.com - to unsubscribe from this list, send a message back to
>>>>> the list with 'unsubscribe' as the subject.
>>>>> Powered by mailenable.com - List managed by www.readify.net
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> OzSilverlight.com - to unsubscribe from this list, send a message back to
>>>>> the list with 'unsubscribe' as the subject.
>>>>> Powered by mailenable.com - List managed by www.readify.net
>>>>> -------------------------------------------------------------------
>>>>> OzSilverlight.com - to unsubscribe from this list, send a message back to
>>>>> the list with 'unsubscribe' as the subject.
>>>>> Powered by mailenable.com - List managed by www.readify.net
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> .net noobie™
>>>>
>>>> This Framework is not Big Enough for the both of us...
>>>> -------------------------------------------------------------------
>>>> OzSilverlight.com - to unsubscribe from this list, send a message back to
>>>> the list with 'unsubscribe' as the subject.
>>>> Powered by mailenable.com - List managed by www.readify.net
>>>>
>>>
>>> -------------------------------------------------------------------
>>> OzSilverlight.com - to unsubscribe from this list, send a message back to
>>> the list with 'unsubscribe' as the subject.
>>> Powered by mailenable.com - List managed by www.readify.net
>>>
>>
>>
>>
>> --
>> .net noobie™
>>
>> This Framework is not Big Enough for the both of us...
>>
>
>
>
> --
> .net noobie™
>
> This Framework is not Big Enough for the both of us...
> -------------------------------------------------------------------
> OzSilverlight.com - to unsubscribe from this list, send a message back to
> the list with 'unsubscribe' as the subject.
> Powered by mailenable.com - List managed by www.readify.net
>
-------------------------------------------------------------------
OzSilverlight.com - to unsubscribe from this list, send a message back to the
list with 'unsubscribe' as the subject.
Powered by mailenable.com - List managed by www.readify.net
