It is time for the perennial “try-out-linux” experience, and this year I decided to not waste the effort on a crappy machine, but to try it out in a virtual environment on my more up to date laptop.
I gave it a chance, but my patience wore out. Vista is no more on my laptop, back to XP pro, but the trip was bumpy and filled with alot of pinched foreheads.
How to get AJAX functionality out of your ASP.NET web pages, without the javascript bloat of the ScriptManager / Ajax.NET.
Although I have been guilty of such in the past, I have to come to the point where I will avoid creating a UI client for a business process if it is at all possible.
Could their ever be a more flame-worthy title? Yet, what makes Sharepoint the new Notes is not only what is does well, but also what it does not do well.
The warning prompt; the last ditch effort to make a user aware of an action they are about to take. Yet over the years we, as developers, have thrown up so many warnings, cautions, and advisories, that users really do not take notice. So how do you secure an application button from inadvertent clicking? Make them work for it.
A recent need at work was to find a way for assist users in data entry tasks so as to help eliminate common data entry mistakes (transposition, wrong data, etc..). Although copying and pasting was the first thought, we eventually decided to use drag and drop technology.
His vector graphics Javascript library is one of the easiest to work with and now Walter has surpassed himself with the easiest Tooltip / Help bubble javascript library.
Database triggers are a great thing, and using them to create an audit trail is pretty simple. Yet when you want to pass some custom values to the triggers, like user name when you are using a single DB login for your application, things get tricky.
ASP.NET has a nice Impersonation feature that allows server-based web applications to use alternate credentials to perform network activities. Unfortunately, it does not extend into Windows “thick” clients; until now.