Drazen Dotlic

My feedback

  1. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Drazen Dotlic commented  · 

    There is no need for this.
    What you need to do is let ServiceStack's adapter be used only by ServiceStack itself and you should use full power of Autofac yourself. ServiceStack uses a custom build of Funq as IOC/DI library whose API is in no way (it doesn't even try) as feature rich as Autofac's. Forcing the two APIs to align would be akin to fitting a round peg in a square hole.

    This does mean that you should:
    1. Modularize your app
    2. Make sure all dependencies are registered before your service starts running - IOW, don't resolve "manually" (it's a bad practice anyway)

    We've had great success with this kind of approach and run things in production for 2+ years like this just fine.

  2. 38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    Drazen Dotlic supported this idea  · 
  3. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Drazen Dotlic commented  · 

    More details in this issue here: https://github.com/ServiceStack/Issues/issues/96

    Drazen Dotlic shared this idea  · 

Feedback and Knowledge Base