www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.ide - VisualD

reply Rinzwind <rinzwind live.nl> writes:
Brand new Windows 10 install with Visual Studio 2022.

Added latest Visual D, but the standard templates are nowhere to 
be found (at 'create a new project')? Remember this being an 
issue before too. Anyway to manually fix this?
Feb 27
parent reply Rainer Schuetze <r.sagitario gmx.de> writes:
On 27/02/2022 09:55, Rinzwind wrote:
 Brand new Windows 10 install with Visual Studio 2022.
 
 Added latest Visual D, but the standard templates are nowhere to be 
 found (at 'create a new project')? Remember this being an issue before 
 too. Anyway to manually fix this?
Cannot reproduce here, though I don't have a completely fresh installation without other VS versions. Is it only that the project templates are missing or does the extension not show up at all? For example, is Visual D shown in the extensions menu? If not, maybe it has to be enabled in "Manage Extensions".
Mar 01
parent reply Rinzwind <rinzwind live.nl> writes:
On Wednesday, 2 March 2022 at 07:50:02 UTC, Rainer Schuetze wrote:
 On 27/02/2022 09:55, Rinzwind wrote:
 Brand new Windows 10 install with Visual Studio 2022.
 
 Added latest Visual D, but the standard templates are nowhere 
 to be found (at 'create a new project')? Remember this being 
 an issue before too. Anyway to manually fix this?
Cannot reproduce here, though I don't have a completely fresh installation without other VS versions. Is it only that the project templates are missing or does the extension not show up at all? For example, is Visual D shown in the extensions menu? If not, maybe it has to be enabled in "Manage Extensions".
The Visual D menu is there in Extensions... It is just that it is not listed under language drop down at new project. I do have a C:\Program Files (x86)\VisualD\Templates folder. How does VS know to look here?
Mar 02
parent reply Rainer Schuetze <r.sagitario gmx.de> writes:
On 02/03/2022 09:51, Rinzwind wrote:
 On Wednesday, 2 March 2022 at 07:50:02 UTC, Rainer Schuetze wrote:
 On 27/02/2022 09:55, Rinzwind wrote:
 Brand new Windows 10 install with Visual Studio 2022.

 Added latest Visual D, but the standard templates are nowhere to be 
 found (at 'create a new project')? Remember this being an issue 
 before too. Anyway to manually fix this?
Cannot reproduce here, though I don't have a completely fresh installation without other VS versions. Is it only that the project templates are missing or does the extension not show up at all? For example, is Visual D shown in the extensions menu? If not, maybe it has to be enabled in "Manage Extensions".
The Visual D menu is there in Extensions... It is just that it is not listed under language drop down at new project. I do have a C:\Program Files (x86)\VisualD\Templates folder. How does VS know to look here?
The project templates are given by the Asset Microsoft.VisualStudio.ProjectTemplate defined in "c:\Program Files\Microsoft Visual Studio\2022\Preview\Common7\IDE\Extensions\Rainer Schuetze\VisualD\1.2\extension.vsixmanifest" Maybe there is a problem with the path using the short name "Progra~2" instead of "Program Files (x86)". If you change that you might have to force an update of the extension cache by modifying "c:\Program Files\Microsoft Visual Studio\2022\Preview\Common7\IDE\Extensions\extensions.configurationchanged".
Mar 02
parent reply Rinzwind <rinzwind live.nl> writes:
On Wednesday, 2 March 2022 at 21:50:43 UTC, Rainer Schuetze wrote:
 On 02/03/2022 09:51, Rinzwind wrote:
 On Wednesday, 2 March 2022 at 07:50:02 UTC, Rainer Schuetze 
 wrote:
 On 27/02/2022 09:55, Rinzwind wrote:
 [...]
