F
Flomo Togba Kwele
I am developing a forms app on a Windows XP machine with VS 2005 and also a
copy of SQL Server 2005 Developer.
The target environment is a dedicated server running SQL Server 2005 Standard
and client machines running the VS2005-developed code on Windows XP. Initial
testing looked OK after changing the connection string in the app config file.
However, I get an error whenever I run an app which uses strongly-typed
datasets - Error 26 - Error Locating Server / Instance Specified.
There are six projects in the solution. One is for forms, another is for data
access. I put all the dataset definitions in the latter. I created the datasets
using the Data Sources window and Add New Data Source.
The first time I used that option, it asked me how to log onto the SQL server.
It built a connection string and stored it in the Project settings for the data
access project (Settings.settings). It hard codes the development connection
string into Settings.Designer.vb, but also exposes a readonly property to
retrieve the string. During compilation, it copies this string into the
app.exe.config file, in the <connectionStrings> element of the <configuration>
section.
I changed the value of this connection string on the client running against the
Standard server, but obviously it's not being used when using datasets.
I must be missing something here. How else can I manage connection strings at
deployment?
Thanks, Flomo
--
copy of SQL Server 2005 Developer.
The target environment is a dedicated server running SQL Server 2005 Standard
and client machines running the VS2005-developed code on Windows XP. Initial
testing looked OK after changing the connection string in the app config file.
However, I get an error whenever I run an app which uses strongly-typed
datasets - Error 26 - Error Locating Server / Instance Specified.
There are six projects in the solution. One is for forms, another is for data
access. I put all the dataset definitions in the latter. I created the datasets
using the Data Sources window and Add New Data Source.
The first time I used that option, it asked me how to log onto the SQL server.
It built a connection string and stored it in the Project settings for the data
access project (Settings.settings). It hard codes the development connection
string into Settings.Designer.vb, but also exposes a readonly property to
retrieve the string. During compilation, it copies this string into the
app.exe.config file, in the <connectionStrings> element of the <configuration>
section.
I changed the value of this connection string on the client running against the
Standard server, but obviously it's not being used when using datasets.
I must be missing something here. How else can I manage connection strings at
deployment?
Thanks, Flomo
--