Last post Dec 20, 2006 10:26 AM by Gogatorz
Feb 03, 2006 01:39 PM|Motley|LINK
Render the listitem attributes, PLEASE.
SelectAllButton property that takes a link/image/command button, and attaches an onclick event that client-side selects all the checkboxes, and then if autopostback is turned on (And only if) for the checkboxlist, perform a postback.
No formview/detailsview/datarepeater needed. Build form, drop singlesqldatasource control on page, and singlesqldatasource will PUSH/PULL values from controls (via "parameters") depending if you call it's .select, .insert, or .update, or .delete method.
Why can't we inherit from say sqlparameters? I hate the new overloads you provide. I want parametername,sqldbtype,optionally value,optionally direction. I rarely need scale, precision, nullability, sourcecolumn, and the rest of the stuff. yes, I can inherit
from dbparameters, but why should I have to?
Better localization support. I want a culture dropdown (en-US,en-GB,es-MX, etc) that makes the designer pull in the values from the local resource files, then allows me to edit the page, and when I save, put the values back into the resource file - Except
if the value you are going to save, would be the same thing if you didn't specify it at all, and used the culture-invariant's value instead, or default culture's value, then don't save that value.
Fix the dropdownlist bugs with selectedvalue.
Definately add more ajax-enabled controls by default -- dropdownlist is obviously a big one.
Not really asp.net related, more .net related. I would really like to see something like java's prototype functionality in .NET. Where I could redefine functionality for a class, rather than having to declare a new class inheriting that class (If it can
be inherited from). Like say string. I want all my strings to have a IsNullOrEmpty boolean property -- Not a shared method. Sure, I can go create a new class, give it a name, and always use that class. Except when a co-worker wants to use his special string
class with IsReallyLong boolean property as well. Now we have to make a 3rd class that is both his class and my class, and he can't use his property in my projects, nor can I use mine in his, unless we go through and change all the declarations. Actually,
the whole IsNullOrEmpty type code where it's shared taking a parameter of it's type just really irks me quite frankly. Why should I have to string.IsNullOrEmpty(mystring)? What's wrong with mystring.IsNullOrEmpty?
I'd like to see a viewstate provider with a few different standard ones. Session, database, cache storage, form (What it is today), adaptive (use form unless the client's bandwidth is bad, then use an alternative). Yes, I can write my own, and I have,
but why should I have to? I'm working on a website for whatever, it has nothing to do with "viewstate" or where the server puts and get it. .NET should handle the details, and let me work on my business logic.
The membership provider really should have a "LockoutPeriod" attribute that resets the locked out user(s) after the specified time, defaulting to an hour or something.
SqlDataSource could really use a membershipparameter type to pass in the logged in user's username? userparameter type would be nice as soon as the user object contains the providerkey/userid.
Maybe I'm missing something, but I seem to be missing the user provider. How does one programmatically create users, get a users providerkey without looking at the raw tables? membership will give me the user's providerkey, but what if I'm using windows
authentication? I don't have a valid membership object, hence no way to retrieve the providerkey, but the default profile provider knows how to get it (I assume by looking directly at the base tables/views).
Include the default providers source code so we can "fix" these annoying limitations without having to recreate them from scratch.
Oh, and revisit your profile providers, the out of the box one is pretty limiting in that you can't get at the profiles from T-SQL very easily (I did write a T-SQL function to de-blobify them, so we can search, slowly atleast), and the 2 replacements you
have require that every programmer that uses the profiles now has to be able to modify database objects (Either table structures, or stored procedures), and I don't WANT our jr programmers doing this stuff.
Jun 13, 2006 02:12 AM|Motley|LINK
I'll add these to my wishlist:
Multiview - decent control, except when switching from design to source view, it always places the cursor at the top of the multiview.. UGH! I really hate that, makes working with the darn thing a pain.
VS 2005 IDE quirks - Strange things just "happen" if you leave VS 2005 running too long. Sometimes all of a sudden I can't edit properties any more. Well, you can, but then they immediately reset themselves again. A real pain. Closing Visual Studio and
reopening it fixes the problem until it happens again.
Controls not displaying properly. This is usually directly after I've moved a bunch of controls from one container to another. Closing the page and reopening it usually fixes it. If not, closing Visual Studio and reopening it fixes it.
Control.FindControl - Sure would be nice if it'd do it recursively. I'd be able to stop putting putting my SuperFindControl function in my projects. Here ya go:
basectrl = Page
I'm sure it has some quirks. I seem to recall an issue about finding if the control actually has child controls, but it works for my purposes for now. I think basectrl.hasControls isn't always accurate, sometimes it's false when it
really does have child controls or something, so I switched to basectrl.controls.count instead.
Atlas -- What a waste. It seems to work, as long as the moons align in the right places. That or you keep your pages very simple. The places I've really wanted to use Atlas so far, atlas just can't do, which is a shame. For example, a detailsview in
which one of the fields has a VERY large dropdownlist, and I needed to update a few other controls in the detailsview. I finally got atlas to work within the template control, but it was quirky, and I finally hit a roadblock that I just didn't have the time
to fix, and dropped atlas completely from the project.
CascadingDropdown - Great control, if your dropdowns have 3 items in it. Try it with 30,000, and watch IE lock up for a minute. I'll deal with the 1/10th of a second screen flicker and 2 second response over 60 second response and locking up IE, followed
by 15 seconds of the dropdowns flickering.
The atlas extenders sometimes work, sometimes they don't. Sometimes they won't even show up in the extended controls. Sometimes they will, but when you try to fill out the properties, they don't "save", and reset to nothing.
Modal popup? Not exactly modal, dropdowns still work, update/cancel/edit buttons on grids, detailviews, etc still fire. Maybe call it, kinda-sorta modal popup?
UpdatePanel? I actually had a use for this, and it worked, until I had to put some validators in the detailsview contained in the UpdatePanel, then everything broke. Remove validator, works, put validator back, broke. Ok, remove UpdatePanel, project works.
Simple solution, too bad.
Double databinding a control often leads to an unstable form (Like binding a dropdown's selectedvalue in a grid, and pulling the list from a second datasource). You get a nice error message about databinding only being available within a container or something
Databinding order - Really, if a parameter of a datasource of one control depends on the value of another control, please databind the dependant control first. As it sits, you have to programmatically databind everything yourself to get stuff to work right,
and dropdownlists HATE being databound twice (Selectedvalue not found, when it's right there, UGH).
Things like a DropDownField, DateField, etc really should be part of the base framework. Yes, I've written my own classes, and they work quite well (Although, I still can't figure out how to get the gridview/detailview let me create a field of that type,
if you create it manually in the aspx page, it'll happily let me set all the properties, although it calls it a "Field" instead of "DropDownField", etc).
ASP.NET Configuration button - Please stop writing the xml ns attribute in the web.config file, which breaks intellisense.
Get rid of the __ASP is not CLS-compliant warning message when you compile. I didn't create that, VS did.
Random profile object not compiling correctly the first time, leading to numerous error messages about file ASJDAJJKJD.aspx not found. Recompile a second time gets rid of the error messages (Odd, compiling twice fixes a problem with no changes?)
Having a table set to width=100% causes the IDE to always have a horizontal scroll bar, odd I could have sworn I said 100% not 110% [:O] In addition, when working on any page like that, clicking on the 3/4ths left part of the vertical scroll bar will actually
select part of the page, and if you then try to "drag" the scroll bar, you set the width of the object. I can't count the number of times I, and team mates have changed controls widths because of this bug. Really annoying. Best workaround, is to put the
whole page in a div that has a width of 95%, then on page load, set it to 100%, so the IDE sees it as 95% and circumvents all it's issues.
Localize controls that you can't actually select to type stuff into. I hate this control. HATE it. Really, it should have some kind of text placeholder like the label control, so you can actually put text in there without flipping to source view. Or better
yet, why can't you highlight text, right click and "Localize" to put the text in a localization control?
Trying to access another control that's within the same row of a gridview/detailsview is too difficult. Many of my controls depend on a value from another control within the row, and it's always a pain. It'd be nice to use a cascadingdropdown control,
but you can't. Atlas won't let you in a template. And you could, can't databind it. /sigh
So far, "Atlas" seems nice, until you use it. I haven't been able to use it in any page in any project successfully yet. Hopefully that will change with the next release.
Oh, and why can't the webservice results be cached? /sigh. Apparently XMLHTTP doesn't support etags or caching. Shame. Thought perhaps this might be a nice way to have clients cache large datasets, but nope.
Jun 13, 2006 02:34 AM|Motley|LINK
Oh, and since this is my wishlist... I wish you asp.net guys would walk over to the IE team and beat them silly.
Receiving a compressed page (gzip/deflate) should not have any bearing on caching. I've found no way to override IE's braindead caching of gzip/deflated pages, forcing me to abandon gzip/deflate for IE based browsers.
Not traversing the IP stack for localhost. Still can't get fiddler to run well with IE 7 and VS's built in web server. /sigh.
No acid test compliance. Really guys. Fix this, so I can stop listening to all the open source whiners already.
I do miss some of the more complex css selector support (First/last item within an item, etc). Would be nice for headers/footers without having to code a specific class id.
Ok, back to .NET wishlists.
Skin files. They suck. How do I skin the button images in a gridview commandfield, or a detailsview? Oh, you can't? Nice.
Insert support in the gridview, right out of the box. Really. Please?
Once you are done with that, add "All rows editable at once" for the gridview, thanks.
Jun 23, 2006 07:57 PM|Connect|LINK
Dec 20, 2006 10:26 AM|Gogatorz|LINK