.net - Why so many individual System.Web.* DLLs? -
I'm thinking about ways to redo a significantly expanded class / utility library, and one thing I think That's what I want to do to isolate any high-level accessibility utility that introduces new dependencies. I read some of the previous questions here, and what I especially saw was a comment about how Microsoft is in DLL Uses names Yes. The given example is System.Web
- it is in the base frame, but there is also a System.Web.dll
that adds more functionality to the namespace if you wish.
I have too many other systems Web. * DLL is available, and I was wondering if there is any reason that they will not be added to the same DLL. Could it be that they have their own individual dependencies and Microsoft (like me) wanted to separate assemblies with those lines? Or is it for easy maintenance? Something else completely?
Reason 1. Dll are not different because there are different versions of the framework.
System.Web version 2.0 under
system. Web. Abestation, system. Web. Dynamic data, system Web. Dynamic Data. Design, etc. . .
If you system. Web 1 DL and then all users will have to change .NET 3.5. The framework, IIS still uses 2.0.
Comments
Post a Comment