VS 2005 & Express to SQL "005

[Guest]

I am not sure if this is the proper place to put this query but we have had
no success elsewhere.

Creating a website using VS 2005 and using the "ASP .Net Configutration"
tool updates the database ASPNETDB.MDF. If we move the security and data
tables from Express to a SQL 2005 full version are there any issues other
than changing
the source/instance in the Web.Config file and the machine.config files as
referenced below.

Web.Config:
<add name="ASPNETDBConnectionString" connectionString="Data
Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\ASPNETDB.MDF;Integrated
Security=True;User Instance=True"


machine.config:
<add name="LocalSqlServer" connectionString="data
source=.\SQLEXPRESS;Integrated
Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User
Instance=true" providerName="System.Data.SqlClient" />

 

[Frans Bouma [C# MVP]]

I am not sure if this is the proper place to put this query but we
have had no success elsewhere.

Creating a website using VS 2005 and using the "ASP .Net
Configutration" tool updates the database ASPNETDB.MDF. If we move
the security and data tables from Express to a SQL 2005 full version
are there any issues other than changing
the source/instance in the Web.Config file and the machine.config
files as referenced below.

Web.Config:
<add name="ASPNETDBConnectionString" connectionString="Data
Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\ASPNETDB.MDF;Inte
grated Security=True;User Instance=True"


machine.config:
<add name="LocalSqlServer" connectionString="data
source=.\SQLEXPRESS;Integrated
Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User
Instance=true" providerName="System.Data.SqlClient" />

You shouldn't be needing to alter machine.config. THe full version
doesn't need to attach .mdf files, you just connect to the sqlserver
service using a connectionstring. As datasource you don't specify
..\SQLEXPRESS but the name of the server. You don't attache a file and
that's basicly it.

FB

--