J
John Saunders
The good news is that, in recent weeks, we seem to be getting a lot more
questions from developers new to ASP.NET.
The bad news is that, in recent weeks, we seem to be getting a lot more
questions from developers new to ASP.NET.
There seem to be some basics which aren't being communicated to these new
developers before they're being required to write ASP.NET code. Although we
can help them individually (and I've tried to do that recently), perhaps it
would be better to help them collectively, with a FAQ?
I'm especially concerned that there may be new developers we're losing
because they _don't_ ask questions at all and just give up, and some we're
going to lose because they're not going to ask questions until they're in
way over their heads and have developed mistaken ideas about how ASP.NET
works.
I don't have enough "copious spare time" to write such a thing, though I'd
be glad to contribute to a list of questions which should be answered in a
FAQ. My question for today is, "Can I do <some client-side thing> from the
server?", and the corollary, "Can I do <some server-side thing> from the
client?". These are questions which should be answered by someone with more
patience than I have. I'm too likely to answer, "usually not, because the
client is not the server". A better answer might include discussion of
stateless client-server programming. ;-)
questions from developers new to ASP.NET.
The bad news is that, in recent weeks, we seem to be getting a lot more
questions from developers new to ASP.NET.
There seem to be some basics which aren't being communicated to these new
developers before they're being required to write ASP.NET code. Although we
can help them individually (and I've tried to do that recently), perhaps it
would be better to help them collectively, with a FAQ?
I'm especially concerned that there may be new developers we're losing
because they _don't_ ask questions at all and just give up, and some we're
going to lose because they're not going to ask questions until they're in
way over their heads and have developed mistaken ideas about how ASP.NET
works.
I don't have enough "copious spare time" to write such a thing, though I'd
be glad to contribute to a list of questions which should be answered in a
FAQ. My question for today is, "Can I do <some client-side thing> from the
server?", and the corollary, "Can I do <some server-side thing> from the
client?". These are questions which should be answered by someone with more
patience than I have. I'm too likely to answer, "usually not, because the
client is not the server". A better answer might include discussion of
stateless client-server programming. ;-)