Sanity check for code reuse

Results 1 to 2 of 2

Thread: Sanity check for code reuse

  1. #1
    Join Date
    Dec 1969

    Default Sanity check for code reuse

    I am building an application that the front end will be replicated on the same server:<BR><BR><BR><BR><BR><BR><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.

  2. #2
    Join Date
    Dec 1969

    Default Don't know about sanity but...

    You really should buy "Applied Microsoft .NET Framework Programming":<BR><BR><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&#039;t want to hear this information from a NEWBIE like me :-) buy the book and read it for yourself.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts