On Friday, 10 July 2020 at 07:32:42 UTC, Jacob Carlborg wrote:

> Yeah, VisualD has a huge advantage since it's now using the DMD frontend for these things. For example, DCD does not support UFCS, which is really annoying.

That is the most annoying thing for sure: It would be great to have the semantic engine of visual-d exposed via a language server ...

/P

On 7/9/2020 11:21 PM, Rainer Schuetze wrote:
> My first open source project was cv2pdb, a tool that converts old-style
> CodeView debug information generated by optlink to a PDB file. Now that
> this functionality is more or less available in dmd itself when
> compiling to COFF object files, cv2pdb seems to be more popular among
> C++ people using gcc on Windows, because it also allows to convert DWARF
> to PDB.

I hope cv2pdb is in D, as that is a fine way to get C++ people used to D!

On 10/07/2020 9:04 PM, Walter Bright wrote:
> I hope cv2pdb is in D, as that is a fine way to get C++ people used to D!

https://github.com/rainers/cv2pdb

Nope.

On Wednesday, 8 July 2020 at 09:09:40 UTC, Manu wrote:
> I've been testing the first-install process for almost 10 years.
> I haven't had any problems with first-install for at least 6 years.
>
> Make sure to create bug reports for issues like that; what version of VS are you using? Are there any non-standard elements to your installation or dev environment?

Just installed Visual Studio Community 2019 and then VisualD from scratch. It looks like VS has no idea that VisualD is installed at all. So there is definitely an issue here.

On Friday, 10 July 2020 at 13:53:39 UTC, psycha0s wrote:
>
> Just installed Visual Studio Community 2019 and then VisualD from scratch. It looks like VS has no idea that VisualD is installed at all. So there is definitely an issue here.

I think you have the same problem as this reported bug.

https://issues.dlang.org/show_bug.cgi?id=21028

Check the comments how to fix the problem with an existing VisualD installation.

On Friday, 10 July 2020 at 13:53:39 UTC, psycha0s wrote:
> Just installed Visual Studio Community 2019 and then VisualD from scratch. It looks like VS has no idea that VisualD is installed at all. So there is definitely an issue here.

Okay, sorry, I figured it out. It was my fault. I'm a Linux guy, so I'm not used to all Windows stuff. It seems I didn't complete the installation of Visual Studio. The installer asked me to reboot the computer and it was going to install some additional components after that. But after rebooting it didn't do a thing, so I assumed everything is already installed and ran VS.

On Saturday, 4 July 2020 at 14:42:05 UTC, Manu wrote:
> This is huge!
>
> Congrats on the super cool milestone with a bunch of really great new stuff.
> Thanks so much for your tireless work Rainer!
> I wouldn't be here without all your effort on this.
>
> On Sat, Jul 4, 2020 at 11:05 PM Rainer Schuetze via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote:
>
>> Hello,
>>
>> after having passed the 10 year anniversary of public availability recently, it is finally time to release version 1.0 of Visual D, the Visual Studio extension that adds D language support to VS 2008-2019.
>>
>> You can find the installer at http://rainers.github.io/visuald/visuald/StartPage.html
>>
>> Highlights from this release:
>>
>> - semantic engine based on dmd front end now enabled by default and updated to 2.092. If you are low on memory or run a 32-bit Windows, you should switch back to the legacy engine.
>>
>> - debugger extension mago will now evaluate struct or class properties (methods or fields) __debugOverview, __debugExpanded and __debugTextView to customize the debugger display. mago can even display forward ranges as a list, but that is currently rather slow, so it is disabled by default (see debugger options).
>>
>> - the bar on the top of the edit window now displays the current edit scope and allows faster navigation within a source file (needs the dmd based engine)
>>
>> - ever wondered how to navigate to the type of a variable declared by `auto` inference? clicking an identifier in a tool tip from intellisense will now jump to its definition (only with the dmd based engine)
>>
>> See https://rainers.github.io/visuald/visuald/VersionHistory.html for the complete list of changes.
>>
>> Cheers,
>> Rainer

Each time run visualD project I get this error. I really did not know what i am not doing well. I will appreciate your help



Build Log

Building Win32\Debug\WindowsApp2.exe

Command Line

set PATH=C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\bin\HostX86\x86;C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE;C:\Program Files (x86)\Windows Kits\10\bin;C:\D\dmd-2.093.0\windows\bin;%PATH%
set DMD_LIB=C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\lib\x86;C:\Program Files (x86)\Windows Kits\10\Lib\10.0.18362.0\ucrt\x86
set VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\
set VCTOOLSINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\
set VSINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\
set WindowsSdkDir=C:\Program Files (x86)\Windows Kits\10\
set WindowsSdkVersion=10.0.18362.0
set UniversalCRTSdkDir=C:\Program Files (x86)\Windows Kits\10\
set UCRTVersion=10.0.18362.0
"C:\Program Files (x86)\VisualD\pipedmd.exe" -deps Win32\Debug\WindowsApp2.dep dmd -debug -m32mscoff -g -gf -X -Xf"Win32\Debug\WindowsApp2.json" -c -of"Win32\Debug\WindowsApp2.obj" WindowsApp2.d
if %errorlevel% neq 0 goto reportError

set LIB=C:\D\dmd-2.093.0\windows\bin\..\lib32mscoff
echo. > C:\Users\great\source\repos\WindowsApp2\Win32\Debug\WindowsApp2.link.rsp
echo "Win32\Debug\WindowsApp2.obj" /OUT:"Win32\Debug\WindowsApp2.exe" user32.lib  >> C:\Users\great\source\repos\WindowsApp2\Win32\Debug\WindowsApp2.link.rsp
echo kernel32.lib  >> C:\Users\great\source\repos\WindowsApp2\Win32\Debug\WindowsApp2.link.rsp
echo legacy_stdio_definitions.lib /LIBPATH:"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\lib\x86" /LIBPATH:"C:\Program Files (x86)\Windows Kits\10\Lib\10.0.18362.0\ucrt\x86" /DEBUG /PDB:"Win32\Debug\WindowsApp2.pdb" /INCREMENTAL:NO /NOLOGO /NODEFAULTLIB:libcmt libcmtd.lib /SUBSYSTEM:CONSOLE >> C:\Users\great\source\repos\WindowsApp2\Win32\Debug\WindowsApp2.link.rsp
"C:\Program Files (x86)\VisualD\mb2utf16.exe" C:\Users\great\source\repos\WindowsApp2\Win32\Debug\WindowsApp2.link.rsp

"C:\Program Files (x86)\VisualD\pipedmd.exe" -msmode -deps Win32\Debug\WindowsApp2.lnkdep "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\bin\HostX86\x86\link.exe" @C:\Users\great\source\repos\WindowsApp2\Win32\Debug\WindowsApp2.link.rsp
if %errorlevel% neq 0 goto reportError
if not exist "Win32\Debug\WindowsApp2.exe" (echo "Win32\Debug\WindowsApp2.exe" not created! && goto reportError)

goto noError

:reportError
echo Building Win32\Debug\WindowsApp2.exe failed!

:noError
Output

LINK : fatal error LNK1181: cannot open input file 'user32.lib'
Building Win32\Debug\WindowsApp2.exe failed!

On 12/07/2020 11:11, greatsam4sure wrote:
[...]
> set WindowsSdkDir=C:\Program Files (x86)\Windows Kits\10\
> set WindowsSdkVersion=10.0.18362.0
> set UniversalCRTSdkDir=C:\Program Files (x86)\Windows Kits\10\
> set UCRTVersion=10.0.18362.0
[...]
> echo legacy_stdio_definitions.lib /LIBPATH:"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\lib\x86" /LIBPATH:"C:\Program Files (x86)\Windows Kits\10\Lib\10.0.18362.0\ucrt\x86"
[...]
> 
> LINK : fatal error LNK1181: cannot open input file 'user32.lib' Building Win32\Debug\WindowsApp2.exe failed!


I suspect you don't have the Windows SDK installed with Visual Studio. user32.lib is usually found in "C:\Program Files (x86)\Windows Kits\10\lib\10.0.18362.0\um\x86", but that path is not passed on the command line with /LIBPATH.

On 12/07/2020 23:35, Rainer Schuetze wrote:
> 
> 
> On 12/07/2020 11:11, greatsam4sure wrote:
> [...]
>> set WindowsSdkDir=C:\Program Files (x86)\Windows Kits\10\
>> set WindowsSdkVersion=10.0.18362.0
>> set UniversalCRTSdkDir=C:\Program Files (x86)\Windows Kits\10\
>> set UCRTVersion=10.0.18362.0
> [...]
>> echo legacy_stdio_definitions.lib /LIBPATH:"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\lib\x86" /LIBPATH:"C:\Program Files (x86)\Windows Kits\10\Lib\10.0.18362.0\ucrt\x86"
> [...]
>>
>> LINK : fatal error LNK1181: cannot open input file 'user32.lib' Building Win32\Debug\WindowsApp2.exe failed!
> 
> 
> I suspect you don't have the Windows SDK installed with Visual Studio. user32.lib is usually found in "C:\Program Files (x86)\Windows Kits\10\lib\10.0.18362.0\um\x86", but that path is not passed on the command line with /LIBPATH.
> 

On second thought: if you installed the SDK after Visual D, the settings
in "Tools -> Options -> Projects and Solutions -> Visual D Settings ->
DMD directories -> Win32 COFF32 -> Library Paths" might not reflect that
(it should contain something like
$(WindowsSdkDir)lib\$(WindowsSdkVersion)\um\x86).

You can also click "Reset Settings" on the Visual D settings page to correct that.

On Monday, 13 July 2020 at 06:48:02 UTC, Rainer Schuetze wrote:
>
>
> On 12/07/2020 23:35, Rainer Schuetze wrote:
>> 
>> 
>> On 12/07/2020 11:11, greatsam4sure wrote:
>> [...]
>>> [...]
>> [...]
>>> [...]
>> [...]
>>> [...]
>> 
>> 
>> I suspect you don't have the Windows SDK installed with Visual Studio. user32.lib is usually found in "C:\Program Files (x86)\Windows Kits\10\lib\10.0.18362.0\um\x86", but that path is not passed on the command line with /LIBPATH.
>> 
>
> On second thought: if you installed the SDK after Visual D, the settings
> in "Tools -> Options -> Projects and Solutions -> Visual D Settings ->
> DMD directories -> Win32 COFF32 -> Library Paths" might not reflect that
> (it should contain something like
> $(WindowsSdkDir)lib\$(WindowsSdkVersion)\um\x86).
>
> You can also click "Reset Settings" on the Visual D settings page to correct that.



Thanks a lot. I will look into that today