September 05, 2017 [Issue 17808] New: VisualD doesn't work if Visual Studio is installed to non-ASCII path | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=17808 Issue ID: 17808 Summary: VisualD doesn't work if Visual Studio is installed to non-ASCII path Product: D Version: D2 Hardware: x86_64 OS: Windows Status: NEW Severity: minor Priority: P1 Component: visuald Assignee: nobody@puremagic.com Reporter: karol.m.stasiak@gmail.com Created attachment 1656 --> https://issues.dlang.org/attachment.cgi?id=1656&action=edit 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. -- |
Copyright © 1999-2021 by the D Language Foundation