Merging two VB.NET projects

  • Thread starter Thread starter Daniel Manes
  • Start date Start date
D

Daniel Manes

Working w/ someone in my company. We've both developed a project in
VB.NET, and now we want to merge them into a single project/solution so
they can communicate with each other. The communication is fairly
simple stuff (e.g., if user selects a row in a DataGridView in one
form, it selects a corresponding row in the other form).

I pretty much have the class written that will handle all the
communication, but what I'm not sure about is, what's the best way to
merge these babies? Just copy all the vb files and references into a
single project? Or create a single solution with two separate projects?
Or ... ?

Your advice much appreciated,

-Dan
 
Daniel Manes said:
Working w/ someone in my company. We've both developed a project in
VB.NET,
Click to expand...

Please remove m.p.vb.general.discussion from the cross-post as this has
nothing to do with VB 6 or earlier
 
We've both developed a project in VB.NET
Click to expand...

Please do not crosspost between .NET and non-.NET groups. The *.vb.* groups
are for VB6 and ealier. The *.dotnet.* groups are for .NET.
 
Daniel said:
Working w/ someone in my company. We've both developed a project in
VB.NET, and now we want to merge them into a single project/solution so
they can communicate with each other. The communication is fairly
simple stuff (e.g., if user selects a row in a DataGridView in one
form, it selects a corresponding row in the other form).

I pretty much have the class written that will handle all the
communication, but what I'm not sure about is, what's the best way to
merge these babies? Just copy all the vb files and references into a
single project? Or create a single solution with two separate projects?
Or ... ?

Your advice much appreciated,

-Dan
Click to expand...

I normally would create a solution with all the projects under it.
 
Daniel,

In addidition to Tom be aware that one of those is a Form project (Exe) (as
that is the fact) and the others are Dynamic Link Libraries (DLL), you can
set that from any project in the project properties.

I hope this helps,

Cor
 
Dan,
I would suggest you to create a single solution with two separate
projects!
Click to expand...

Well, as long as we're going to keep discussing
..Net to no purpose in a VB group....

Isn't that .Net nomenclature just too zany? :)
Only in the unique world of Microsoft could software
be a solution before it's solved a problem...
even before it's been written!
In any other context the sentence above is
utterly nonsensical.
 
Isn't that .Net nomenclature just too zany? :)
Only in the unique world of Microsoft could software
be a solution before it's solved a problem...
even before it's been written!
Click to expand...

That's not .NET nomenclature; this existed in VS 6.0. We VB6 folks never saw
it, though, because our IDE wasn't integrated into the VS IDE.

Don't blame .NET for things that aren't its "fault."
 
That's not .NET nomenclature; this existed in VS 6.0. We VB6 folks never saw
it, though, because our IDE wasn't integrated into the VS IDE.

Don't blame .NET for things that aren't its "fault."
Click to expand...
That's interesting. I never noticed the MS usage
of "solution" before .Net. I don't see "solutions" in
VS6 - just projects and workspaces. But when I did a
search of MSDN I got an article from *1995* near the
top of the list, named:
"Client/Server Solutions: The Design Process"
 
Cor said:
In addidition to Tom be aware that one of those is a Form project (Exe) (as
that is the fact) and the others are Dynamic Link Libraries (DLL), you can
set that from any project in the project properties.
Click to expand...

Thanks to everyone who answered...Looks like the two projects in one
solution is the way to go. Next question: *How* do I actually do this?

The only thing I can think of is to convert the smaller project into a
Class Library (DLL) then reference it in the larger project. Is that
what you have in mind? If yes, how do I convert a "Windows Application"
project into a "Class Library" project?

Many thanks,

-Dan
 
mayayana said:
Well, as long as we're going to keep discussing
.Net to no purpose in a VB group....
Click to expand...

Sorry to all the VB6 people for cross-posting my .NET question to your
group. I just sent my latest post with
microsoft.public.vb.general.discussion removed, so hopefully you will
be spared any further unwanted stuff (not counting this message :)).
Only in the unique world of Microsoft could software
be a solution before it's solved a problem...
even before it's been written!
Click to expand...

Maybe that's what Microsoft means when they claim to be "innovative" :)

-Dan
 
That's interesting. I never noticed the MS usage
of "solution" before .Net. I don't see "solutions" in
VS6 - just projects and workspaces.
Click to expand...

Ah, you're looking at a C++ project, I guess. ASP (InterDev) projects used
the "solution" terminology.
 
mayayana said:
That's interesting. I never noticed the MS usage
of "solution" before .Net. I don't see "solutions" in
VS6 - just projects and workspaces. But when I did a
search of MSDN I got an article from *1995* near the
top of the list, named:
"Client/Server Solutions: The Design Process"
Click to expand...

VB6 had the concept of a Project Group which allowed you load several
projects at once. When you have a project open, you can select File ->
Add Project. When you saved, you had a .vbg file with information to
load up both projects. Although I don't recall if you could reference
one project from another.
 
Daniel,

Forgive me the word, yes it is Class Libary not Link Library.

For the rest it is the same as I wrote, just in the Project properties, you
see it almost direct.

Cor
 
Daniel,

Maybe you cannot find it. The setting for Class Library is in the solution
exploirer after that you have Added your existing project to the other one
using the File menu, in the solution explorer you can right click on it and
than it is easy to see. (It is a little bit different between the versions
2003 and 2005).

Cor
 
Back
Top