I have 2 projects in my solution, and they need to share some modules, classes etc.

If I use Project/Add Existing Item from Project2 and reference a file in Project1, I get a [u]copy</u> of the file put into my Project2 folder.

How can I share the modules etc, so I have one version for both projects?

(BTW, I'm using VB Express)

I don't think you're supposed to do that. I can't find a reasonable way to do it.

I think what you're supposed to do is make a class library project and put the code you want to share in it. Then add a reference to the compiled DLL to your other project and use the classes in the DLL.

I think this is the same solution to the "Help! Its all gone horribly wrong!" topic.

Rod
[email protected]
Author of "Visual Basic 2005 Programmer's Reference"
http://www.vb-helper.com/vb_prog_ref.htm

Sign up for the free VB Helper Newsletters at http://www.vb-helper.com/newsletter.html

It seems there is a rather hidden dropdown on the Project/Add existing item/Add button to Add as link. This gives adds a reference to the item rather than the item itself and works fine...

ms-help://MS.VSExpressCC.v80/MS.NETFramework.v20.en/dv_vssoln/html/15f4cfb7-78ab-457f-9f14-099a25a6a2d3.htm

Ah ha! You learn something new every day.

You should still keep the DLL solution in mind. That's the "right" way to do this. Linking will probably work for you but it could cause trouble if you had multiple developers working on all of the projects. If you use a DLL, you have more control over when changes to the DLL break compatibility so you know that you need to rebuild other projects.

Rod
[email protected]
Author of "Visual Basic 2005 Programmer's Reference"
http://www.vb-helper.com/vb_prog_ref.htm

Sign up for the free VB Helper Newsletters at http://www.vb-helper.com/newsletter.html

It's actually quite clever... if you have two copies of VB2005 running with projects that share a file, if you change the file in one, the other detects the change and offers to re-load it.