Isolate VSSDK version in NuGet.Clients solution build #3890

Closed
alpaix opened this Issue Nov 7, 2016 · 0 comments

Comments

Projects
None yet
1 participant
@alpaix

alpaix commented Nov 7, 2016

Details about Problem

As VSSDK recently introduced breaking changes in VSIX manifest format the NuGet.Clients solution stopped building in VS15 RC.

Proposed Solution

Consider isolate the build by switching to VSSDK official package Microsoft.VSSDK.BuildTools.

@alpaix alpaix added this to the 4.0 RC2 milestone Nov 7, 2016

@alpaix alpaix self-assigned this Nov 7, 2016

alpaix added a commit to alpaix/NuGet.Client that referenced this issue Nov 9, 2016

Isolate VSSDK version in project build files
Resolves NuGet/Home#3890.

In NuGet client project VSSDK is used to generate .pkgdef and .vsix
artifacts via injecting VSSDK specific tasks and targets.
By default path to VSSDK target and prop files is resolved to a current VS
installation. This practice produces inconsistent build output when built
on different dev machines with SxS willow instances and outdated VS
preview installations. Worse, in recent revision VSSDK introduced breaking
changes in manifest format that disrupted build on local dev boxes.

This change provides isolated VSSDK build environment by switching to
`Microsoft.VSSDK.BuildTools` package supplying all necessary target and
prop files.

@alpaix alpaix referenced this issue in NuGet/NuGet.Client Nov 9, 2016

Merged

Isolate VSSDK version in project build files #1015

alpaix added a commit to NuGet/NuGet.Client that referenced this issue Nov 9, 2016

Isolate VSSDK version in project build files
Resolves NuGet/Home#3890.

In NuGet client project VSSDK is used to generate .pkgdef and .vsix
artifacts via injecting VSSDK specific tasks and targets.
By default path to VSSDK target and prop files is resolved to a current VS
installation. This practice produces inconsistent build output when built
on different dev machines with SxS willow instances and outdated VS
preview installations. Worse, in recent revision VSSDK introduced breaking
changes in manifest format that disrupted build on local dev boxes.

This change provides isolated VSSDK build environment by switching to
`Microsoft.VSSDK.BuildTools` package supplying all necessary target and
prop files.

alpaix added a commit to alpaix/NuGet.Client that referenced this issue Nov 9, 2016

Isolated VSSDK version in project build files
Resolves NuGet/Home#3890.

In NuGet client project VSSDK is used to generate .pkgdef and .vsix
artifacts via injecting VSSDK specific tasks and targets.
By default path to VSSDK target and prop files is resolved to a current VS
installation. This practice produces inconsistent build output when built
on different dev machines with SxS willow instances and outdated VS
preview installations. Worse, in a recent revision VSSDK introduced breaking
changes in manifest format that disrupted build on local dev boxes.

This change provides isolated VSSDK build environment by switching to
`Microsoft.VSSDK.BuildTools` package supplying all necessary target and
prop files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment