search

dotnet / upgrade-assistant

A tool to assist developers in upgrading .NET Framework applications to .NET 6 and beyond
MIT License
1.11k stars 163 forks source link

Long project names prevent using default visual studio repository location #429

Closed oteinone closed 3 years ago

oteinone commented 3 years ago

Describe the bug

Some paths are nested too deep when building the solution in visual studio

To Reproduce

  1. Clone the repo to e.g. c:\users\edwardcontoso\source\repos\upgrade-assistant
  2. Open in visual studio
  3. Try to build

Exceptions (if any)

The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

Further technical details

Example file that was nested too deep: C:\Users\otto\source\ext-repos\upgrade-assistant\artifacts\obj\Microsoft.DotNet.UpgradeAssistant.Extensions.Default.Analyzers.Package\Debug\netstandard2.0\Microsoft.DotNet.UpgradeAssistant.Extensions.Default.Analyzers.Package.GeneratedMSBuildEditorConfig.editorconfig

twsouthwick commented 3 years ago

Can you enable long file support?

oteinone commented 3 years ago

I definitely can but I just moved the whole thing under c:\Code to get going. Just thought to report it if you feel like making the project more accessible. Feel free to close this if it doesn't feel relevant.

sunandabalu commented 3 years ago

We can update the readme to call out enabling long path support, no other action needed here.

sunandabalu commented 3 years ago

465 added the note to the contributing guide, closing this issue.