Hi,
I have a number of sites, all asp which share code running in IIS5 Windows 200 srvr. Maintaining this code is becoming a chore as I have to reflect the changes in all sites that use it, upload etc. Im converting this common code to a VB Dll so only one change will be needed.
Im looking for guidelines. Currently I have one dll with a number of classes, eg database selects in one class, functions in another, etc. Is it wise to do this, or should I seperate each class into its own dll and have one class reference a class in another dll. Also, does size (kb) matter with the dll on the web server as many sites=many users=many instances of the dll.
Thanks, Simon
I have a number of sites, all asp which share code running in IIS5 Windows 200 srvr. Maintaining this code is becoming a chore as I have to reflect the changes in all sites that use it, upload etc. Im converting this common code to a VB Dll so only one change will be needed.
Im looking for guidelines. Currently I have one dll with a number of classes, eg database selects in one class, functions in another, etc. Is it wise to do this, or should I seperate each class into its own dll and have one class reference a class in another dll. Also, does size (kb) matter with the dll on the web server as many sites=many users=many instances of the dll.
Thanks, Simon