Import vb class from different directory into current solution

[blisspikle]

Is there any way to use the "imports" keyword for your current
solution to use code (classes) that were used in a different solution
in a different directory without compiling them to a dll? I would
like to just link to the .vb files or the solution, and be able to use
those classes in my current solution. I would like vb to compile all
the code into one exe.

 

[Tom Shelton]

Is there any way to use the "imports" keyword for your current
solution to use code (classes) that were used in a different solution
in a different directory without compiling them to a dll? I would
like to just link to the .vb files or the solution, and be able to use
those classes in my current solution. I would like vb to compile all
the code into one exe.

As long as they are vb.net code:

1) Project -> Add Existing Item

2) Browse to and select the source file. At this point, you can do
one of two things...
You can just take the default Add or you can drop down the little
arrow, and select link. If you select add, the file is copied to your
current project directory. If you select link, then the file stays in
it's original location.

 

[blisspikle]

As long as they are vb.net code:

1) Project -> Add Existing Item

2) Browse to and select the source file. At this point, you can do
one of two things...
You can just take the default Add or you can drop down the little
arrow, and select link. If you select add, the file is copied to your
current project directory. If you select link, then the file stays in
it's original location.

Thanks, that got the file in there. I had a little trouble because
when I tried adding a link they were the same name.

If they are the same name are there any options to use it as a link in
the present project, but not have to change the name on the one that
you are adding?