I have a performance question with regards to packaging assemblies and
referencing them.
First lets say you have created the following assemblies:
Company.Framewo rk.dll
Company.Framewo rk.IO.dll
Company.Framewo rk.Xml.dll
Company.Framewo rk.Data.dll
Company.Framewo rk.Web.dll
Company.Framewo rk.Web.UI.dll
Company.Framewo rk.Web.UI.HtmlC ontrols.dll
Company.Framewo rk.Web.UI.WebCo ntrols.dll
Now, when you go to use one, more, or all of them in an application would it
have been better performance wise to have them all in ONE assembly that could
just be called Company.Framewo rk.dll ?
Other than logical packaging, is there a performance hit for referencing
more than one assembly as opposed to having it all in one "god" assembly?
Please explain or show me an article somewhere.
--
-Demetri
referencing them.
First lets say you have created the following assemblies:
Company.Framewo rk.dll
Company.Framewo rk.IO.dll
Company.Framewo rk.Xml.dll
Company.Framewo rk.Data.dll
Company.Framewo rk.Web.dll
Company.Framewo rk.Web.UI.dll
Company.Framewo rk.Web.UI.HtmlC ontrols.dll
Company.Framewo rk.Web.UI.WebCo ntrols.dll
Now, when you go to use one, more, or all of them in an application would it
have been better performance wise to have them all in ONE assembly that could
just be called Company.Framewo rk.dll ?
Other than logical packaging, is there a performance hit for referencing
more than one assembly as opposed to having it all in one "god" assembly?
Please explain or show me an article somewhere.
--
-Demetri