The previous developer used MS Frontpage 2003 to create this ASP website. He included in every page the strings to send data back and forth to SQL Server 2000. I am now creating some pages using Visual Studio 2005 Beta. I have a problem with the asp.net strings and webconfig. Does anyone know how to fix this problem without redoing any of the code in the pre-existing pages?
There seems to be a conflict. When I have the script in webconfig for the VS pages to connect to SQL, the previous pages, made with Frontpage 2003, will not connect. When the script is not in, of course the VS pages will not work.
The new config file
<!-- Web.Config Configuration File -->
<configuration>
<connectionStrings>
<add name="ADFGrantManagementConnectionString" connectionString="Data Source=ARIES;Initial Catalog=ADFGrantManagement;Persist Security Info=True;User ID=ADFWebUser;Password=adf"
providerName="System.Data.SqlClient" />
</connectionStrings>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
The old config file
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
There seems to be a conflict. When I have the script in webconfig for the VS pages to connect to SQL, the previous pages, made with Frontpage 2003, will not connect. When the script is not in, of course the VS pages will not work.
The new config file
<!-- Web.Config Configuration File -->
<configuration>
<connectionStrings>
<add name="ADFGrantManagementConnectionString" connectionString="Data Source=ARIES;Initial Catalog=ADFGrantManagement;Persist Security Info=True;User ID=ADFWebUser;Password=adf"
providerName="System.Data.SqlClient" />
</connectionStrings>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
The old config file
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>