Configuration Files VS.Net 2003

[Dave Girvitz]

Yesterday I was giving a presentation on the Trace Class to my user's group.
For the purposes of the presentation, I wrote a quick app that used a
configuration file to set the TraceLevel of my switch. I wrote the app
under C#\VS.Net 2002 and hand wrote the config file.

When I opened the application up at the presentation, I got the upgrade
wizard and upgraded the app to VS.Net 2003. However, everytime I compiled
the application, I found that the configuration file got deleted. (I copied
the config file to both the debug and release directories).

Is this normal behavior for VS.Net 2003? If so, how do you properly
genrate/attach a config file to an application in VS.Net 2003?

As a side note, I've heard there were some minor changes to remoting
configuration in VS.Net 2003/.Net 1.1. Where can I find a list of the
changes?

Thanks,
Dave Girvitz, MCAD
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.502 / Virus Database: 300 - Release Date: 07/18/2003

[Jay B. Harlow [MVP - Outlook]]

Dave,
This is normal.

Microsoft fixed a 'feature' of VS.NET 2002 in VS.NET 2003. :-|

You need to add your config file to your VS.NET project's root folder as
app.config, it needs to be named "app.config" without the quotes. When you
build your project VS.NET (both 2002 & 2003) will copy the app.config file
from the project root to your output folder and name it appropriately
(myproject.exe.config).

Hope this helps
Jay
"Dave Girvitz" <dg******@hotmail.com> wrote in message
news:OP*************@tk2msftngp13.phx.gbl...

Yesterday I was giving a presentation on the Trace Class to my user's group. For the purposes of the presentation, I wrote a quick app that used a
configuration file to set the TraceLevel of my switch. I wrote the app
under C#\VS.Net 2002 and hand wrote the config file.

When I opened the application up at the presentation, I got the upgrade
wizard and upgraded the app to VS.Net 2003. However, everytime I compiled
the application, I found that the configuration file got deleted. (I copied the config file to both the debug and release directories).

Is this normal behavior for VS.Net 2003? If so, how do you properly
genrate/attach a config file to an application in VS.Net 2003?

As a side note, I've heard there were some minor changes to remoting
configuration in VS.Net 2003/.Net 1.1. Where can I find a list of the
changes?

Thanks,
Dave Girvitz, MCAD
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.502 / Virus Database: 300 - Release Date: 07/18/2003

[Dave Girvitz]

Thanks
Dave

"Jay B. Harlow [MVP - Outlook]" <Ja********@email.msn.com> wrote in message
news:ux**************@TK2MSFTNGP09.phx.gbl...

Dave,
This is normal.

Microsoft fixed a 'feature' of VS.NET 2002 in VS.NET 2003. :-|

You need to add your config file to your VS.NET project's root folder as
app.config, it needs to be named "app.config" without the quotes. When you
build your project VS.NET (both 2002 & 2003) will copy the app.config file
from the project root to your output folder and name it appropriately
(myproject.exe.config).

Hope this helps
Jay
"Dave Girvitz" <dg******@hotmail.com> wrote in message
news:OP*************@tk2msftngp13.phx.gbl...

Yesterday I was giving a presentation on the Trace Class to my user's

group.

For the purposes of the presentation, I wrote a quick app that used a
configuration file to set the TraceLevel of my switch. I wrote the app
under C#\VS.Net 2002 and hand wrote the config file.

When I opened the application up at the presentation, I got the upgrade
wizard and upgraded the app to VS.Net 2003. However, everytime I compiled the application, I found that the configuration file got deleted. (I

copied

the config file to both the debug and release directories).

Is this normal behavior for VS.Net 2003? If so, how do you properly
genrate/attach a config file to an application in VS.Net 2003?

As a side note, I've heard there were some minor changes to remoting
configuration in VS.Net 2003/.Net 1.1. Where can I find a list of the
changes?

Thanks,
Dave Girvitz, MCAD
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.502 / Virus Database: 300 - Release Date: 07/18/2003

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.502 / Virus Database: 300 - Release Date: 07/18/2003