How are project dependencies handled in MSVC workspaces? Is it an automatic procedure or does the user have to set them up manually?
Sorry I 'm asking, but I 've never used MSVC (not even seen it ;) ) and any help would be appreciated.
Is there a kind soul that could enlighten me?
For what I know, you select which projects depend on which other by using a dialog box. These dependencies are successively stored into a solution file.
Is there a kind soul that could enlighten me?I've attached the GUI how it is implemented in VC6 and VC.NET (2003). I hope this helps.
Thanks Michael :)
If what you say is true, it would be *too* easy ;)
Microsoft Visual Studio Solution File, Format Version 8.00
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "DXUT", "DXUT_2003.vcproj", "{E0CF097B-F22D-465B-A884-D89E55BD7ECD}"
ProjectSection(ProjectDependencies) = postProject
EndProjectSection
EndProject
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "TESTDEP", "..\TESTDEP\TESTDEP.vcproj", "{DD91AD42-5DD3-4DF0-9DCB-1B6256118C8F}"
ProjectSection(ProjectDependencies) = postProject
{E0CF097B-F22D-465B-A884-D89E55BD7ECD} = {E0CF097B-F22D-465B-A884-D89E55BD7ECD}
EndProjectSection
EndProject
Global
GlobalSection(SolutionConfiguration) = preSolution
Debug = Debug
Release = Release
EndGlobalSection
GlobalSection(ProjectConfiguration) = postSolution
{E0CF097B-F22D-465B-A884-D89E55BD7ECD}.Debug.ActiveCfg = Debug|Win32
{E0CF097B-F22D-465B-A884-D89E55BD7ECD}.Debug.Build.0 = Debug|Win32
{E0CF097B-F22D-465B-A884-D89E55BD7ECD}.Release.ActiveCfg = Release|Win32
{E0CF097B-F22D-465B-A884-D89E55BD7ECD}.Release.Build.0 = Release|Win32
{DD91AD42-5DD3-4DF0-9DCB-1B6256118C8F}.Debug.ActiveCfg = Debug|Win32
{DD91AD42-5DD3-4DF0-9DCB-1B6256118C8F}.Debug.Build.0 = Debug|Win32
{DD91AD42-5DD3-4DF0-9DCB-1B6256118C8F}.Release.ActiveCfg = Release|Win32
{DD91AD42-5DD3-4DF0-9DCB-1B6256118C8F}.Release.Build.0 = Release|Win32
EndGlobalSection
GlobalSection(ExtensibilityGlobals) = postSolution
EndGlobalSection
GlobalSection(ExtensibilityAddIns) = postSolution
EndGlobalSection
EndGlobal
Microsoft Developer Studio Workspace File, Format Version 6.00
# WARNING: DO NOT EDIT OR DELETE THIS WORKSPACE FILE!
###############################################################################
Project: "ProjAnotherLib"=.\ProjAnotherLib\ProjAnotherLib.dsp - Package Owner=<4>
Package=<5>
{{{
}}}
Package=<4>
{{{
Begin Project Dependency
Project_Dep_Name ProjDynLib
End Project Dependency
}}}
###############################################################################
Project: "ProjDynLib"=.\ProjDynLib\ProjDynLib.dsp - Package Owner=<4>
Package=<5>
{{{
}}}
Package=<4>
{{{
}}}
###############################################################################
Project: "ProjLib"=.\ProjLib\ProjLib.dsp - Package Owner=<4>
Package=<5>
{{{
}}}
Package=<4>
{{{
}}}
###############################################################################
Project: "ProjTest"=.\ProjTest.dsp - Package Owner=<4>
Package=<5>
{{{
}}}
Package=<4>
{{{
Begin Project Dependency
Project_Dep_Name ProjDynLib
End Project Dependency
Begin Project Dependency
Project_Dep_Name ProjLib
End Project Dependency
}}}
###############################################################################
Global:
Package=<5>
{{{
}}}
Package=<3>
{{{
}}}
###############################################################################
I want to add that MSVC 2005 Compiler is the same as MSVC 2003 regarding this, only changesThe structure of the solution file also change with a new Format Version :wink:. From .NET 2002 (Format Version 7.00) to .NET 2005 (Format Version 9.00) through .NET (Format Version 8.00) small changes are detectable in the solution file structure (e.g., the preSolution in the Global section).
Microsoft Visual Studio Solution File, Format Version 8.00
to
Microsoft Visual Studio Solution File, Format Version 9.00
I said "regarding this" because the structure do change (very small changes though), but the projects dependency part is exactly the same between Version 7.00 to 9.00.Ok :).
I wonder how we get support for MSVC 2005 if the main developer refuses to install it :?I have installed it, and I can only understand anybody who refuses to do so. This is the first IDE that took me half an hour to find where to change the system include paths and the first IDE which seems to have no template for a plain normal Win32 GUI application... you can do every crap with this IDE - just not build a plain normal Win32 GUI application from a template.
I have installed it, and I can only understand anybody who refuses to do so.
This is the first IDE that took me half an hour to find where to change the system include paths and the first IDE which seems to have no template for a plain normal Win32 GUI application... you can do every crap with this IDE - just not build a plain normal Win32 GUI application from a template.
If you wish to create native Win32 programs, you will need to download the Microsoft Windows Platform SDK separately and install it. Like all the current versions of Microsoft software, it requires Windows 2000, XP, 2003, Vista (or their x64 versions). Note that unlike the commercial Visual Studio Professional 2005, it does not have 64-bit support, MFC, ATL, Win32 resource editor, macro assembler, source code control integration, etc.
Project dependencies inside workspaces implemented (rev.1499).Yiannis, this rocks again!!!
Well, it is quite obvious that you need the platform SDK - but even if you have it, you cannot build a plain normal Win32 app.
Ok, you can... but you have to start with a console app and change the project's type and do everything by hand. This cannot seriously be the way... :lol:
Project dependencies inside workspaces implemented (rev.1499).
supercool, but I just rebuilded, and I don't seem to find the menu entries for it.
When I close CB then (time to go home ..) it will say the workspace has changed and so on ...I do have my workspace under version control and I see no problem. I would like to store the project dependencies in it to have another user using it. If the workspace file is saved then normally (in my case) only the date changes. A (good :)) version control system will detect that and not commit. If the project dependencies have changed then I normally want to provide these changes to the other users as well.