elmah during install places connection string in wrong place if configSource is specified

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create web.config that uses configSource attribute on connectionStrings 
section
2. Install elmah 1.2 via nuGet
3.

What is the expected output? What do you see instead?
I expect the connection string placed into the file specified in the 
configSource attribute, but instead it places the new connection string in the 
connectionString section which then throws an error because you can't put them 
there if the configSource attribute is specified.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by kingmot...@gmail.com on 14 Sep 2011 at 3:09

[GoogleCodeExporter]

This is an issue with NuGet itself rather than the ELMAH packages, and should 
be raised there.

The only way round it from ELMAH's perspective would be to write some heavy 
duty Powershell scripts for install and uninstall which would completely negate 
all the goodness of NuGet, and be a LOT harder to maintain.

Even then, there would be boundary cases where it would likely fail!

Original comment by jamesdriscoll71 on 14 Sep 2011 at 3:27

• Changed state: WontFix