Liverpool Users of .Net Google Group

Re: [luodn] Re: MVC

2009-09-15T11:11:06Z

It's a "switch user" for admin.

It's working ok now, like so...

using (Html.BeginForm("ChangeClient" , "Admin", FormMethod.Post, new { id
= "ChangeUser" }))

{ %>

<%= Html.DropDownList("clientid", (from c in new
DataDataContext().Clients orderby c.Name select new SelectListItem() {

Re: [luodn] Re: MVC

2009-09-15T10:57:09Z

Ahh, session state, another ASP.NET legacy! It doesn't translate well
to MVC. Current page can be determined by your url, or current action.
Might be worth looking at filters if you need something to be run
before every single action. Create a BaseController and define your
filters in there.

Are you doing a search form that will be on every single page of a site?

Re: [luodn] Re: MVC

2009-09-15T10:43:41Z

but how do I get the current page into tempdata in the first place? I'd
have to put it in there during the execution of every single action,
plus it's session scoped so if the user has more than one page open
they'll get redirected back to the last action executed rather than the
one they just came from.

Re: [luodn] Re: MVC

2009-09-15T10:39:25Z

This chap just uses some lambdas and model mapping with
RedirectToAction to pass his state around actions:

[link]

Kind of depends how you've set up your models really.

2009/9/15 Thom Shannon <t...@glow-internet.com>:

Re: [luodn] Re: MVC

2009-09-15T10:38:48Z

Personally I think the hidden input is more of a hack, tempdata is
provided by the framework to temporarily hold stuff whilst you perform
some logic, this sounds ideal for what you want to do. That way you
know there's no tampering.

Just my thoughts anyway.

--
Regards,

Michael James

Re: [luodn] Re: MVC

2009-09-15T10:34:56Z

I've used TempData a couple of times, it looks like a bit of a hack
really. I think I'll go with the hidden input option.

--
* Want to become an expert Digital Marketer?
[link] <[link]>

Glow New Media
t: 0151 707 9770
m: 07730 987 574

Re: [luodn] Re: MVC

2009-09-15T10:30:00Z

[link]

TempData is your friend!

2009/9/15 Derek Fowler <dezfow...@gmail.com>:

Re: [luodn] Re: MVC

2009-09-15T10:26:08Z

I dunno what the "right" answer is but could your controller inherit from a
common controller that provides the action method for your partial? You'd
have to record what the current action was so you could redirect back to
that action when your partial one is done.

2009/9/15 Thom Shannon <t...@glow-internet.com>

Re: MVC

2009-09-15T10:20:21Z

Another question for you all.
I have a partial view and I want it to perform a simple action on the
server, but return the user to the current page. Do I have to post to
another action and then get it to redirect back to that page? What's the
right way to do that redirect while preserving all the parameters etc?

Re: [luodn] Re: MVC

2009-09-14T20:13:43Z

You could also have two forms with different Ajax.ActionLinks
specified and then return a partial with search results from each one.
To be honest I found the transition to mvc a bit painful, but like
others have said well worth it once you can break out of the old
webforms mindset and once you add jquery into the mix it's really fun.

Re: [luodn] Re: MVC

2009-09-14T11:26:01Z

Bit far for me to come now - suppose I could get a flight.

2009/9/14 Thom Shannon <t...@glow-internet.com>

--
Derek Fowler
m. +44 (0) 7966 512 369
e. dezfow...@gmail.com

Re: MVC

2009-09-14T11:13:46Z

Thanks guys! That was all helpful.
We should get the luodn meetings going again :)

Re: [luodn] MVC

2009-09-14T10:37:10Z

Hi Thom.
Used it quite a bit.

I find it better to separate everything out, sometimes a controller action
for each form is best. In your case I would have a Search action on the the
controller that you are using. Then on your view (web page) have two forms
with the same method and action but with different hidden variables

Re: [luodn] MVC

2009-09-14T10:35:35Z

Actually, re-reading your post it seems like your problem is how to
re-render the page after a post. Simple answer is don't, maintain
state in the client and do an AJAX post with some jQuery to an action
which returns just the search results and inserts them into the DOM.
The Postback and ViewState models don't really transfer to MVC.

Re: [luodn] MVC

2009-09-14T10:35:15Z

You can have actions with the same name but you need to use the AcceptVerb
attribute and specify which verbs each is responsible for i.e. have one of
them handle the POST from the search form. Easiest thing is probably to just
have the action method expect two strings from the form and check
IsNullOrEmpty on each and decide what to do based on that.