Re: compiled DLL's and performance

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Kurt Schroeder (KurtSchroeder_at_discussions.microsoft.com)
Date: 02/08/05 

Date: Tue, 8 Feb 2005 10:21:07 -0800

this is a running discussion so i apologize if question s appear more than
once.
and some answers also:
this is a a simple sub declaration to do a sort

    Private Sub SortGrid(ByVal objSender As Object, ByVal objArgs As
DataGridSortCommandEventArgs) Handles dgrdStkHst.SortCommand
        Call bindDataGrid("stkhstX")
    End Sub
It give me this error when run: 'INDEXBUILDDaily._try.Private Sub
SortGrid(objSender As Object, objArgs As
System.Web.UI.WebControls.DataGridSortCommandEventArgs)' is not accessible in
this context because it is 'Private'.
if not declared private it runs and calls a sub that is private. I seems to
me that it should be declared as private, but i really don't know that much
(i mean it).
well, even when it does run the datagrid disappears. I can get ti to sort,
but only if i do it seprate from the data grid using a button control, ...

for now i'd just be happy to figure why it does not want to be declared
private
thanks
kes
"Patrice" wrote:

> So this is not a performance problem ?
>
> Granted there are some plumbing going on behind the scene but it should
> really show up only on rare occasions and is likely needed.
>
> ..NET also creates some code to perform actions done "visually" (is this
> those private subs you are talking about or do yu mean protected variable
> declarations ?). I don't see those "need to be declared as *not* private"
> procedures you are talking about. AFAIK subs handling datagrid events are
> private and you have to write them ???..
>
> You may want to give us a precise sample of the code you are referring to...
>
> ASP.NET 2.0 should still hide a bit more of this plumbing (such as having a
> declaration in the ASPX page doesn' t require to have a programmatic
> declaration in the code behind + DataSource controls are not creating code
> etc...).
>
>
> Patrice
>
> --
>
> "Kurt Schroeder" <KurtSchroeder@discussions.microsoft.com> a écrit dans le
> message de news:F706E4D9-E4AD-47A7-A23D-AC65E5E5EF50@microsoft.com...
> > thanks for responding,
> > I knew that the pages got compiled on the first hit. I was not asking
> about
> > the first time hit or a specific page, but a general question. I hav
> elearned
> > according to another post that there is no difference once the source is
> > compiled first hit by a Browser. The over-head issue was a question about
> the
> > VisualStudio.Net development environment. It seems to add a lot more
> > complacation than apears necessary. for example the class creates Private
> > Subs for the general controls such as buttons and links. That's ok, but it
> > gets me a little confussed because the same automatic subs are not
> generated
> > for some other objects like DataGrid Events. And here the subs need to be
> > declared as not private. I'm guessing there is a ways to do this
> correctly,
> > but i still don't know how.
> >
> > "Patrice" wrote:
> >
> > > Anyway it always execute compile code ? What are you seeing exactly ? Is
> it
> > > the first time you hit a page ? Or each time you access the page ?
> > >
> > > Patrice
> > >
> > > --
> > >
> > > "Kurt Schroeder" <KurtSchroeder@discussions.microsoft.com> a écrit dans
> le
> > > message de news:F46A5F87-D5A9-42F8-9C0B-FD6F07A58B12@microsoft.com...
> > > > does compiling the code behind source using studio give and
> performance
> > > boost?
> > > > this is a rephrase of an a question i posted yesterday. To be honist
> > > VS.net
> > > > is becomming a pain to work with for asp.net. Vb.net and c.net hey, no
> > > > problem, but asp.net it seems to create way too much over head and
> > > > complication. thanks for listening and would appreciate an opinion.
> > > > thanks
> > > > kes
> > >
> > >
> > >
>
>
>

Quantcast