Reputation: 1698
I am writing generic modules for multiple programs - for example, a series of parsing functions or array handling routines. I would like multiple programs to access this so that if any updates are made to the generic module, the changes are shared across all projects. I am using VB.NET, but this is not a VB question, it's more for the studio.
Here's the scenario:
I copied the generic routines into their own folder at the Visual Studio project level.
I then deleted the modules out of the project and could only figure to load them back into the project was using the ADD > Existing module and I pointed to the modules in the generic folder:
However, even though I point to the generic folder when I added the modules, they are copied into the current project's folder and when looking at properties, it shows they are in the local project:
My question is: other than using the Add Existing function, is there any other way to have VB use modules in a different folder?
I'm fairly new to Visual Studio (Used VB6 IDE for ages). I have explored through VS as much as I can and even searched the Internets (LOL) but I can't even come up with good search terms for something like this.
I also understand this may the wrong place for this and apologize in advance - if it's in the wrong place please let me know where I should post it.
Perhaps sharing modules across multiple modules may not be the best way to do things - just in my mind, I can test a module with a test program, then put it into the "real" program and if I want to add enhancements to the module, I can go back to my test program (plus of course share with other modules). I also know this is not OOP so don't flame me please. If you have other constructive ideas, I would be very glad to hear it. By the way, after being on Stack Overflow for a couple of years, this is my FIRST question ever.
Upvotes: 0
Views: 659
Reputation: 887415
In the Add Existing Item dialog, click the down arrow next to Add, then click Add as Link.
Upvotes: 2