rainersigwald on vsix-depend-on-nuget
VSIX dependency on NuGet.BuildT… Disambiguate branch name (compare)
livarcocc on vs16.0
Bump version to disambiguate wi… Merge pull request #4119 from r… (compare)
livarcocc on livarcocc-patch-1
livarcocc on vs16.0
Adding a vs16.0 trigger Updating to a more general trig… Merge pull request #4118 from M… (compare)
.projitems, but it seems that doesn't work for imported
.targets. It gives me
Microsoft.Common.CurrentVersionas source instead of the
.projitemsfile. So I'm guessing
Noneitems are redefined somehow in there.
dotnet publish -o=xxx
<TargetFrameworks>netstandard1.0;netstandard2.0;net20</TargetFrameworks>. Is there a better event we can monitor in order to only bump once prior to the build(s) for each platform?
Rebuildattempt effectively wipes those assets at the moments when any CG would take place.
PrivateAssets PackageReference(s) internally for our CG.
netstandard2.0, but not when the multitarget happens.
<Target Name="..." BeforeTargets="DispatchToInnerBuilds" Condition="'$(TargetFrameworks)' != ''" />or
<Target Name="..." BeforeTargets="BeforeBuild" Condition="'$(TargetFrameworks)' == ''">, respectively.
buildfrom among the
<IncludeAssets>runtime; native; contentfiles; analyzers</IncludeAssets>for the time being. Although, I think possibly this is a bug in
msbuilditself and should be addressed.
buildassets, I get
warning MSB4011, the bump does happen as expected, but only because I included the targets myself. Something about this condition is prohibiting the bump from ever happening,
<ImportGroup Condition=" '$(TargetFramework)' == 'netstandard1.0' AND '$(ExcludeRestorePackageImports)' != 'true' "><Import Project="$(NuGetPackageRoot)\bumpassemblyversions\1.3.1\build\BumpAssemblyVersions.targets" Condition="Exists('$(NuGetPackageRoot)\bumpassemblyversions\1.3.1\build\BumpAssemblyVersions.targets')" /></ImportGroup>.
ExcludeRestorePackageImportsmust be blocking, because there are similar cases for the other targets, i.e.
<ImportGroup Condition=" '$(TargetFramework)' == 'netstandard1.3' AND '$(ExcludeRestorePackageImports)' != 'true' " />.
MSBUILD : error MSB1021: Cannot create an instance of the logger. Could not load the file '/home/dylan/Desktop/git/mono-git/msbuild/.packages/microsoft.dotnet.arcade.sdk/1.0.0-dev.18424.13/tools/net472/Microsoft.DotNet.Arcade.Sdk.dll'
ITaskItemspecs, that I want to filter. I only want the most recent ones by the
Includename to be included. Is it possible to filter based on that from a .targets perspective? Or would it just be simpler just to have received them into my custom target as an
ITaskItem, do whatever transformations to internal descriptors, and just do the filtering there? That is to say, I know I can do the latter, but I wondered if the former was possible and I could do it in the target.
<MySpec Include="Test" PropertyA="true" PropertyB="123" ... />, then possibly something like
<MySpec Update="Test" PropertyC="false" />. Question is, if we update the spec, does that undo the
Bproperties and leave only the
Cproperty? Or does it preserve the
Bproperties? To be clear, we want to see only the
Cproperty when we update in this manner. We could do that, from a targets perspective, possibly. If necessary, we can do the filtering internally to the custom target implementation, however.
<Exec />dotnet CLI tool, which, apparently, does not adequately identify its package references during build time. So the next best thing we want to try is delivering all the required bits in one single package.
binfolder prior to code generation tasking taking place.