You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently attempting to build and run the DevToys.Windows project in VS 2022 but getting the following error when attempting to build:
Severity Code Description Project File Line Suppression State Details
Error (active) CS0016 Could not write to output file 'D:\source\CoreyHayward\DevToys\obj\AnyCPU\DevToys.Business\Debug\net8.0\generated\CommunityToolkit.Mvvm.SourceGenerators\CommunityToolkit.Mvvm.SourceGenerators.RelayCommandGenerator\DevToys.Business.ViewModels.ToolPageViewModel.ToggleSelectedMenuItemFavorite.g.cs' -- 'Could not find a part of the path 'D:\source\CoreyHayward\DevToys\obj\AnyCPU\DevToys.Business\Debug\net8.0\generated\CommunityToolkit.Mvvm.SourceGenerators\CommunityToolkit.Mvvm.SourceGenerators.RelayCommandGenerator\DevToys.Business.ViewModels.ToolPageViewModel.ToggleSelectedMenuItemFavorite.g.cs'.' DevToys.Business (net8.0) D:\source\CoreyHayward\DevToys\src\app\dev\DevToys.Business\CSC 1
Hi,
I suspect you encounter this issue because your Windows doesn't have LongPath enabled. By default, Windows paths are limited to 255 characters, and the one you shared is longer than that.
It's not the first time someone encounter a similar issue. I just made a few changes to give a heads up when building and when running init.ps1.
Current behavior
Currently attempting to build and run the
DevToys.Windows
project in VS 2022 but getting the following error when attempting to build:I have followed the steps in the Contributing.MD guide
How to reproduce it (as minimally and precisely as possible)
.\init.ps1
DevToys-Windows.sln
(Visual Studio 2022)DevToys.Windows
Expected behavior
Builds correctly
Screenshots
Workaround
No response
Affected platforms
Windows
Affected DevToys kind
DevToys (app with GUI)
DevToys Version
Commit: 79c33ce
Relevant Assets/Logs
No response
The text was updated successfully, but these errors were encountered: