Hi ppl,
Now this is very funny,
luk, my company is a small 1, i just completed a project, this is connected to backend (MS SQL). since itis small, my company canot keep a server for the client alone.
now, how can i deploy.
I tld my MD tat the client can make its own computer as a server n hence use it. this can happen.
but, if the client needs to have a server, he/she shud install the sql server. if it is installed there, then the connection string would obviously change, right.......
so now wat i need to knw is, after the client installs the server, the data source wud have changed, how could i get that assembly info, i mean the data source ( the server name) n then put it into my deployed project.
is there anything which does it automatically,
here, i wud give the client just the server cd as well as the setup file, but not the vs code.
is there anything called data source = "Assembly Info" (some thing similar) so tat it takes the name frm the comp itself directly....
plz help me, i have been braking my head for the past week in to this...

I'm not getting it.
You want to build a connectionstring for a sql db on the client host.
in this case just use 'localhost' as data source.

You can use "localhost", but I would make it a "configurable" option. What if they decide to move the database to another computer? Place all user configurable options in a file (text or binary)--in essence make your own ".ini" file. Then read the values from file either when the program is loaded or before trying to connect to the database. Obviously you also need to build an interface that will allow the user to update/change the necessary information. If I it was me, I would make it so that it is easy to add support for different databases. See http://www.connectionstrings.com for connection string info for other databases. Also if you don't really have concurrent transactions occurring you may consider using SQL Server Compact edition providing you meet the requirements of their "Terms and Conditions"--it is a free download from the Microsoft website.

Hi,
use configuration file to store connection string. then read connection string whenever required. this way it will allow to change it whenever you required, even after deploying the project.

Thanks a lot to lqdo,cgeier,DangerDev..
that was a valid piece of info, wil try both the ways possible,
wil get back to u abt this...

the error tat was said was:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

i have a doubt regarding this, shud i put the datasource as
localhost or
Localhost or
Local Host or
'localhost' or
"localhost".

plz do help me with this regard...

the error tat was said was:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

i have a doubt regarding this, shud i put the datasource as
localhost or
Localhost or
Local Host or
'localhost' or
"localhost".

plz do help me with this regard...

I think in the connection string if you give like this it will work:

DataSource = .

Since .(DOT) refers to the current system.

could u plz gimme the complete connection string tat i can i use, wrt the example given by me....
plz do reply...

connectionString="Data Source=.;Initial Catalog=Library;Integrated Security=True"

I think this should help you out. Because . here refers to the current system.