I have a small project, and I want to have 2 compiled versions of this project:
- which targets the .NET 2.0 platform
- which targets the .NET 3.5 platform
Everything is going well; I included my project in continuous integration (using CC.NET), and I created 2 CC.NET projects. One project for each target structure.
I will not go into details (irrelevant), but my solution is targeting the .NET 3.5 platform in VS.NET.
I have 2 msbuild-tasks:
- one task that builds a solution for .NET 3.5 (simple and simple)
one task that builds a solution for .NET 2.0
In this Task, I invoke MSBuild, and I indicate that TargetFrameworkVersion should be v2.0. I also define some additional building conditions (so that the specific .NET3.5 code is not built into the target of the .NET2.0 build).
So far so good. Everything is working fine. Now the problem is this:
My solution has several dependencies (links to third-party assemblies). In VS.NET, I set 'copy local' to true for these dependencies. When CC.NET creates my version of the .NET3.5 assembly, the third-party dependencies are actually copied to my output directory.
However, when CC.NET creates my version of .NET2.0 for assembly, the dependencies are not copied to my output directory. (Then this leads to the failure of my unit tests).
:
msbuild, .NET2.0 ?
, , - script. , .