[dba-VB] VB.Net - Using modules in other projects

Gustav Brock Gustav at cactus.dk
Thu Oct 11 11:56:27 CDT 2007


Hi John et al

To add to the confusing, I see no "Link" option anywhere; _if_ the Open button has an dropdown arrow juxtaposed, it offers "Open" or "Open with ..." only. 

/gustav

>>> jwcolby at colbyconsulting.com 11-10-2007 18:48 >>>
Charlotte,

This conversation is like trying to discuss a specific switch on the space
shuttle.  I don't know enough to know what I want to do.  I have modules
that I am developing or have found out there that I want to use in various
projects.  I do not want those modules embedded in each project precisely
because of maintenance issues.  In my terminology that is a library.  ATM
this is really a "library" of classes / modules that will be shared between
projects.

Understand that I do not truly understand "project" and "solution".  A
project is where poor people live and a solution is chemicals mixed in a
liquid.  Alternatively Project and Solution are terms used by much more
advanced .Net programmers used to confuse beginners and establish respective
positions in the programming hierarchy.

Take it from there. 


John W. Colby
Colby Consulting
www.ColbyConsulting.com 
-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com 
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Thursday, October 11, 2007 12:16 PM
To: dba-vb at databaseadvisors.com 
Subject: Re: [dba-VB] VB.Net - Using modules in other projects

But I thought you were trying to add your other project to a solution, not
just a specific class.

Charlotte Foust 

-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com 
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Thursday, October 11, 2007 9:12 AM
To: dba-vb at databaseadvisors.com 
Subject: Re: [dba-VB] VB.Net - Using modules in other projects

Hmmm... If you "add existing" a file Find dialog opens.  At the bottom of
THAT is an ADD button which has a little drop down to the right of it.  If
you drop that down a "LINK option".  If you select "LINK" then it adds the
module as a link instead of importing it directly into the project. 


John W. Colby
Colby Consulting
www.ColbyConsulting.com 
-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Thursday, October 11, 2007 10:58 AM
To: dba-vb at databaseadvisors.com 
Subject: Re: [dba-VB] VB.Net - Using modules in other projects

You're talking about two different things.  Open is a menu item under the
file menu.  That's what Doris was referring to, I think.

Charlotte Foust 

-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com 
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Thursday, October 11, 2007 5:39 AM
To: dba-vb at databaseadvisors.com 
Subject: Re: [dba-VB] VB.Net - Using modules in other projects

Doris,

OK, I finally figured out how to do what you are talking about.  It is
actually the "ADD" button which threw me for awhile, I kept going back and
forth searching diligently for this "OPEN" button.

Anyway, that is handled.  So if I open a linked file, I am opening the
actual source out in the lib and if I edit it, the changes are stored in
that module in that lib?  

This works for me! 


John W. Colby
Colby Consulting
www.ColbyConsulting.com 
-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com 
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Doris Manning
Sent: Tuesday, October 09, 2007 10:51 AM
To: dba-vb at databaseadvisors.com 
Subject: Re: [dba-VB] VB.Net - Using modules in other projects

John,

When you add an existing item to a project and press the OPEN button, you
are actually importing the module from its existing location into the
project location.  

If you click on the small black arrow on the far right of the OPEN button,
you have a "Link file" choice.  Choosing this option adds the module to your
project but keeps it in its existing location.  Any projects that link to it
will instantly inherit the changes but will need to be rebuilt so the
executable picks up the changes.

Doris Manning
Database Administrator
Hargrove Inc.  

-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com 
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Tuesday, October 09, 2007 8:15 AM
To: dba-vb at databaseadvisors.com 
Subject: [dba-VB] VB.Net - Using modules in other projects

I am developing modules that I need to use in various projects.  This
includes things like a status form with specific controls and code to
display status updates from operations, and base classes for making another
class serializable.  Stuff like that.  

I need to know what the process is for making such objects accessible to
other projects such that as I add capabilities and fix bugs, such
enhancements are available to all the other projects that use these things.
IOW, something similar to an MDA in Access.  I know that it is possible, I
just do not understand the mechanics of referencing the common objects.

Could someone give me a detailed "step by step" of how to do it, what to
click, select this menu item, click this etc. from inside of the referencing
project.  Or alternately a web article that discusses this stuff.

TIA,

John W. Colby
Colby Consulting
www.ColbyConsulting.com 




More information about the dba-VB mailing list