Project Dependencies not saved

[Lukasz Gwozdz[MSFT]]

They are stored in the solution file itself (.sln). Do you save the solution
file on exit? Is it read only? These were the easy guesses, let me know if
you can't figure it out.
They look like this:

Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "WindowsApplication24",
"..\WindowsApplication24\WindowsApplication24.csproj",
"{CFB9637D-7E5F-4BAA-A59F-F20EAA38F8F2}"
ProjectSection(ProjectDependencies) = postProject
>>> {3ABD99B0-02BF-4964-A6C7-57D8C13092F6} =
{3ABD99B0-02BF-4964-A6C7-57D8C13092F6} <<<
EndProjectSection
EndProject

Now that I'm writing this, I remembered there was a similar problem with
Enterprise Template projects. Does your solution contain any? (they look
like nested projects)

--
thanks,
Lukasz

(This posting is provided "AS IS" with no warranties, and confers no
rights.)

"Jacco" <anon...@discussions.microsoft.com> wrote in message
news:C14302D0-0FFB-4EDF...@microsoft.com...
> Hi there,
>
> I'm new to VS.NET (2003) and received a solution from an external company.
It works fine, the problem however is that I need to manually set the
project dependencies in order to change the Build Order every time I open
the solution. I would expect the build order to be saved somewhere (in my
solution.sln file f.i.).
>
> Does anyone has an idea why these settings are not saved ?

[Jacco]

Thanks for the reply. The answer is Yes about the Enterprise Template projects. My Solution consists of a 15 projects grouped using a total of 6 Enterprise Template projects.

What was the issue you are remembering with ETP's?

By the way, I've checked the basis things like Readonly (it was in fact, the entire solution is placed in sourcesafe). I removed the read-only flag from my local solution file and tried it again without success. After making the changes I save all files.

Regards,

Jacco

[Lukasz Gwozdz[MSFT]]

Well, the issue was that project dependencies don't get saved for ETPs.
There are a few workarounds for this problem though:

- Use project to project references instead of user specified dependencies.
If you need to alter the build order, there's a good chance you're doing
that because of dependencies between your projects - some of them need
others' outputs to build. Project references are usually a better way to
express dependencies (Project context menu/Add reference/Projects tab), and
they are persisted for ETPs.
- Modify the solution file manually. Not convenient, but works - if you
enter the dependency data manually VS will be able to read it (although if
you save the solution file in VS later you'll have to do that again). Here's
the sample data:

Microsoft Visual Studio Solution File, Format Version 8.00
...
Global
GlobalSection(SolutionConfiguration) = preSolution
...
EndGlobalSection
GlobalSection(ProjectDependencies) = postSolution
{E0F43498-FBEB-45F8-ABE8-50E23C5E4333}.0 =
{943C9114-7C6A-4795-B59F-1056ED51CFFC}
{E0F43498-FBEB-45F8-ABE8-50E23C5E4333}.1 =
{23C2DF2A-C0BC-4DD3-A75D-1BF826F67B45}
{A2519D63-6B81-4E39-A316-09A71DC00C4C}.0 =
{943C9114-7C6A-4795-B59F-1056ED51CFFC}
{A2519D63-6B81-4E39-A316-09A71DC00C4C}.1 =
{23C2DF2A-C0BC-4DD3-A75D-1BF826F67B45}
{A2519D63-6B81-4E39-A316-09A71DC00C4C}.2 =
{E0F43498-FBEB-45F8-ABE8-50E23C5E4333}
EndGlobalSection
...
EndGlobal

So, if you have an entry like GUID_PROJ1.XX = GUID_PROJ2 it means that the
project with GUID_PROJ1 depends on the project with GUID_PROJ2. If you enter
multiple dependencies for one project, you increment the index - XX. You can
find project guids in the project files - it's the "ProjectGuid" attribute.
Oh, and the ordering of sections doesn't really matter.

- Finally, you can contact PSS (product support) and ask them for a hotfix
for this problem.

Hope that helps, and sorry for the inconvenience.

--
thanks,
Lukasz

(This posting is provided "AS IS" with no warranties, and confers no
rights.)

"Jacco" <anon...@discussions.microsoft.com> wrote in message

news:43E48517-11D6-4F90...@microsoft.com...

[Lukasz Gwozdz[MSFT]]

One more thing, my news reader splits each GUID.XX = GUID entry into two
lines of text, but it should really be just one line for each entry.

--
thanks,
Lukasz

(This posting is provided "AS IS" with no warranties, and confers no
rights.)

"Lukasz Gwozdz[MSFT]" <luk...@online.microsoft.com> wrote in message
news:unl6WeO7...@tk2msftngp13.phx.gbl...

[Jacco]

Thanks Lukasz,

I made the references as you suggested directly in the projects (and not in the solution). This seems to work well.

Thanks for the support!

Jacco.