4 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Anonymous commented  ·  April 11, 2012 3:08 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I agree with Mark, (an easy) decommissioning support is a must.
  any mature IoC container requires that.
  Adding IoC contaneir support with no decommissioning support basically is vanishing the feature itself.
  MVC3 has it and also WebAPI prev6 has it too.. how come with new webapi has been made more difficult?

• AdminDaniel Roth (Admin, ASP.NET Future Feature Feedback) commented  ·  April 3, 2012 11:55 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  We are now tracking this issue in the Issue Tracker on our new CodePlex. Please take a look at the proposed resolution and post any feedback you have as comments:

  http://aspnetwebstack.codeplex.com/workitem/26

• mick delaney commented  ·  March 29, 2012 8:59 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  we need a simple solution, at the moment its very error prone and i dont see any good reason coming from the asp.net team for they're approach....

• Binjie Zhao commented  ·  March 22, 2012 4:47 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I'm with Mark, releasing machanism should be added to make it complete.