Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 631719
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T19:59:48+00:00 2026-05-13T19:59:48+00:00

We are using renderaction provided by MVC futures. We’ve noticed that HttpExceptions in child

  • 0

We are using renderaction provided by MVC futures.
We’ve noticed that HttpExceptions in child action methods are not propagated to the parent action. Even though a fragment has failed, we still see
the parent request resulting in a 200, and this throws our error handling for a toss. Any suggestions on how this could be handled?

Thanks,

Varun

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T19:59:49+00:00Added an answer on May 13, 2026 at 7:59 pm

    http://forums.asp.net/t/1529174.aspx

    Don’t use RenderAction() from Futures. Use the one provided in-box instead. RenderAction() was officially moved into the framework as of MVC 2 Beta, and this problem should have been fixed.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have parent view that also renders sub-controller action using RenderAction() (that returns a
Using ASP.NET MVC 2 and and Html.RenderAction in my masterpage implemented as below throws
I'm not quite sure I understand what Html.RenderAction() does. I've just noticed one weird
As we all know RenderAction() is either part of: Asp.net MVC 1 Futures or
I have an MVC controller that has a single constructor, I am using structure
I have a Masterpage (site.master) that calls a View using RenderAction. At the moment
In my MVC3 app I am using some child actions (RenderAction()) to populate 2
In my layout I'm using RenderAction that will output a simple email form which
I'm rendering a common Log-In form using Html.RenderAction, on every page of my site.
I'm using ASP.NET MVC and I have a model class which represents a peice

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.