Jump to page: 1 2
Thread overview
VisualD installer does not find visual studio 2019 community edition
Jun 08
exo1
Jun 08
exo1
Jun 09
Seb
Jun 09
exo1
Jun 09
exo1
Jun 09
exo1
Jun 10
exo1
Jun 13
exo1
Jun 09
exo1
June 08
Hello,
I am trying to install visualD because it supports using dmd-fe to provide goto-def and is therefore much better than the vscode extension.
However, its installer is not able to detect vs2019-community. I have reinstalled (vs2019 + c++ for desktop) three times and restarted afterwards, and still the installer does not detect it.
Has anybody been able to use VisualD 0.52.0 with vs2019 community?
June 08
On Monday, 8 June 2020 at 11:05:10 UTC, exo1 wrote:
> Hello,
> I am trying to install visualD because it supports using dmd-fe to provide goto-def and is therefore much better than the vscode extension.
> However, its installer is not able to detect vs2019-community. I have reinstalled (vs2019 + c++ for desktop) three times and restarted afterwards, and still the installer does not detect it.
> Has anybody been able to use VisualD 0.52.0 with vs2019 community?

Okay so I reinstalled 4th time by first cleaning up with InstallCleanup.exe (https://docs.microsoft.com/en-us/visualstudio/install/remove-visual-studio?view=vs-2019) and this time VisualD got installed.

However when I enable "Experimental: use DMD parsing engine for semantic analysis", i get lots of weird errors during intellisense (not during building) -
```
errors in imported modules:
Error: C:\D\dmd2\src\phobos\std\stdio.d(16): module `core.stdc.stddef` import `wchar_t` not found
Error: C:\D\dmd2\src\druntime\import\core\stdc\time.d(151): undefined identifier `time_t`, did you mean function `time`?
Error: C:\D\dmd2\src\druntime\import\core\stdc\time.d(151): undefined identifier `time_t`, did you mean function `time`?
Error: C:\D\dmd2\src\druntime\import\core\stdc\time.d(153): undefined identifier `time_t`, did you mean function `time`?
Error: C:\D\dmd2\src\druntime\import\core\stdc\time.d(153): undefined identifier `tm`
etc. etc.
```
and
```
errors in imported modules:
Error: C:\D\dmd2\src\druntime\import\core\stdc\stdio.d(1243): unrecognized `pragma(printf)`
Error: C:\D\dmd2\src\druntime\import\core\stdc\stdio.d(1246): unrecognized `pragma(scanf)`
Error: C:\D\dmd2\src\druntime\import\core\stdc\stdio.d(1249): unrecognized `pragma(printf)`
Error: C:\D\dmd2\src\druntime\import\core\stdc\stdio.d(1252): unrecognized `pragma(scanf)`
Error: C:\D\dmd2\src\druntime\import\core\stdc\stdio.d(1255): unrecognized `pragma(printf)`
etc. etc.
```

DMD parsing engine was the only reason I tried to use VisualD. However it does not work for some reason. Maybe it needs to be updated for the latest D release? IDK. The editor tooling for Dlang is really bad :(

June 09
On Monday, 8 June 2020 at 11:23:49 UTC, exo1 wrote:
> On Monday, 8 June 2020 at 11:05:10 UTC, exo1 wrote:
>> [...]
>
> Okay so I reinstalled 4th time by first cleaning up with InstallCleanup.exe (https://docs.microsoft.com/en-us/visualstudio/install/remove-visual-studio?view=vs-2019) and this time VisualD got installed.
>
> [...]

Pragma(printf) and friends are a very recent addition from the latest release: https://dlang.org/changelog/2.092.0.html#printfParams2

You could temporarily try to use 2.091 which should probably fix this issue until VisualD has been updated.
June 09

On 08/06/2020 13:23, exo1 wrote:
> On Monday, 8 June 2020 at 11:05:10 UTC, exo1 wrote:
>> Hello,
>> I am trying to install visualD because it supports using dmd-fe to
>> provide goto-def and is therefore much better than the vscode extension.
>> However, its installer is not able to detect vs2019-community. I have
>> reinstalled (vs2019 + c++ for desktop) three times and restarted
>> afterwards, and still the installer does not detect it.
>> Has anybody been able to use VisualD 0.52.0 with vs2019 community?
> 
> Okay so I reinstalled 4th time by first cleaning up with
> InstallCleanup.exe
> (https://docs.microsoft.com/en-us/visualstudio/install/remove-visual-studio?view=vs-2019)
> and this time VisualD got installed.

How did you install VS? Latest version? Visual D searches the installation database in the registry to find an appropriate entry. Not sure what can go wrong there...

> However when I enable "Experimental: use DMD parsing engine for semantic
> analysis", i get lots of weird errors during intellisense (not during
> building) -
> ```
> errors in imported modules:
> Error: C:\D\dmd2\src\phobos\std\stdio.d(16): module `core.stdc.stddef`
> import `wchar_t` not found
> Error: C:\D\dmd2\src\druntime\import\core\stdc\time.d(151): undefined
> identifier `time_t`, did you mean function `time`?
> Error: C:\D\dmd2\src\druntime\import\core\stdc\time.d(151): undefined
> identifier `time_t`, did you mean function `time`?
> Error: C:\D\dmd2\src\druntime\import\core\stdc\time.d(153): undefined
> identifier `time_t`, did you mean function `time`?
> Error: C:\D\dmd2\src\druntime\import\core\stdc\time.d(153): undefined
> identifier `tm`
> etc. etc.
> ```
> and
> ```
> errors in imported modules:
> Error: C:\D\dmd2\src\druntime\import\core\stdc\stdio.d(1243):
> unrecognized `pragma(printf)`
> Error: C:\D\dmd2\src\druntime\import\core\stdc\stdio.d(1246):
> unrecognized `pragma(scanf)`
> Error: C:\D\dmd2\src\druntime\import\core\stdc\stdio.d(1249):
> unrecognized `pragma(printf)`
> Error: C:\D\dmd2\src\druntime\import\core\stdc\stdio.d(1252):
> unrecognized `pragma(scanf)`
> Error: C:\D\dmd2\src\druntime\import\core\stdc\stdio.d(1255):
> unrecognized `pragma(printf)`
> etc. etc.
> ```
> 
> DMD parsing engine was the only reason I tried to use VisualD. However it does not work for some reason. Maybe it needs to be updated for the latest D release? IDK. The editor tooling for Dlang is really bad :(
> 

As Sebastian mentioned this looks like a mismatch between compiler versions, the parsing engine doesn't know these pragmas yet.

I've made a new beta updated to dmd 2.092:

https://github.com/dlang/visuald/releases/tag/v1.0.0-beta1
June 09
On Tuesday, 9 June 2020 at 06:26:21 UTC, Rainer Schuetze wrote:
>
>
> How did you install VS? Latest version? Visual D searches the installation database in the registry to find an appropriate entry. Not sure what can go wrong there...
>

I had both vs 2019 build tools and vs 2019 community installed. So, when I tried to install VisualD the first time, I got options for integrating it with both the build tools and community, whether I selected both build tools and community or just community did not matter because it only installed the files into build tools folders and not into community.
So after that I uninstalled build tools, and then VisualD installer stopped showing me both build tools and community. (Also to note that the community edition was previously installed with installation nickname 2, however now I changed the nickname by modifying some files found on a answer to a stackoverflow question).
Now, I though that something might have gone wrong because of the nickname stuff, so I "repaired" VS2019 community edition. Still Visual D installer did not work. Then I reinstalled VS2019 community edition, it did not work. I tried starting the installer from a cmd prompt by first running vcvars_all.bat and then the installer, still nothing. I tried a few more things, it did not work.
So then finally I found out about clean uninstall which deletes every registry keys or whatever files it had created on disk as well. So I ran InstallCleanup.exe, uninstalled VS completely, reinstalled and then it finally worked.
(Also, to note that I restarted my computer everytime I repaired/reinstalled/did any changes to VS installation)

>
> As Sebastian mentioned this looks like a mismatch between compiler versions, the parsing engine doesn't know these pragmas yet.
>
> I've made a new beta updated to dmd 2.092:
>
> https://github.com/dlang/visuald/releases/tag/v1.0.0-beta1

I will try this updated version. However, what about these errors -
```
errors in imported modules:
Error: C:\D\dmd2\src\phobos\std\stdio.d(16): module `core.stdc.stddef` import `wchar_t` not found
Error: C:\D\dmd2\src\druntime\import\core\stdc\time.d(151): undefined identifier `time_t`, did you mean function `time`?
Error: C:\D\dmd2\src\druntime\import\core\stdc\time.d(151): undefined identifier `time_t`, did you mean function `time`?
Error: C:\D\dmd2\src\druntime\import\core\stdc\time.d(153): undefined identifier `time_t`, did you mean function `time`?
Error: C:\D\dmd2\src\druntime\import\core\stdc\time.d(153): undefined identifier `tm`
etc. etc.
```
I tried the older DMD version that comes bundled with VisualD installation and I get these errors on that version as well.
June 09
On Tuesday, 9 June 2020 at 07:00:19 UTC, exo1 wrote:
> I will try this updated version. However, what about these errors -

Those errors are no more. Yay!!!

However, go to definition for overloaded procs show a list of overloads instead of automatically going to the correct one. I thought the DMD engine was supposed to work automatically?
June 09
On Tuesday, 9 June 2020 at 07:15:25 UTC, exo1 wrote:
> On Tuesday, 9 June 2020 at 07:00:19 UTC, exo1 wrote:
>> I will try this updated version. However, what about these errors -
>
> Those errors are no more. Yay!!!
>
> However, go to definition for overloaded procs show a list of overloads instead of automatically going to the correct one. I thought the DMD engine was supposed to work automatically?

Also "VisualD -> Compile and Run" does not seem to work. "Compile and Debug" & "Compile and Disassemble" work.
And, it does not display any errors in the code, not even when I save my code.
June 09
On Tuesday, 9 June 2020 at 06:26:21 UTC, Rainer Schuetze wrote:

>
> I've made a new beta updated to dmd 2.092:
>

This version seems to be crashing on a fresh project created through `dub init`.

According to windows task manager, dmdserver goes up to about 41mb memory, then crashes, then the extensions restarts dmdserver, it goes up to about 41mb memory, then crashes again.

(does not seem to crash with a D project created through VS template, however it takes 500mb ram for a hello world project)
June 10

On 09/06/2020 09:23, exo1 wrote:
> On Tuesday, 9 June 2020 at 07:15:25 UTC, exo1 wrote:
>> On Tuesday, 9 June 2020 at 07:00:19 UTC, exo1 wrote:
>>> I will try this updated version. However, what about these errors -
>>
>> Those errors are no more. Yay!!!
>>
>> However, go to definition for overloaded procs show a list of overloads instead of automatically going to the correct one. I thought the DMD engine was supposed to work automatically?
> 
> Also "VisualD -> Compile and Run" does not seem to work. "Compile and
> Debug" & "Compile and Disassemble" work.
> And, it does not display any errors in the code, not even when I save my
> code.

Are you using a VS project, or are you just editing source files that you build through dub?
June 10

On 09/06/2020 09:37, exo1 wrote:
> On Tuesday, 9 June 2020 at 06:26:21 UTC, Rainer Schuetze wrote:
> 
>>
>> I've made a new beta updated to dmd 2.092:
>>
> 
> This version seems to be crashing on a fresh project created through `dub init`
> 
> According to windows task manager, dmdserver goes up to about 41mb memory, then crashes, then the extensions restarts dmdserver, it goes up to about 41mb memory, then crashes again.

I can reproduce this. Will have to investigate...

> 
> (does not seem to crash with a D project created through VS template, however it takes 500mb ram for a hello world project)

Memory usage should be similar to what the compiler is using (with -lowmem).
« First   ‹ Prev
1 2