Search Results

Search found 3 results on 1 pages for 'arootbeer'.

Page 1/1 | 1 

• Multiple Windows Desktop areas for Full-Screen applications

  - by arootbeer

  Is it possible to run multiple instances of Windows Explorer within a single user session, or configure multiple desktops that are portions of a screen? I don't know the best way to describe what I want to achieve, but here's a picture of what I've got: I've got a 4 monitor setup, 3 portrait and one landscape, and I am normally running a number of RDP sessions, outlook, chrome, a development environment or two, so on and so forth. Most of these applications support full-screen views which mostly or completely hide the window borders, but on the Windows Desktop they take up a full monitor to do so. What I want to do is have 7 "desktops", "regions", call them what you will, each of which is, for the purposes of applications running in it, a "full screen" environment: I'm not tied to Windows Explorer for this, in case it helps - a different window manager that will support this functionality would be a perfectly acceptable answer.

  Read the article

• How can I Setup overloaded method invocations in Moq?

  - by arootbeer

  I'm trying to mock a mapping interface IMapper: public interface IMapper<TFoo, TBar> { TBar Map(TFoo foo); TFoo Map(TBar bar); } In my test, I'm setting the mock mapper up to expect an invocation of each (around an NHibernate update operation): //... _mapperMock.Setup(m => m.Map(fooMock.Object)).Returns(barMock.Object); _mapperMock.Setup(m => m.Map(barMock.Object)).Returns(fooMock.Object); //... However, when the second Map invocation is made, the mapper mock throws because it is only expecting a single invocation. Watching the mapper mock during setup at runtime, I can look see the Map(TFoo foo) overload get registered, and then see it get replaced when the Map(TBar bar) overload is set up. Is this a problem with the way Moq handles setup, or is there a different syntax I need to use in this case?

  Read the article

• Castle Windsor - Resolving a generic implementation to a base type

  - by arootbeer

  I'm trying to use Windsor as a factory to provide specification implementations based on subtypes of XAbstractBase (an abstract message base class in my case). I have code like the following: public abstract class XAbstractBase { } public class YImplementation : XAbstractBase { } public class ZImplementation : XAbstractBase { } public interface ISpecification<T> where T : XAbstractBase { bool PredicateLogic(); } public class DefaultSpecificationImplementation : ISpecification<XAbstractBase> { public bool PredicateLogic() { return true; } } public class SpecificSpecificationImplementation : ISpecification<YImplementation> { public bool PredicateLogic() { /*do real work*/ } } My component registration code looks like this: container.Register( AllTypes.FromAssembly(Assembly.GetExecutingAssembly()) .BasedOn(typeof(ISpecification<>)) .WithService.FirstInterface() ) This works fine when I try to resolve ISpecification<YImplementation>; it correctly resolves SpecificSpecificationImplementation. However, when I try to resolve ISpecification<ZImplementation> Windsor throws an exception: "No component for supporting the service ISpecification'1[ZImplementation, AssemblyInfo...] was found" Does Windsor support resolving generic implementations down to base classes if no more specific implementation is registered?

  Read the article

1