Cannot reproduce here, though I don't have a completely fresh installation without other VS versions. Is it only that the project templates are missing or does the extension not show up at all? For example, is Visual D shown in the extensions menu? If not, maybe it has to be enabled in "Manage Extensions".
The Visual D menu is there in Extensions... It is just that it is not listed under language drop down at new project. I do have a C:\Program Files (x86)\VisualD\Templates folder. How does VS know to look here?
The project templates are given by the Asset Microsoft.VisualStudio.ProjectTemplate defined in "c:\Program Files\Microsoft Visual Studio\2022\Preview\Common7\IDE\Extensions\Rainer Schuetze\VisualD\1.2\extension.vsixmanifest" Maybe there is a problem with the path using the short name "Progra~2" instead of "Program Files (x86)". If you change that you might have to force an update of the extension cache by modifying "c:\Program Files\Microsoft Visual Studio\2022\Preview\Common7\IDE\Extensions\extensions.configurationchanged".
I finally tried it, and it worked! Just as test I changed it back to Progra~2, and it still workded. Maybe just the modified date change of extensions.configurationchanged was needed? Anyway, thanks. Hopefully something that can be 'fixed' in the installer. Just as reference, the VS community path is C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\Extensions
Mar 17
next sibling parent reply Rinzwind <rinzwind live.nl> writes:
Hmm first I got this when trying to compile/run:

TRACKER : error TRK0005: Failed to locate: "dmd". The system 
cannot find the file specified.

I did see DMD was installed in C:\D, but apparently no 
environmental path added. Downloaded DMD which did add 
C:\D\dmd2\windows\bin; to %path%

Still not much luck; sample project

import core.sys.windows.windows;

windows is underlined as error, windows.d cannot be read

Trying to run results in
Build started...
------ Build started: Project: WindowsApp2, Configuration: Debug 
x64 ------
Building x64\Debug\WindowsApp2.exe...
LINK : fatal error LNK1104: cannot open file 'phobos64.lib'
Building x64\Debug\WindowsApp2.exe failed!

This is all on a recent and clean Windows 10 64 bit install.

Probably easy to fix if one knows the details, but I don't. Just 
getting my feed wet with D and even did not use Visual Studio 
much before.
Mar 17
parent reply Mike Parker <aldacron gmail.com> writes:
On Friday, 18 March 2022 at 05:11:21 UTC, Rinzwind wrote:

 Probably easy to fix if one knows the details, but I don't. 
 Just getting my feed wet with D and even did not use Visual 
 Studio much before.
You can set the path to DMD and other tools in the global settings: https://rainers.github.io/visuald/visuald/GlobalOptions.html
Mar 18
parent Rainer Schuetze <r.sagitario gmx.de> writes:
On 18/03/2022 14:13, Mike Parker wrote:
 On Friday, 18 March 2022 at 05:11:21 UTC, Rinzwind wrote:
 
 Probably easy to fix if one knows the details, but I don't. Just 
 getting my feed wet with D and even did not use Visual Studio much 
 before.
You can set the path to DMD and other tools in the global settings: https://rainers.github.io/visuald/visuald/GlobalOptions.html
Indeed, setting it there should help. The issue is that VS 2022 is a 64-bit process so Visual D installer doesn't pick up the registry entries from the 32-bit installers by default. See also https://issues.dlang.org/show_bug.cgi?id=22764 I've fixed that for the next release.
Mar 19
prev sibling parent Rainer Schuetze <r.sagitario gmx.de> writes:
On 18/03/2022 05:52, Rinzwind wrote:
 On Wednesday, 2 March 2022 at 21:50:43 UTC, Rainer Schuetze wrote:
 Maybe there is a problem with the path using the short name "Progra~2" 
 instead of "Program Files (x86)". If you change that you might have to 
 force an update of the extension cache by modifying "c:\Program 
 Files\Microsoft Visual 
 Studio\2022\Preview\Common7\IDE\Extensions\extensions.configurationchanged". 
I finally tried it, and it worked! Just as test I changed it back to Progra~2, and it still workded. Maybe just the modified date change of extensions.configurationchanged was needed? Anyway, thanks. Hopefully something that can be 'fixed' in the installer.
The installer updates the date of this file. Maybe the translation of Progra~2 changed afterwards because it was such a fresh installation of Windows? I doubt that but who knows...
 Just as reference, the VS community path is C:\Program Files\Microsoft 
 Visual Studio\2022\Community\Common7\IDE\Extensions
Yeah, I meant mine just as an example. The actual path is evaluated from installation entries in the registry.
Mar 19