castle-windsor

My application uses the "SignalR" client/server comms framework. If you aren't familiar with it, the server-side app typically contains one or more "hub" classes (similar to asmx web services), each providing methods that can be called by a client. During startup, the client needs to first create a connection, then create a "proxy" for each hub that it will need to talk to, e.g.:- var hubConnection = new HubConnection("http://..."); var fooHubProxy = hubConnection.CreateHubProxy("FooHub"); var barHubProxy = hubConnection.CreateHubProxy("BarHub"); ...etc... The string parameter passed to

I would like to take advantage of the new task-based operations for a WCF client. I am currently using the WCFFacility as follows: container.Register(Component .For<IAdminService>() .LifeStyle.Transient .AsWcfClient(new DefaultClientModel() { Endpoint = WCFHelpers.BasicHttp(settings.MaxReceivedMessageSize) .At(addr) })); where IAdminService is the ServiceContract class. All the MSDN articles about task-based operations refer to setting a 'task based operations' tick box when importing the service reference. But in the style I am currently using, there is no imported service reference because I

I'm new to asp.net core. What I'm trying to do is to build multi projects solution and use dependency injection to pass interfaces between projects. What I know is that in ASP.NET core project we have ConfigureServices method in startup.cs file to register our interfaces and their implementations like this: public void ConfigureServices(IServiceCollection services) { // Add framework services. services.AddMvc(); services.AddTransient<IMyInterface,MyImplementation>(); ..... } This is good if you have classes all in the same project, but what if I have multi projects ? Usually what I'll do is

If you are using the LoggingFacility in Castle Windsor the container will automatically resolve the logger associated with your class if you have optional logger dependencies in your class (an ILogger property that castle can inject the logger into), but how can I leverage the facility if I want to implement the logging using AOP (interceptor approach)? I basically want to write something like: public void Intercept(IInvocation invocation) { ILogger logger = LogManager.GetLogger(invocation.TargetType); //.. } But there is no LogManager to speak of in the Castle framework. What is the best

I have an abstract base class Search . An abstract class IndexedRepositorySearch descends from Search . An abstract class FacetSearch descends from IndexedRepositorySearch . Concrete classes IngredientFacetSearch and RecipeFacetSearch descend from FacetSearch . Currently we're registering everything that descends from Search with Castle Windsor as follows: AllTypes.FromAssembly(assembly) .BasedOn<Search.Search>() .WithServiceBase() .WithServiceSelf() .LifestyleTransient() .AllowMultipleMatches() When we then call _container.ResolveAll<FacetSearch>(new { searchInput = input, searchResults });

I'm out of ideas how to configure right Windsor container for use with repositories in Windows app. I have generic repository implementation Repository, where T is entity type, it has a dependency IDatacontextProvider, which provides datacontext for it: public class Repository<T> : IRepository<T> where T : class { protected DataContext DataContext; public Repository(IDataContextProvider dataContextProvider) { DataContext = dataContextProvider.DataContext; } .... } And for simple things everything works ok with following configuration: container.Register( Component.For<IDataContextProvider>()