Search

Can no longer Render RadioButtonList without HttpContext by Thejuan

Closed
as Won't Fix Help for as Won't Fix

1
Sign in to vote
0
Sign in to vote
Sign in
 to vote
Type: Bug
ID: 104962
Opened: 5/9/2006 5:19:10 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
RadioButtonList Render method assumes the presence of a HTTPContext.
We have code from 1.1 that generates HTML based on the Rendering of a Control Structure without a HTTPContext.
This code no longer works as a Null Reference Exception is throw when the render method attempts to access this.Context.Request.Browser.Tables

The main problem for us with this is that we can't inherit and override as the EnableLegacyRendering and ControlToRepeat properties are not accesible from a child class
Details (expand)
Product Language
English
Version
Visual Studio 2005
Category
Controls
Operating System
Windows XP Professional
Operating System Language
US English
Steps to Reproduce
Create a new Console Application.
Create a new RadioButtonList and add Items
Attempt to Render the Control by calling control.RenderControl(HtmlWriter)
Actual Results
NullReferenceException
Expected Results
Rendered HTML
File Attachments
1 attachments
Sign in to post a comment.
Posted by Microsoft on 5/10/2006 at 3:18 AM
Thank you for your feedback. We are investigating this issue.

Thank you, Visual Studio Product Team.
Posted by Microsoft on 5/10/2006 at 3:50 AM
Thanks for reporting the issue, we are unable to repro the issue with the steps provided. If you could provide us with a sample project/solution demonstrating the issue and the exact repro steps, we would still like to address the issue.

Thank you,
Nagesh, Visual Studio Product Team
Posted by Thejuan on 5/14/2006 at 5:28 PM
Uploaded Attachment
Posted by Microsoft on 9/16/2006 at 11:51 PM
Thejuan,

Thanks for your feedback on the .NET Framework! S. Somasegar, the Developer Division VP recently wrote in his blog (http://blogs.msdn.com/somasegar/archive/2006/05/18/601354.aspx) on how the next release of the .NET Framework (codename “Orcas”) requires a high degree of backward compatibility and therefore, how we are being very strict about the number and scope of bugs that are fixed and features that are added in the “Red Bits” during Orcas. Unfortunately, this bug falls into the red bits category, and so we are not able to address it in Orcas due to the potential for it to introduce compatibility issues.

We recognize you submitted this bug because of a specific problem you are experiencing with the product. If you submitted this bug because of a blocking problem you’re experiencing and continue to experience, you may want to contact Microsoft Professional Services http://support.microsoft.com. Alternatively you may find additional information by searching or posting to the ASP.NET forums (http://forums.asp.net) . Finally, if you submitted this bug because of a blocking problem you’re experiencing and continue to experience, you may want to also open a support call with Microsoft Professional Services (http://support.microsoft.com/?LN=en-us&scid=gp%3Ben-us%3Bofferprophone&x=8&y=14), which is a better support option when you’re experiencing business impact for your problem and are unable to resolve it in a timely manner on forums or other support channels.

Before starting work on the next full release of the .NET Framework, we will review the Connect data to help us identify and address the top customer reported issues. We’ll broadly review all bugs submitted to date at that time.

Kashif Alam
UI Frameworks Team
© 2010 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement