Describe the bug
We're hitting an issue with MAX_PATH again for some reason, even after having tested prior fixes if the repo is checked out too deep on a machine:
Severity Code Description Project File Line Suppression State Error DEP1000: Cannot copy file "C:\Users\...\source\uwp\Labs-Windows\labs\StackedNotificationsBehavior\samples\StackedNotificationsBehavior.Samples\StackedNotificationsBehaviorCustomSample.xaml.cs" to layout "C:\Users\...\source\uwp\Labs-Windows\platforms\CommunityToolkit.Labs.WinAppSdk\bin\x86\Debug\net6.0-windows10.0.19041.0\AppX\SourceAssets/StackedNotificationsBehavior\samples\StackedNotificationsBehavior.Samples\StackedNotificationsBehaviorCustomSample.xaml.cs.dat". DirectoryNotFoundException - Could not find a part of the path 'C:\Users\...\source\uwp\Labs-Windows\platforms\CommunityToolkit.Labs.WinAppSdk\bin\x86\Debug\net6.0-windows10.0.19041.0\AppX\SourceAssets/StackedNotificationsBehavior\samples\StackedNotificationsBehavior.Samples\StackedNotificationsBehaviorCustomSample.xaml.cs.dat'. [0x80070003] CommunityToolkit.Labs.WinAppSdk
(Incidentally, this is also related to CommunityToolkit/Tooling-Windows-Submodule#18, #88, #37 and fixing not needing to copy the assets for Uno.)
Looking at our setup, we duplicate the experiment name in a lot of folders:

- For instance in the samples folder we're already in the
ProjectTemplate\samples folder, so we should have our subfolders be:
- Content
- Uwp
- Wasm
- WinAppSdk
For tests we could do similar:
- Shared (or maybe Cases?)
- Uwp
- WinAppSdk
- Alternatively, I like even better just the idea of splitting out the runner projects entirely:
- project template
- src
- samples
- docs/pages just go directly here now
- tests
- test pages/cases go directly here now
- heads (if only we could auto-generate these all on solution opening...)
- Uwp
- Wasm
- WinAppSdk
- Tests.Uwp
- Tests.WinAppSdk
Not only does this remove a whole directory layer from our tree, it also makes it immediately clear where everything goes in an experiment and everything that doesn't need to be touched by a contributor and only needed to run the projects is in a single place.
That also makes it easier for us to migrate experiments when we make future infrastructure changes as we should be able to theoretically just wipe and re-create the heads directory of each experiment and not have to reach into so many directories as we would now.
Steps to reproduce
Clone repo through VS to the standard source folder under users off main...
Build, then try and deploy...
Expected behavior
Should be able to run.
Screenshots
No response
Code Platform
Windows Build Number
Other Windows Build number
No response
App minimum and target SDK version
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
No response
Help us help you
Yes, but only if others can assist.
Describe the bug
We're hitting an issue with MAX_PATH again for some reason, even after having tested prior fixes if the repo is checked out too deep on a machine:
(Incidentally, this is also related to CommunityToolkit/Tooling-Windows-Submodule#18, #88, #37 and fixing not needing to copy the assets for Uno.)
Looking at our setup, we duplicate the experiment name in a lot of folders:
ProjectTemplate\samplesfolder, so we should have our subfolders be:For tests we could do similar:
Not only does this remove a whole directory layer from our tree, it also makes it immediately clear where everything goes in an experiment and everything that doesn't need to be touched by a contributor and only needed to run the projects is in a single place.
That also makes it easier for us to migrate experiments when we make future infrastructure changes as we should be able to theoretically just wipe and re-create the heads directory of each experiment and not have to reach into so many directories as we would now.
Steps to reproduce
Expected behavior
Should be able to run.
Screenshots
No response
Code Platform
Windows Build Number
Other Windows Build number
No response
App minimum and target SDK version
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
No response
Help us help you
Yes, but only if others can assist.