Skip to content

Fix Pipeline Error VSSDK1300 in CreateVsix: shorten Dev17 VSIX intermediate paths#6496

Open
DinahK-2SO wants to merge 2 commits into
mainfrom
user/DinahK-2SO/template_fix_pipeline_error_260521
Open

Fix Pipeline Error VSSDK1300 in CreateVsix: shorten Dev17 VSIX intermediate paths#6496
DinahK-2SO wants to merge 2 commits into
mainfrom
user/DinahK-2SO/template_fix_pipeline_error_260521

Conversation

@DinahK-2SO
Copy link
Copy Markdown
Contributor

@DinahK-2SO DinahK-2SO commented May 22, 2026

Fixes the CreateVsix stage failing with VSSDK1300 since #6407.

Root cause: VSSDK's GenerateTemplatesManifest extracts each .vstemplate zip under $(IntermediateOutputPath)$(TargetFramework)\.... Combined with the 32-char project names WindowsAppSDK.{Cpp,Cs}.Extension.Dev17 and deep template asset paths, outputs exceed Windows MAX_PATH (260) on CI agents (repo root C:\__w\1\s\WindowsAppSDK\). The task aborts mid-stream and reports only the first overflowing file.

Fix: Alias the two Dev17 folder segments to Cpp17 / Cs17 in dev/Templates/VSIX/Directory.Build.props. Saves ~27 chars per path; ~26 chars margin to MAX_PATH. Other projects keep $(MSBuildProjectName) for diagnosability.

Long project names plus deep VSSDK extraction paths exceed MAX_PATH on CI.

Alias Cpp17/Cs17 saves ~27 chars per path; restores headroom for new assets.
@DinahK-2SO
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@DinahK-2SO DinahK-2SO changed the title Fix VSSDK1300 in CreateVsix: shorten Dev17 VSIX intermediate paths Fix Pipeline Error VSSDK1300 in CreateVsix: shorten Dev17 VSIX intermediate paths May 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants