"Standard Practice" advice

ROTRTechTeam · Post by **ROTRTechTeam** » Sat Feb 26, 2005 1:41 pm

I have a project that contains all the files for a desktop app written in VB 6. In that project is a file called "common.cls" that is used to compile a DLL that is used on a website that integrates into the database used by the desktop app. My question is regarding the standard practice for storing this stuff in Vault.

I have a project for the DLL file. Should I be storing the project file to its own folder in Vault? If so, how do I link the common.cls in the main project (for the desktop app) to the folder that contains the project for the DLL file? Would it be better to just store the DLL project file in with the rest of the files with the desktop app?

Thus, I'm looking at two solutions here and am not sure which is best:

$/DesktopApp
|--Desktop app.vbp file
|--All other files associated with Desktop app
|--common.cls
|--DLL file.vbp file

-or-

$/DesktopApp
|--Desktop app.vbp file
|--All other files associated with Desktop app
|--common.cls

$/DLLFile
|--DLL File.vbp file
|--common.cls (somehow linked back to $/DesktopApp folder)

My reason for wanting the link is obvious...I want any changes made to the common.cls file in the desktop app to be reflected in the DLL version of the same file.

Help, I'm new at this stuff.

Thanks!

Mike

ROTRTechTeam · Post by **ROTRTechTeam** » Mon Feb 28, 2005 8:30 am

I ended up sharing the file with the DLL project folder. It seems like the logical thing to do.

Mike

mlippert · Post by **mlippert** » Wed Mar 02, 2005 3:34 pm

Sorry, I saw your post while I was at home, but didn't have the time to respond. I was going to tell you to share the file, which you have already figured out.

Good Luck,
Mike