Which offers better performance?

From: JustMe (temilson_at_sasktel.net)
Date: 09/08/04 

Date: 8 Sep 2004 13:14:46 -0700

Hi:

This may be a dumb question. I have a custom textbox class. During
the lifetime of my application, this special textbox is created MANY
times.

I currently compile the class with the rest of my application code.

Would I find a performance increase/decrease by compiling my Textbox
class to a separate dll and then referencing this in my main
application?

Any suggestions/pointers would be greatly appeciated.

--Terry

Relevant Pages

  • Re: Accessing members of a user control from the aspx page.
    ... you've made the textbox a static instance. ... > i have a fix for it but it might be moot if it doesn't compile correctly ... >> ascx page ... >>>> on the control and drop the control on the page. ...
    (microsoft.public.dotnet.framework.aspnet.webcontrols)
  • Re: letting users make controls
    ... I would half to say yes, Since .net can compile at runtime then this is ... It will be a pain in the ass as far as useability, a lot of training will be ... > 7 charters long with a label in the label ... And the default value in the textbox will be 100 ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Which offers better performance?
    ... But, as always, performance gains/losses should be something that's tested ... know I have to and I have the metrics showing where my changes will actually ... I have a custom textbox class. ... > I currently compile the class with the rest of my application code. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: SALFORD ERROR
    ... I decided to try the Salford Fortran and it appears to have just what I am ... a call to TextBox() ... I think they'd sell more if they toned it down a bit, ... compile is enough to turn most people off. ...
    (comp.lang.fortran)
  • Re: there is an invalid use of the . (dot) or ! operator or invalid parentheses
    ... >>txtOrderSubTotal is a textbox on the form. ... >Compile the project does it compile OK? ... Why do you feel that this line is at fault? ... But if I set the controlsource to =Forms! ...
    (microsoft.public.access.formscoding)