Hi,

Just to say I've got round to creating a NuGet package, and adding 
documentation about how to use the facility to the GitHub page.

All the info about it should be in the readme 
at https://github.com/adamconnelly/WindsorAppConfigFacility.

If you fancy adding this to the site, that would be really cool.

Cheers,
Adam

On Friday, October 10, 2014 1:28:18 PM UTC+1, adam.rp...@gmail.com wrote:
>
> That's fine by me. In that case I'll look into putting it up on nuget / 
> symbol source, and add decent documentation to the github page.
>
> On Thursday, October 9, 2014 1:58:50 PM UTC+1, adam.rp...@gmail.com wrote:
>>
>> Hi,
>>
>> I haven't seen anything like this that comes as part of Windsor, but 
>> apologies in advance if I've just ended up reinventing the wheel.
>>
>> I tend to create interfaces for accessing app config settings so that I 
>> can easily mock them when writing unit tests. What I found myself doing was 
>> ending up having to alter a concrete class with boiler plate code each time 
>> I added a new setting to an application, which was starting to get a bit 
>> annoying. So what I ended up doing was creating a Windsor facility that 
>> uses dynamic proxy to automatically implement a settings interface, so I 
>> don't have to update stuff in two places.
>>
>> For example, say I've got some settings like:
>>
>> <appSettings>
>>     <add key="Zendesk.Url" value="abc.zendesk.com"/>
>>     <add key="Zendesk.ApiToken" value="aaaaaaaaa"/>
>>     <add key="Git.Email" value="a...@email.com"/>
>>     <add key="Git.Name" value="Adam Connelly"/>
>> </appSettings>
>>
>> And a couple of interfaces:
>>
>> public interface ZendeskConfig
>> {
>>     string Url { get; }
>>     string ApiToken { get; }
>> }
>>
>> public interface GitConfig
>> {
>>     string Email { get; }
>>     string Name { get; }
>> }
>>
>> You can configure your container like this:
>>
>> var container = new WindsorContainer();
>> container.AddFacility<AppConfigFacility>();
>>
>> container.Register(
>>     Component.For<IZendeskConfig>().FromAppConfig(c => 
>> c.WithPrefix("Zendesk.")),
>>     Component.For<IGitConfig>().FromAppConfig(c => c.WithPrefix("Git."))
>> );
>>
>> Then just resolve them / inject them as normal.
>>
>> It also supports getting the settings from Azure, caching, and computed 
>> properties currently.
>>
>> The code's available on Github at 
>> https://github.com/adamconnelly/WindsorAppConfigFacility.
>>
>> What I'm wondering is whether you'd be interested in adding this to 
>> Windsor, and if so, what would I need to change for you to accept it. I'm 
>> more than happy to reformat any files to suit your code format, and make 
>> any changes where I've missed stuff.
>>
>> Cheers,
>> Adam
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Castle Project Development List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to castle-project-devel+unsubscr...@googlegroups.com.
To post to this group, send email to castle-project-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/castle-project-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to