![]() Maybe setting the Workspace base path variable of NCrunch to something like C:\Temp\NC could help. Is it possible to have another look at this? So now it appears that VS2019 properly supports the long paths, but NCrunch does not. Could not find a part of the path 'bin\Debug\netcoreapp3.1\pact-linux-x86_64\lib\vendor\ruby\2.2.0\gems\pact-provider-verifier-1.30.0\lib\pact\provider_verifier\provider_states\remove_provider_states_header_middleware.rb'. \.\.\program files (x86)\microsoft visual studio\2019\professional\MSBuild\Current\Bin\ (4643, 5): Unable to copy file "C:\Users\ian.darroch\.nuget\packages\pactnet.linux.圆4\2.5.2\tools\pact-linux-x86_64\lib\vendor\ruby\2.2.0\gems\pact-provider-verifier-1.30.0\lib\pact\provider_verifier\provider_states\remove_provider_states_header_middleware.rb" to "bin\Debug\netcoreapp3.1\pact-linux-x86_64\lib\vendor\ruby\2.2.0\gems\pact-provider-verifier-1.30.0\lib\pact\provider_verifier\provider_states\remove_provider_states_header_middleware.rb". The third party package is for PACT testing, and results in errors like this when building from NCrunch: I then tried to verify my colleague's experience by shifting the solution to a longer path. I enabled the LongPathsEnabled setting on my machine (and restarted to make sure it took effect), but NCrunch still complains the path is too long. He altered the setting as mentioned in this link how to make windows 10 accept file paths over 260 characters (which sets the registry value shown by the OP), and found that VS could now compile the project.įor myself, I was not originally having the problem with VS, as my solution path was just short enough to allow the build to proceed, but I was having a problem with NCrunch, as the build worker path was slightly longer. One of my colleagues (who does not have NCrunch) was having a problem with Visual Studio 2019 not building a project that pulls in a package which has files in long paths. The Long Path Tool provides a straightforward solution to a problem faced by many Windows users: managing files with path names that exceed the character limit imposed by the operating system. I saw this issue was raised a couple of years back Path too long error prevents project from building, but I have run into it today.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |