-
Notifications
You must be signed in to change notification settings - Fork 67
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
Q: How to publish transformed file to multiple directories #298
Comments
I have tried these couple of scenarios, neither of which seems to be copying, packaging, etc, as expected. <None Include="build\BumpAssemblyVersions.props">
<TransformOnBuild>true</TransformOnBuild>
<Pack>true</Pack>
<PackagePath>build;buildMultiTargeting</PackagePath>
<PackageCopyToOutput>true</PackageCopyToOutput>
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
</None>
<None Update="build\BumpAssemblyVersions.Debug.props">
<IsTransformFile>true</IsTransformFile>
<DependentUpon>BumpAssemblyVersions.props</DependentUpon>
</None>
<None Update="build\BumpAssemblyVersions.Release.props">
<IsTransformFile>true</IsTransformFile>
<DependentUpon>BumpAssemblyVersions.props</DependentUpon>
</None> Also: <None Include="build\BumpAssemblyVersions.props">
<TransformOnBuild>true</TransformOnBuild>
</None>
<None Update="build\BumpAssemblyVersions.Debug.props">
<IsTransformFile>true</IsTransformFile>
<DependentUpon>BumpAssemblyVersions.props</DependentUpon>
<Pack>true</Pack>
<PackagePath>build;buildMultiTargeting</PackagePath>
<PackageCopyToOutput>true</PackageCopyToOutput>
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
</None>
<None Update="build\BumpAssemblyVersions.Release.props">
<IsTransformFile>true</IsTransformFile>
<DependentUpon>BumpAssemblyVersions.props</DependentUpon>
<Pack>true</Pack>
<PackagePath>build;buildMultiTargeting</PackagePath>
<PackageCopyToOutput>true</PackageCopyToOutput>
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
</None> Either of these seem like the most plausible way of adding packaging support. Under a prior attempt, I think I had gone the route with a Is there another, better way? Or is the Thanks... |
Bottom line there, would be nice to publish to multiple locations, as well as relaying additional packaging aspects, but I do not think it is possible coordinating |
To be fair, have not tried yet, I have the following scenario.
I have a source
.props
or.targets
, or anything that needs transforming, and I want to deploy the result to eitherbuild
orbuildMultiTargeting
directories.Starting from a base source, for instance:
The naive outlook on the objectives says I factor the package, copy, other similar aspects, to the transform update. Again, have not tested that hypothesis. Was wondering is that was accurate.
It is key that I need to include some of these outputs in the resulting package as well.
The text was updated successfully, but these errors were encountered: