Enough with the new stuff!

That's a comment I get a lot -- many people are tired of reading of software in Beta (or not even there yet), and only want solutions that help them today!

So, what articles do you need to answer your 2003 woes? How to user HttpHandlers to solve your problems? How to create widgets and foodangles to solve the latest management hullabaloo? How to plug your ASP.NET 1.1 pages into your office glamwhatzit?

As always, I await your ideas. Rather, I desperately need them. I've almost run out of 2003 ideas, and just love playing in the 2005 meadows of lovely smelling flowers and mangos (yes, mangos!).
Print | posted on Monday, May 30, 2005 9:27 AM

Feedback

# re: "Enough with the new stuff!"

left by Anonymous at 5/30/2005 6:01 PM Gravatar
Hey, you know your " are HTMLEncoded in the title, right?

Anyways, I'm in with the "enough" crowd. I still have plenty of problems to solve with 1.1 technology...longhorn hype doesn't do me any good...

Anyways, your Httphandler is a good idea. I've only ever written one (it handles a centralized javascript repository common.axd?type=1&type=2)... but I'm sure I'd use them more if I knew why/what I could do :) (maybe a whole theme on sharing resources (controls/resources/xml/config across multiple apps?)

I've also toyed with doing an article on XmlHttp (specifically using the Ajax.Net wrapper, http://ajax.schwarz-interactive.de/csharpsample/default.aspx) as I greatly believe in the technology.

I've also heard good things about FlexWiki and thought it might be a good best practice example/document.

You can never EVER have too many good server control articles. Too many people shy away from them because of their complexity. Simple (inherit label + 1 property) server controls can really be great..but going from that to composite controls + postback is scary.

One of the most asked about questions in the forums revolve around dynamic controls - how to do them, how to preserve them and their value across postback. Issues with invalid viewstates because of them and so on.

Some of my better articles came from helping out in the newsgroups and seeing the same question asked over and over (and over) again.

Cheers,
Karl

# re: Enough with the new stuff!

left by Anonymous at 5/31/2005 5:00 PM Gravatar
One I have always had trouble with and I can't figure out where my problem really is because all the documentation says it should work is in the Global.asax
protected void Application_Error(Object sender, EventArgs e)

I have gone through MSDN, I have tried on personal PC, I have tried on dev servers I have tried 2003, and 2000. Supposedly when an error occurs anywhere in the application this event is supposed to fire and I should be able to get the error doing Server.GetLastError, however I can not. I have read several articles but something just never works.

# re: Enough with the new stuff!

left by Anonymous at 6/2/2005 6:42 PM Gravatar
We don't have time to think about our current problems, we're too busy prototyping with the Beta. We need to stay ahead of the curve or our jobs will be outsourced.

# re: Enough with the new stuff!

left by kent at 6/3/2005 7:55 AM Gravatar
Hi Sal,

That is an interesting position -- are there still 'issues' with outsourcing? Is it primarily out of country, or 'localsourcing'? What are the issues your employer(s) feel are best served (or is it entirely cost)?
Comments have been closed on this topic.