Re: My first impressions of ASP.NET
- From: "OldProgrammer" <OldProgrammer@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 15 Aug 2005 03:20:01 -0700
The basic thrust was that we have a 2200 page ASP web site in production that
is responsible for the delivery of vital aircraft parts to active duty US
Navy aircraft so that they may continue to fly and provide close air support
to our troops in Iraq and Afghanistan. This site needs to be updated to the
latest technology but VS.net kept placing obstacles in the way with its
inconsistent behavior. so of these kids seem to think it was funny that
peoples lives are dependent upon the proper operation of an application.
Re inconsistent behavior, The other day I was using a class level variable
to preserve state between post-backs as advertised and advocated by Microsoft
only to be informed that the latest information on the subject was advising
against the use of these constructs as they did not perform as advertised. I
was able to confirm this through experimentation and had to rely on an old
ASP trick of storing the variable in an hidden text box. This is not the
kind of product I have come to expect from Microsoft. I have been repeatedly
disappointed while using this environment. I think you must add to your list
ease of use. Unless a product can be consistently developed easily and
quickly, there is going to be increasing amount of hesitation in updating
the massive older applications to use the new technologies. I am sure
everyone remembers the big Y2K fiasco.
"Rob R. Ainscough" wrote:
> Not sure what this is about, guess someone doesn't like classic ASP?? Not
> sure what Afghanistan has to do with this. I've got a lot of programming
> experience and to be honest I'd rather do any other kind of programming that
> is NOT web based.
>
> But whether the language is ASP, VB.NET with ASP.NET, HTML, XHTML,
> JavaScript, VBScript, etc. etc. etc. -- the fundamental problems of
> developing in this nightmare of an environment are:
>
> 1. Stateless
> 2. Security
> 3. Rendering pages
>
> Those issues have not changed, we just have different tools with same set of
> issues as the old tools. Change is needed, what that change will be I'm not
> sure, but the current status of web development is ultimately doomed unless
> we realize those changes soon.
>
> My personal opinion and what can be achieved to some success today is rely
> on .NET framework on client PCs -- since .NET framework is currently
> available across platforms it might be a much better faster and more rebust
> solution. Use basic HTML to retain the pretty graphics and basic linking,
> but the links such for example "Manage Your Account" should just download
> small footprint .NET apps that execute immediately on the client side
> (outside of the browser). This will elminate stateless, and page rendering
> and IF implemented correctly can be much more secure.
>
> Rob.
>
> "OldProgrammer" <OldProgrammer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:F2FCF020-505C-4728-8A30-933EC8594463@xxxxxxxxxxxxxxxx
> >I am sure that the families of the 1769 US service men and women that have
> > died in Iraq and the 500+ that have died in Afghanistan think it is very
> > funny as well.
> >
> > I am sure that you could write in 20 minutes an application in compliance
> > with DoD regulations to replace the existing Web Site which was working
> > wonderfully until ASP.Net came along. Why don't you write the Dept of the
> > Navy and bid on the contract for the CAD/PAD VFS website.
> >
> > "Cor Ligthert" wrote:
> >
> >> > Holy crap!!!!
> >> >
> >> > It's a scary thought that lives are dependent on a Classic ASP app!!!
> >> >
> >> LOL
> >>
> >>
> >>
>
>
>
.
- Prev by Date: Re: Starting up SDK doco from the command line?
- Next by Date: Re: can Classic ASP use the .NET dll ?
- Previous by thread: can Classic ASP use the .NET dll ?
- Next by thread: ClickOnce - database changes
- Index(es):
Relevant Pages
|
