|
web
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Merging two VB.NET projectsWorking 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" <danth***@cox.net> wrote in message Please remove m.p.vb.general.discussion from the cross-post as this hasnews:1161907979.170048.278740@h48g2000cwc.googlegroups.com > Working w/ someone in my company. We've both developed a project in > VB.NET, nothing to do with VB 6 or earlier "Daniel Manes" <danth***@cox.net> wrote in message Please do not crosspost between .NET and non-.NET groups. The *.vb.* groups news:1161907979.170048.278740@h48g2000cwc.googlegroups.com... > We've both developed a project in VB.NET are for VB6 and ealier. The *.dotnet.* groups are for .NET. Daniel Manes wrote:
Show quoteHide quote > Working w/ someone in my company. We've both developed a project in I normally would create a solution with all the projects under it.> 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 -- Tom Shelton 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 Show quoteHide quote "Daniel Manes" <danth***@cox.net> schreef in bericht news:1161907979.170048.278740@h48g2000cwc.googlegroups.com... > 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 > Cor Ligthert [MVP] wrote:
> In addidition to Tom be aware that one of those is a Form project (Exe) (as Thanks to everyone who answered...Looks like the two projects in one> that is the fact) and the others are Dynamic Link Libraries (DLL), you can > set that from any project in the project properties. 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 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 Show quoteHide quote "Daniel Manes" <danth***@cox.net> schreef in bericht news:1161974600.128194.53380@i3g2000cwc.googlegroups.com... > Cor Ligthert [MVP] wrote: > >> 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. > > 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 > 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 Show quoteHide quote "Daniel Manes" <danth***@cox.net> schreef in bericht news:1161974600.128194.53380@i3g2000cwc.googlegroups.com... > Cor Ligthert [MVP] wrote: > >> 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. > > 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 > Dan,
I would suggest you to create a single solution with two separate projects! Daniel Manes wrote: Show quoteHide quote > 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 Dan,
I would suggest you to create a single solution with two separate projects! Daniel Manes wrote: Show quoteHide quote > 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 > Dan, Well, as long as we're going to keep discussing> I would suggest you to create a single solution with two separate > projects! > ..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. "mayayana" <mayaXXyan***@mindXXspring.com> wrote in message That's not .NET nomenclature; this existed in VS 6.0. We VB6 folks never saw news:Wyp0h.559$zf.221@newsread3.news.pas.earthlink.net... > 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! 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 interesting. I never noticed the MS usage> > 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! > > 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." > 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" "mayayana" <mayaXXyan***@mindXXspring.com> wrote in message Ah, you're looking at a C++ project, I guess. ASP (InterDev) projects used news:u0q0h.13714$Lv3.12692@newsread1.news.pas.earthlink.net... > That's interesting. I never noticed the MS usage > of "solution" before .Net. I don't see "solutions" in > VS6 - just projects and workspaces. the "solution" terminology. mayayana wrote:
Show quoteHide quote > > VB6 had the concept of a Project Group which allowed you load several> > > 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! > > > > 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 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" 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. mayayana wrote:
> Well, as long as we're going to keep discussing Sorry to all the VB6 people for cross-posting my .NET question to your> .Net to no purpose in a VB group.... 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 Maybe that's what Microsoft means when they claim to be "innovative" :)> be a solution before it's solved a problem... > even before it's been written! -Dan 
Other interesting topics
|
|||||||||||||||||||||||
