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!
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!