-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to express project dependencies in Traversal SDK? #504
Comments
Unfortunately, build ordering in a solution file is not a very good best practice. Since the ordering is only respected when building the solution file, this means that when you build projects instead, the build ordering is not guaranteed. The better solution is to declare dependencies directly in each project. This will have your build order respected in Visual Studio and the command-line, whether you're building a solution or a project. Are you able to add <ItemGroup>
<!-- Declare a build dependency on a project but don't actually depend on the assembly at compile time -->
<ProjectReference Include="..\SomeDependency\SomeDependency.csproj" ReferenceOutputAssembly="false" />
</ItemGroup> If you run into target framework incompatibility, you can also set |
In a Visual Studio solution, I can explicitly express dependencies between projects. This is useful when projects implicitly depend on the output of other projects, so that Visual Studio can calculate a compatible build order.
How can I describe project dependencies in a Microsoft.Build.Traversal SDK proj?
The text was updated successfully, but these errors were encountered: