We, The ASP.NET team, are very interested in ensuring that the “top customer pain-points” within ASP.NET are considered or acted upon in every new release.
I’d like to ensure that you have the opportunity to connect with the product team so that you can submit your top “pain points” and so that we get a consolidated (and ideally prioritized) list of such items from a number of avenues.
As most of my readers are avid ASP.NET Developers, I’d love to hear from you.
Here are some areas to consider:
- Problems understanding, as the feature area is way too complex or cumbersome
- Problems in coding, such as way to complex, or not possible, or involves way too much code”
- Plain bugs in the product with either no or complex workarounds
In addition, if there are requests for new scenarios or feature sets, please pass them my way too.
When you provide a response or idea, please give us some idea of the number of times you have encountered the issue, that might help us set priority for our investigation.
For example, as we are in late stages for FX4, we might be able to accommodate only a few remaining requests, so a sense of priority on the issue would be required.
We cannot guarantee that every issue will be resolved, but this represents one way that the team can be more connected with our users, and for you to help shape what gets added in new releases.
Please send your comments, issues or any other ideas by using this link (Email Joe) and please include‘ASP.NET Customer pain-point: .. ‘ in the top of the message
Many Thanks!
Joe & The ASP.NET Team
The e-mail link has a few problems – it does not have a subject field and it does not give any feedback if the e-mail was sent successfully. So, just to be sure, here’s a copy.ASP.NET Customer pain-point: Control LoadViewStateRecursive and SaveViewStateRecursive uses different Control collections. Saving uses _occasionalFields.Controls, but loading uses this.Controls.This should be a simple fix… The problem surfaces when you override the Controls property to return the ControlCollection from another control. My work-around was to check the call stack which resulted in this:var caller = new System.Diagnostics.StackFrame(1, false).GetMethod();if (string.Equals(caller.Name, "LoadChildViewStateByIndex", StringComparison.Ordinal))return base.Controls;elsereturn this.InnerPanel.Controls;
My biggest "pain-point" or "wish list fix" involves the XHTMLConformance tag. It doesn’t operate anything at all like you would think it should. Currently it only mandates that the code produced by the server controls render as Legacy (not recommended), XHTML 1.0 Transitional, or XHTML 1.0 Strict). While this is nice, you’d expect the XHTMLConformance tag to actually go through your project and change the doctype statement on those pages (masterpages etc) within the project where a doctype statement exists to new doctype specified by the XHTMLConformance tag. Also though, it would be nice if this tag also account for XHTML 1.1 STRICT, and HTML 5 doctypes. THis way, based on the associated doctype the server controls could render the appropriate (X)HTML based on the doctype which is what it should be doing.My second wishlist item is that the ASP.NET team would release a portable application version of the Visual Web Developer Exress platform for people like me who carry a "portable web development studio" on a USB Flash Drive. This way we could use any computer to demo their sites to them without having to copy them up to test / or production servers that may or may not be available from the meeting location.Well, that’s my "two-cents" worth.
Arguably Gridview is the most used asp.net control. What I would like to see in the next release would be a Gridview that has spreadsheet like structure. You know how you can expand or contract the width of excel cells. Nothing is more style-whacker than having a column with large content and the grid has to be out of proportionally lengthy to accommodate it. I hope you get my point. And oh! While I am at it [Gridview], would in it be nice to have nested Gridview out of the box? Instead of writing all these ugly code on ItemDataBound event, all you need would be to supply a foreign key and table name or sp to the main grid, and then the child Gridview would be automatically bounded.Thanks a lot
Sorry but I don’t see subject section in that link?
Glad to hear that. Performance is what I care most, the current ajax framework is too large, and cost more resource then others such as JQuery.Hope there will be some improvement.
Hi, the biggest problem i had was with 2 way databinding (not working within updatepanels and a couple other scenarios) which i posted a bug up on a the connect website and have been notified this will be fixed in the v4
.Here’s the other issues i have:1. DataSource control parameters are case sensitive for the SelectCountMethod but not for SelectMethod, InsertMethod, UpdateMethod of DeleteMethod.2. <%# Bind("Name") %> doesn’t allow you to specify a different name for the update parameter and the property, also you cannot wrap utility functions around Bind.To overcome this in the past i have had to use Eval and then add the parameter on the OnUpdating event of the DataSource control.3. As a follow up to the above you cannot set default values when using two way databinding, without having to go into the code behind.That’s all i can come up with for now.As you can see databinding is my biggest headache and if these were resolved life would be so much easier.
Hi Joe, hope you and your family are all well. I saw Stephen Walthers’ talks at Mix 09, and he made one very important statement: websites should be built like desktop applications. This means that when any button or control is activated, the response is immediate.What would be great is that having future builds of .Net and Ajax as one – combine both development into one framework. If all controls of .Net (gridview e.t.c.) could be integrated into Ajax, then this would definitely be the future of web development. Thanks!
Hi Joe,I saw Stephen Walthers’ talks at Mix 09 and he made one very important statement: Websites should be build like desktops. This means that when any event is fired, the response should be immediate, just like the user experience when using any desktop application. What would be great is that instead of having two seperate builds of .Net and Ajax, they should collaborate to produce a fusion of the two. So to have all the great controls of the .Net framework (gridview e.t.c.) be able to have immediate response when on the website by having Ajax incorporated into them. All the best!