Hi Stephen,
You are having a tricky few days :)
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]<mailto:[EMAIL PROTECTED]> | W:
www.readify.net<http://www.readify.net/>
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Price
Sent: Wednesday, 27 August 2008 11:17 PM
To: [email protected]
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<http://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
