app.config changes not being saved

[Eric]

I'm trying to manipulae my app.config file. Below is code to test that I can
remove a ConfigurationSe ction. It looks like its working, but the app.config
file is not changed when I look at it after.

I think it has something to do with the file path; the .FilePath returned
<C:\Projects\My Project\src\Cor e.Tests\bin\Deb ug\MyProject.Co re.Tests.dll.te mp.config>
isn't app.config but I've seen a couple of places that say that
ConfigurationMa nager.OpenExeCo nfiguration(Con figurationUserL evel.None); is
how you get hold of it.

Thanks for helping - Eric

CODE
------
[Test]
public void RemoveASection( ) {
var config =
ConfigurationMa nager.OpenExeCo nfiguration(Con figurationUserL evel.None);
var groups = config.Sections ;
Console.WriteLi ne(config.FileP ath);

if
(config.Section s[DomainObjectMap pingConstants.C onfigurationSec tionName] !=
null) {
var section =
config.Sections[DomainObjectMap pingConstants.C onfigurationSec tionName] ;
Assert.That(sec tion.SectionInf ormation.Name,
Is.EqualTo(Doma inObjectMapping Constants.Confi gurationSection Name));
groups.Remove(s ection.SectionI nformation.Name );
config.Save(Con figurationSaveM ode.Full);
Assert.That(con fig.Sections[DomainObjectMap pingConstants.C onfigurationSec tionName]
== null);
}
}

APP.CONFIG
---------------
<?xml version="1.0" encoding="utf-8" ?>
<configuratio n>
<configSections >
------------
<section name="domainObj ectMappingsConf iguration"
type="Core.Doma in.FactoryFrame work.Configurat ion.DomainMapSe ttings,
Core, Version=1.0.0.0 , Culture=neutral , PublicKeyToken= null"/>
------------
</configSections>

</configuration>

[Hans Kesting]

Eric submitted this idea :

I'm trying to manipulae my app.config file. Below is code to test that I can
remove a ConfigurationSe ction. It looks like its working, but the app.config
file is not changed when I look at it after.

I think it has something to do with the file path; the .FilePath returned
<C:\Projects\My Project\src\Cor e.Tests\bin\Deb ug\MyProject.Co re.Tests.dll.te mp.config>
isn't app.config but I've seen a couple of places that say that
ConfigurationMa nager.OpenExeCo nfiguration(Con figurationUserL evel.None); is
how you get hold of it.

The file that is named app.config in your VS project is renamed to
<assemblyoutput >.config and copied to the build-directory when you
compile the project. I don't know where the ".temp" part is coming
from.

Did you read *that* file after the test was run, or your original
"app.config " file? Any changes will not be copied back...

Hans Kesting

[Eric]

I looked at (read) the original app.config file. Isn't that where changes
should be?
"Hans Kesting" <ne*********@sp amgourmet.comwr ote in message
news:Od******** ******@TK2MSFTN GP05.phx.gbl...

Eric submitted this idea :

>I'm trying to manipulae my app.config file. Below is code to test that I
can remove a ConfigurationSe ction. It looks like its working, but the
app.config file is not changed when I look at it after.

I think it has something to do with the file path; the .FilePath returned
<C:\Projects\M yProject\src\Co re.Tests\bin\De bug\MyProject.C ore.Tests.dll.t emp.config>
isn't app.config but I've seen a couple of places that say that
ConfigurationM anager.OpenExeC onfiguration(Co nfigurationUser Level.None);
is how you get hold of it.

The file that is named app.config in your VS project is renamed to
<assemblyoutput >.config and copied to the build-directory when you compile
the project. I don't know where the ".temp" part is coming from.

Did you read *that* file after the test was run, or your original
"app.config " file? Any changes will not be copied back...

Hans Kesting

[Hans Kesting]

Eric formulated on dinsdag :

I looked at (read) the original app.config file. Isn't that where changes
should be?

No, that file is copied to the build directory and renamed. See your
returned "FilePath" - do you see your changes in *that* file?
This is identical to the "live" situation: there you also don't have
that "app.config " anywhere, just the renamed version: full name of the
project output (including a .dll or .exe extension) plus the (extra)
..config extension.

Hans Kesting

>
"Hans Kesting" <ne*********@sp amgourmet.comwr ote in message
news:Od******** ******@TK2MSFTN GP05.phx.gbl...

>Eric submitted this idea :

>>I'm trying to manipulae my app.config file. Below is code to test that I
can remove a ConfigurationSe ction. It looks like its working, but the
app.config file is not changed when I look at it after.

I think it has something to do with the file path; the .FilePath returned
<C:\Projects\ MyProject\src\C ore.Tests\bin\D ebug\MyProject. Core.Tests.dll. temp.config>
isn't app.config but I've seen a couple of places that say that
Configuration Manager.OpenExe Configuration(C onfigurationUse rLevel.None); is
how you get hold of it.

The file that is named app.config in your VS project is renamed to
<assemblyoutpu t>.config and copied to the build-directory when you compile
the project. I don't know where the ".temp" part is coming from.

Did you read *that* file after the test was run, or your original
"app.config " file? Any changes will not be copied back...

Hans Kesting