No, as far as i know all DLLs are loaded at the same time...
The only thing is that ASP.NET will have less to compile....
I would recomend to precompile application and then use "merge". So you will
get only single DLL as a result...
Meaning that the whole application will be compiled into 1 dll (plus an
other external dlls application using).
here are 2 lines I am using to precompile and merge my application
C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspn et_compiler -v
/RetailStore/ -p C:\Inetpub\wwwroot\RetailStore -f C:\tmp\RetailStore
C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspn et_merge.exe
C:\tmp\RetailStore -o RetailStore
I produces one RetailStore.dll (parameter -o) in virtual root /RetailStore/
(parameter -v) from source located in parameter -p and it puts the result
into parameter -f (C:\tmp\RetailStore)
George.
"my cats, Gag and yak" <mr********@comcast.netwrote in message
news:6-******************************@comcast.com...
>I am trying to decrease the time a asp 3.5 website loads.
Does changing the business layer to separate DLLs ( so they are only in
memory when needed ) improve load time, or, . . . any help is greatly
appreciated.
Thank you