Debugging with Visual Studio 2026

If you debug on Visual Studio 2026, you may receive the following warning that prevents running Scripture Forge from Visual Studio

Could not copy "{YOUR PATH HERE}\web-xforge\src\RealtimeServer\node_modules\@aws-sdk\credential-provider-cognito-identity\node_modules\@aws-sdk\client-cognito-identity\dist-types\ts3.4\commands\GetOpenIdTokenForDeveloperIdentityCommand.d.ts" to "bin\Debug\net8.0\RealtimeServer\node_modules\@aws-sdk\credential-provider-cognito-identity\node_modules\@aws-sdk\client-cognito-identity\dist-types\ts3.4\commands\GetOpenIdTokenForDeveloperIdentityCommand.d.ts". Beginning retry 1 in 1000ms. Could not find a part of the path 'bin\Debug\net8.0\RealtimeServer\node_modules\@aws-sdk\credential-provider-cognito-identity\node_modules\@aws-sdk\client-cognito-identity\dist-types\ts3.4\commands\GetOpenIdTokenForDeveloperIdentityCommand.d.ts'.

This occurs because your web-xforge directory is too deep in your file system. To resolve this you can:

1. Run dotnet run from the command line then attach the debugger.
2. Use Visual Studio Code.
3. Move web-xforge to the root of your drive.
4. Modify your registry to enable long paths:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"LongPathsEnabled"=dword:00000001