MabBObiaBrorm
New Member
I am building an application that the front end will be replicated on the same server:<BR><BR>mydomain.com/co1<BR>mydomain.com/co2<BR>mydomain.com/co3<BR>mydomain.com/co4<BR>mydomain.com/co5<BR><BR>Done this way for additional security issues. I have common business methods that I want to share among all of these sites, and be able to update one central location. Am I going down the right path by creating a vb class project, writing my code in classname.vb with all of my methods and properties then adding a reference to the release version of the dll?<BR><BR>I have also considered creating a vb component in the same project. Can someone give me some insight to which is the better route, if there is any difference?<BR><BR>Thx.You really should buy "Applied Microsoft .NET Framework Programming":<BR><BR> http://www.amazon.com/exec/obidos/ASIN/0735614229/forestlakewebser/<BR><BR>Specifically, read Chapter 3 titled "Shared Assemblies".<BR><BR>In short, if you are developing components that will be shared among many projects, then you should consider creating strongly named assemblies. There are many benefits (as I understand it) to creating strongly named assemblies when you need to share them, including versioning issues and the ability to deploy your assembly to the global assembly cache.<BR><BR>But seriously, you don't want to hear this information from a NEWBIE like me 
buy the book and read it for yourself.
buy the book and read it for yourself.