I have a problem which seems very similar to the one described in http://markmail.org/message/6rlrzkgyx3pspmnf which is about the singleton actually creating more than a sin
In V3, there is finally a solution for this in the shape of new overloads on Bind, see this related: question.
If you want the singleton to be shared, you need to change your second Bind
to:
kernel.Bind().ToMethod(()=>kernel.Get()).InSingletonScope();
Re circular references and confusion etc. Internally the implicit self-binding will add an implicit binding registration for Service. You should post the exception.
EDIT: Re your comment. If you do it like this:
Func serviceCreator = () => new Service(false);
kernel.Bind().ToMethod(serviceCreator).InSingletonScope();
kernel.Bind().ToMethod(()=>kernel.Get()).InSingletonScope();
Then no implicit Class Self Binding gets generated when IService
gets Resolved - it uses the existing one.
There was another Q here on SO in recent weeks someone was doing this type of thing but was running into an issue with IInitializable - that example would have the correct ordering but the one above makes sense based on my reading of the source and the way in which it generates the implicit class self-bindings.