Bug 17808 – VisualD doesn't work if Visual Studio is installed to non-ASCII path

Created attachment 1656 Build script with mangled paths Windows 10, Polish locale, Visual Studio Community 2015, VisualD 0.45.1. Visual Studio is installed at D:\Pliki programów (x86)\Microsoft Visual Studio 14.0 When I run the installer for VisualD, it detects that I have VS2015 installed, but then it proceeds to install the extension to D:\Pliki program� (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions Note the invalid character. After the installation, Visual Studio listed the extension on the extension list, but the extension obviously did not load. I was unable to create any D projects or change D-related settings. After I moved the extension manually, it loaded and I could create a new project, but then it still wouldn't work: - running the x86 target displays a console window for a fraction of a second, shows the following in the output, and does nothing else: C:\Windows\SysWOW64\kernel32.dll unloaded. C:\Windows\SysWOW64\dbghelp.dll unloaded. The thread 0x7a4 has exited with code 0 (0x0). The thread 0x29c has exited with code 0 (0x0). The thread 0xf4 has exited with code 0 (0x0). The program '[2596] ConsoleApp1.exe' has exited with code 0 (0x0). - as for the x64 target, the build script (x64\Debug\ConsoleApp1.build.cmd) contains wrong paths (two different ones!) as well, so VS cannot build anything. I've attached the file. VS failed to produce any executables.

Thanks for the report. > but then it proceeds to install the extension to D:\Pliki program� (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions Is it only visuald.pkgdef that is in the wrong place or are extension.vsixmanifest and vdlogo.ico affected aswell? > running the x86 target displays a console window for a fraction of a second, shows the following in the output, and does nothing else: Try switching the debug engine to "Visual Studio" (debugging settings). > as for the x64 target, the build script (x64\Debug\ConsoleApp1.build.cmd) contains wrong paths (two different ones!) as well, so VS cannot build anything. I've attached the file. As a workaround you could try replacing $(VCInstallDir) and similar macros in the global options with the explicit path.

(In reply to Rainer Schuetze from comment #1) Please disregard whatever I wrote about the x86, it appears to had worked correctly. > Is it only visuald.pkgdef that is in the wrong place or are > extension.vsixmanifest and vdlogo.ico affected aswell? All three files were misplaced. In fact, there was not even a "Rainer Schuetze" folder in the correct location. > > as for the x64 target, the build script (x64\Debug\ConsoleApp1.build.cmd) contains wrong paths (two different ones!) as well, so VS cannot build anything. I've attached the file. > > As a workaround you could try replacing $(VCInstallDir) and similar macros > in the global options with the explicit path. After I replaced the paths, the names in the build script were still wrong. It appears that they are being encoded in CP582 and then decoded as Windows 1250, so I used ˇ instead of ó and it managed to start the linker. Then it turned out that the library paths are being decoded not as Windows 1250, but as UTF-8, and VS didn't let me use ├│ in configuration values. I copied the libraries to another location and finally I managed to get a working x64 executable and even the debugger works, but I ended up having extra 500MB of static libraries. So it kinda works, but it's hacky.

Installation with non-ASCII paths should work with https://github.com/dlang/visuald/releases/tag/v0.46.0-beta1. Working with characters not in your standard code page might still cause trouble when having to pass them through batch files used during building, though.

fixes now released in https://github.com/dlang/visuald/releases/tag/v0.46.0