asp.net dll's question and problem

T

THX-1138

hi,

I am having a trouble at work. We currently have many pages in our site and
we are having trouble with dll's.( we think )

Our site outputs static pages as .aspx pages becasue we have a toolbar that
uses .net so all pages that use the toolbar need to be .aspx. We have many,
many pages on our site ( 10000 or so ) and we are running into
trouble...here is the issue:

When we do development work we need to put a new dll up to the site...when
we do so the site drags as it recompiles..and it can take up to 45 minutes
to finish off...doing changes often results in lags all the time. We have
been in the process of switching the dll to code behinds so that we
wouldn't have to worry about doing changes on the fly but over the weekend
the asp.net temporary internet files folder grew too big and so our sys
admin deleted some files..today when we went to do a change to a page we
got a runtime error even though it tested fine on our local environments
and on our staging server...rebooting the server fixed nothing and we had
to roll back the changes and the problem corrected itself.

Here is the question: how many .aspx pages is too much for a site? SHould
we be using compiled dll's or code behinds? Is there a way to limit this
recompile time on the server?...answers or imput would be appreciated!
 
T

THX-1138

thanks!

are there any ways to avoid the cost of compiling when adding the dll to
the production server that you kow of? I know that in asp.net 2.0 there
are 4 different ways to compile...or is there a way to avoid certain
directories..or are the limitations with the compiled pages?
 
T

THX-1138

ASLO: we work on a live server with people who are always are on it..in
fact its a cluster...we can shut off the site, switch over the dll and
then turn it back on..then we switch the site over and repeat the
process....I guess the problem with the site is most likly due to the
code behinds and the dlls...so when a dll is added all of the pages are
complied at run time...that stays the same no matter what....

...OK.so I add a new page and that page must be recompiled at run time
right..no matter if its referenceing a code behind or a dll. BUT if I
have a new dll that is referenced on many pages do all of the pages
attempt to recompile when I add the new dll?

new page = recompile that file
new dll = recompile all files that reference that dll?
 
T

THX-1138

anyone else comment on this?

ASLO: we work on a live server with people who are always are on it..in
fact its a cluster...we can shut off the site, switch over the dll and
then turn it back on..then we switch the site over and repeat the
process....I guess the problem with the site is most likly due to the
code behinds and the dlls...so when a dll is added all of the pages are
complied at run time...that stays the same no matter what....

..OK.so I add a new page and that page must be recompiled at run time
right..no matter if its referenceing a code behind or a dll. BUT if I
have a new dll that is referenced on many pages do all of the pages
attempt to recompile when I add the new dll?

new page = recompile that file
new dll = recompile all files that reference that dll?
 
S

sandhya

I am very new to this kind of development. I have created a dll, I wanted to use this dll in my .aspx page.

For this I created a bin folder in my website folder and dropped this dll. I also A also added at the top of the aspx page <%@ import Namespace="my namespace" %>

Do I have to do anything other than this. Do I have to add this assembly reference in web.config and does this assembly have to be strongly named.


From http://search.yahoo.com/search?p=Ho...+pages&fr=FP-tab-web-t&toggle=1&cop=&ei=UTF-8

Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top