Hi Don,
Many thanks for replying. Sorry I wasn't very clear in
the last mail, I actually want to avoid imposing anything
atall, on the users, so, let me put it this way -:
On downloading the trial version (of the software)that has
to be tested locally by the user before loading a definite
version to a server of his choice. Considering the fact that
I'll have a connection string(like that below)that'll point
to a local database file(mdf), after the user has downloaded
the software, if he has the Express database installed on
his machine, I was thinking he wouldn't have to do any other
configuration apart from installing the package that
however, would store him the db file on his local drive.
add name="ConnectionString"
connectionString="Data Source=.SQLExpress;integrated
security=true;attachdbfilename=|DataDirectory|DatabaseFileN
ame.mdf;User Instance=True"
providerName="System.Data.SqlClient" />
In other words, do you think it's better to leave the
configuration as is(above) on both versions (both trial and
real)or is it advisable to prepare the db files to be
attached to a sql server db on deploying to the web? I
appreciate.
-----Original Message-----
From: Discussion of writing applications and components
using Visual Basic .NET [mailto:VBDOTNET DISCUSS.DEVELOP.COM] On Behalf Of Don Edwards
Sent: mercoledì 25 ottobre 2006 21.27
To: VBDOTNETDISCUSS.DEVELOP.COM
Subject: Re: [VBDOTNET] Deploying .net applications with SQL
EXPRESS.
From: "Ezeoke, Gregory" <Gregory.EzeokeHILTI.COM>
>For example, I recently found out it's better I set the
"user
>instance" to false so that every connection to the
database
>would go to just one database instead of creating one
for
>every connected user. In short, how best can I configure
>the connection (connection strings ecc.) to the database
so
>that any user could just download and deploy without
>worrying about the data connection configurations. Any
>advice is welcomed. Many thanks in advance.
You can't.
That is, unless you impose a server name upon your users -
which will make them unhappy as it will break existing apps,
file-sharing, printer-sharing, etc.
You need two installation packages.
One for the database. In the course of it, you should
DISPLAY the name of the server machine, and the port
number that the database server is using. (The default
for the latter is 1433. We use a different number for
security reasons.)
And one for the application. This should ASK for the
name of the database server machine (cannot default,
except to localhost, which will be wrong on at least
n-1 machines in an n-user-machine installation) and the
port number (can default to 1433). And store that
information somewhere in its configuration.
Also make sure that if the user already has an existing
SQL Server (inc. MSDE/SQL Server Express) database
server and some database applications, your database
deployment won't destroy them.
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
|