By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,353 Members | 1,555 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,353 IT Pros & Developers. It's quick & easy.

Connection problem in 2005

P: n/a
Hello,
I've just upgraded from .NET 2003 to 2005 and to SQL Server Express 2005.

I've rebuilt my connection string. Before I used app.config, and now have
the connection string is in the settings.settings.
This works great for debugging/running on my machine, but I'm not sure how
to deploy this and install on another machine.
With 2003, in my app.config file, I had several connection strings, all but
the one I needed commented out (so when I was working on my machine, I had it
set to my connection, before I deployed, I'd change the connection string to
the machine I was putting it on).
I can't get the current connection string to work when I install on another
machine.
My old string was:

<add key="SqlDb.DbConnection" value="packet size=4096;user id=sa;integrated
security=SSPI;data source=MKKCT;persist security info=False;initial
catalog=FSIS"

How can I recreate this in settings.settings so it will work when I deploy it?

TIA,
Amber
Nov 23 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi,

All the information on Settings.Settings are saved automatically in your
App.Config file. So really VS 2005 has made it very simple to access config.
And another aded feature is that you can actually save changes to your
app.config through settings.

Fitim Skenderi
"amber" <am***@discussions.microsoft.com> wrote in message
news:94**********************************@microsof t.com...
Hello,
I've just upgraded from .NET 2003 to 2005 and to SQL Server Express 2005.

I've rebuilt my connection string. Before I used app.config, and now have
the connection string is in the settings.settings.
This works great for debugging/running on my machine, but I'm not sure how
to deploy this and install on another machine.
With 2003, in my app.config file, I had several connection strings, all
but
the one I needed commented out (so when I was working on my machine, I had
it
set to my connection, before I deployed, I'd change the connection string
to
the machine I was putting it on).
I can't get the current connection string to work when I install on
another
machine.
My old string was:

<add key="SqlDb.DbConnection" value="packet size=4096;user
id=sa;integrated
security=SSPI;data source=MKKCT;persist security info=False;initial
catalog=FSIS"

How can I recreate this in settings.settings so it will work when I deploy
it?

TIA,
Amber

Nov 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.