11 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...

• Jens Hofmann commented  ·  December 21, 2011 2:39 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  ViewContext.Controller is what you are searching for. But you should really think about carefully whether to use it or not.

• MQ commented  ·  September 9, 2011 11:18 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This certainly violates MVC pattern. If you have the urge to get to the controller from the view, you need to double check your design.

• Jeffrey Palermo commented  ·  July 17, 2011 8:09 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  If there is a property of the controller whose value you need in the view, consider sending that value/object to the view explicitly. Allowing the view to "poke around" back at the controller could add to unnecessary coupling. Sending another object to the view instead will preserve the one-way and explicit relationship between controller and view.

• Nikos Baxevanis commented  ·  July 16, 2011 1:39 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  -1! It seems someone missed WinForms :)

• Anonymous commented  ·  July 15, 2011 8:52 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  terrible idea

• Stephen Burns commented  ·  July 15, 2011 7:13 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  No thanks. Views should know nothing about controllers. Review the actual MVC pattern please.

• James Kovacs commented  ·  July 15, 2011 6:25 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  -1! I cannot express how bad an idea this is. One of the main points of MVC is decoupling the view from the controller/model. If you need methods in your view, use HTML helpers.

• jorgebg commented  ·  July 15, 2011 3:33 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is bad for design!

• vinbrown2 commented  ·  July 14, 2011 5:05 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Hmm, I wouldn't do it. What methods would you like to call from the view? Every example I can think of sends up flags saying 'please don't do this'.

• Koen Willemse commented  ·  July 13, 2011 2:21 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Not a good idea.The only code the view should incorperate is some basic looping to generate the correct html, not much more.

• Brendan Enrick commented  ·  March 11, 2010 11:15 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  One of the reasons for MVC's existence is to prevent this type of logic from being in the view.