.config in control

This is the problem:

When dragging the user control to the windows onto the windows forms designer, the designer will actually create an instance of the control. This will execute all the code in the InitializeComponent method, including the call where the user control tries to get the value from the application's configuration file. The problem is that the application that created the user control is Visual Studio, so the user control will end up looking in devenv.exe.config for the dynamic property, not in the app.config in your project.

So, how do you solve this?

If you are using Visual Studio 2005, I'd recommend moving away from dynamic properties and use the settings designer/client configuration instead.

If you are using Visual Studio 2003, I would suggest that instead of binding the property in the user control, you add a public property on the user control. You can then use dynamic properties in your windows application that you wanted to add your user control to and bind this new property to a value in app.config. This way, the dynamic property should be defined correctly in the app.config file in the windows application, and things should work as expected.

Best regards,
Johan Stenberg

JohanStenberg at 2007-9-9 >

Johan Stenberg wrote:

If you are using Visual Studio 2003, I would suggest that instead of binding the property in the user control, you add a public property on the user control. You can then use dynamic properties in your windows application that you wanted to add your user control to and bind this new property to a value in app.config. This way, the dynamic property should be defined correctly in the app.config file in the windows application, and things should work as expected. Best regards, Johan Stenberg

As i understand it. I will lose some designtime futures Such as databinding in the usercontrol

RemcoJVG at 2007-9-9 >