About project dependencies...

[mandrav]

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?

[takeshimiya]

A picture says more than 1000 words.

Microsoft Visual C++ 2005 Express is available as a free download at the MSDN site until November 7, 2006.
http://msdn.microsoft.com/vstudio/express/visualc/download/

[mandrav]

Thanks but if I wanted to install it, I would 've done so by now

[takeshimiya]

I wonder how we get support for MSVC 2005 if the main developer refuses to install it :?

Well, I myself say that because I don't want to install it :lol:

[Michael]

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?

May be this msdn link could be useful.

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.

Michael

[mandrav]

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.

Thanks Michael
If what you say is true, it would be *too* easy
Let me check out the link you gave me...

[MortenMacFly]

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.

Morten.

Edit: :oops: :oops: :oops: Sorry, I've just seen that this is in german language. :oops: :oops: :oops:
To clarify:
MSVC6:
- "Projektabhängikeiten" = "Project dependencies"
- "Zu bearbeitendes Projekt markieren" = "Select project to modify"
- "Abhängig von folgenden Projekten" = "Depends on the following projects"
NET2003 (in addition):
- "Abhängigkeiten" = "Dependencies"
- "Buildreihenfolge" = "Build order"
- "Projekte in dieser Reihenfolge erstellen" =  "Build projects using the following order:"
- "Verwenden Sie die Registrierkarte..." = "Use the dependencies tab to change the build order."


[attachment deleted by admin]

[Michael]

Thanks Michael
If what you say is true, it would be *too* easy

You are welcome .

Here is an example of solution file which includes project dependencies:

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

The TESTDEP project depend on DXUT project.

Hope this could help a bit.

Michael

[takeshimiya]

And here a MSVC 6 version of a workspace (*.dsw) containing dependencies:

The dependencies are as following:

ProjTest
    depends on ProjDynLib
    depends on ProjLib
ProjAnotherLib
    depends on ProjDynLib

Code

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>
{{{
}}}

###############################################################################

Attached is a MSVC 6 screenshoot.

[attachment deleted by admin]

[takeshimiya]

I want to add that MSVC 2005 Compiler is the same as MSVC 2003 regarding this, only changes
Microsoft Visual Studio Solution File, Format Version 8.00
to
Microsoft Visual Studio Solution File, Format Version 9.00

[Michael]

I want to add that MSVC 2005 Compiler is the same as MSVC 2003 regarding this, only changes
Microsoft Visual Studio Solution File, Format Version 8.00
to
Microsoft Visual Studio Solution File, Format Version 9.00

The 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).

Michael
 

[takeshimiya]

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.

[Michael]

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 .

Michael

[thomas]

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.

[Michael]

I have installed it, and I can only understand anybody who refuses to do so.

The installation of Microsoft Visual C++ 2005 Express was not a part of pleasure, I must admit . But easier ( :roll:) as Visual Studio .NET 2002/2003.

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 also spent sometime searching the template for Win32 GUI application without finding it... :?

Moreover, Microsoft Visual C++ 2005 Express has other limitations:

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.

Michael