Re: My first impressions of ASP.NET
- From: "Patrice" <nobody@xxxxxxxxxxx>
- Date: Fri, 24 Jun 2005 11:29:32 +0200
Inline...
--
"OldProgrammer" <OldProgrammer@xxxxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le
message de news:06C54A9B-D2DD-4018-AA6C-FF817A475E48@xxxxxxxxxxxxxxxx
> Our company built a web site for the US Navy using ASP. This web site is
> extremely important for squadrons to order the aircraft components to save
> the lives of pilots. Without these components, planes don't fly and
soldiers
> die.
>
> Our ASP web site consisted of 2200 pages after it was partially complete.
> We have 4 programmers to maintain these pages. We were looking forward to
> being able to convert the site to .net in order so as to reduce the number
of
> pages and to expedite page processing. However after the deployment of
> several new ASP.Net modules we have found the following issues.
>
> Limited server resources are being utilized so heavily that at times it
will
> take 20 minutes or more to load a simple listing 15 data points.
Normal behavior ? Really strange IMO or is this such an old server ?
>
> The some programmers are relying on the highly toted garbage collector to
> clean up their database objects instead of disposing of them explicitly
> thereby creating large numbers of database connections that use up the
> resources of the database server.
Solved now that they know that. Lack of training prior to switching to
ASP.NET (IMO it's quite well documented).
>
> The literature on deployment extolled the virtues of the "xcopy" means of
> deployment yet none of the objects want to work when deployed in this
fashion
> requiring extensive amount of troubleshooting on the production machines
and
> as well as time spent creating deployment packages.
It works fine for us...
>
> Strange behavior quirks occur in the IDE that are different from machine
to
> machine and even project to project. This means that a lot of expensive
> programming time is being spent learning about and dealing with these
quirks.
Never had this one (though we are only 4 here)
>
> Example. VS creates the inital page of a Web project to be webForm1,
> obviously an unsatisfactory name for a web page. However, when the rename
> function is used to rename the file, it does not rename the public Class
on
> the page behind the file. When this is noted, and handled, the inherits
> statement in the aspx file still needs to be changed. Our programmers
have
> taken to deleting the initial webform and adding a new one with the name
we
> choose from scratch.
Renaming manually also works. A bit annoying but that's not the everyday
task...
>
> Another example, IIS prefers the initial file of a Web app to be named
> "default". However VS will not allow the class of the code behind file to
> have the name "default" so it renames it "_default". This is fine for
the
> first project created like this. But then when I opened a second project
and
> did the same thing, upon running an error reports that it could not load
> type "projectname._default". After changing the name of the class to
> something innocuous like "zeus", and putting a break point in the page
load
> event, Visual studio proceeded to show as open SECOND "default.aspx.vb"
file
> with a Public class named "_default"?!!?
I believe we had this one once... Not sure how we get around...
>
> Another example. A control gets dropped on a form. Then it's moved to
> examine a new layout. When you try to put it back where it was it won't
go.
> The only alternative is to delete the control and start all over.
Try to move it in HTML mode (anyway due to HTML you can't always IMO be
rigourous when placing an HTML element, I tend to do fine layout tuning in
HTML view.
>
> Another example: We wanted to convert one page at a time to use ASP.Net.
> However we found that we opened an ASP.Net project in the folder of the
page
> we wanted to replace, That folder could no longer be seen in interdev.
None
> of the Design Time Controls that were toted so intensively a few years
ago,
> could be accessed from the VS.Net project. So there was no way to repair
> pages that were breaking. When we asked Microsoft for assistance, we were
> informed "We sorry. Visual Interdev is no longer supported. Please
update
> your applications and try again."
We are using VS.NET now for both ASP and ASP.NET applications (or for those
who have a mix of ASP, ASP.NET pages).
>
> While any new product is going to have a learning curve and quirks, we
still
> have 2200 pages to maintain and convert. We don't have a enough
programmer
> resources to spend half each day searching the internet trying to deal
with
> all of these issues that keep cropping up. VS.Net is not making it easy or
> helpful.
Try to ask a question at a time to get help on particular subjects if
possible..
Patrice
.
- References:
- Re: My first impressions of ASP.NET
- From: OldProgrammer
- Re: My first impressions of ASP.NET
- Prev by Date: Re: Can I inherit controls from another class at runtime??
- Next by Date: Re: Highlighting tabs in a TabControl
- Previous by thread: Re: My first impressions of ASP.NET
- Next by thread: Re: My first impressions of ASP.NET
- Index(es):
Relevant Pages
|
