M
Martin
Hi!
Listen to this:
I have two w2k servers with SQL Server 2000 an the .Net Framework installed.
The first server is called "NET2", the second is called "PAS003".
I have an ASP.NET application, called "manufacturing". In the web.config I
made an application setting for the connectionstring.
The application was build on server NET2, the connectionstring pointed to
NET2.
I copied all the files from NET2 to the PAS003 server, including the visual
studio.net project file.
Now the following thing happens:
When I use visual studio to edit the web.config of PAS003 (because of the
connectionstring), the web.config of NET2 changes. The same thing arround:
when I want to change something on PAS003, I need to open the projectfile on
NET2. This keeps on happening.
Is this some server magic?
Listen to this:
I have two w2k servers with SQL Server 2000 an the .Net Framework installed.
The first server is called "NET2", the second is called "PAS003".
I have an ASP.NET application, called "manufacturing". In the web.config I
made an application setting for the connectionstring.
The application was build on server NET2, the connectionstring pointed to
NET2.
I copied all the files from NET2 to the PAS003 server, including the visual
studio.net project file.
Now the following thing happens:
When I use visual studio to edit the web.config of PAS003 (because of the
connectionstring), the web.config of NET2 changes. The same thing arround:
when I want to change something on PAS003, I need to open the projectfile on
NET2. This keeps on happening.
Is this some server magic?