Re: Visual D 0.50.0 released
On Wednesday, 4 September 2019 at 18:27:14 UTC, Manu wrote: On Wed, Jun 26, 2019 at 1:30 AM a11e99z via Digitalmars-d-announce wrote: On Wednesday, 26 June 2019 at 02:35:53 UTC, Bart wrote: > On Tuesday, 25 June 2019 at 19:47:40 UTC, Rainer Schuetze Your problems are easy to resolve. BuildTools has some weird paths... but you're running VS; why are you using the separate build tools distribution when you have VS installed? This is thoroughly non-standard and weird. Just install the proper C++ tools? The path issue that lead to optlink rather than MS link should be trivial to resolve, then you will not have linking problems. yep, I fixed it already, its ok now - install internal build tools instead separate package. - reset VD settings (such issue was fixed by Schuetze). - fix PATH vars.
Re: Visual D 0.50.0 released
On Wed, Jun 26, 2019 at 1:30 AM a11e99z via Digitalmars-d-announce wrote: > > On Wednesday, 26 June 2019 at 02:35:53 UTC, Bart wrote: > > On Tuesday, 25 June 2019 at 19:47:40 UTC, Rainer Schuetze wrote: > > Before I told about problems with VD on my laptop. > Most of time I use desktop with VS2019 and VD0.49.2 - its working. > I dont have a few days for "debugging" my installation for now so > I put my laptop in case and I am afraid install new VD to > desktop. I will deeply plunge to this jungle at July. > I filled some issues/enhancement to bugtracker yesterday. > In any case thanks for VD, I like it and I need it. Your problems are easy to resolve. BuildTools has some weird paths... but you're running VS; why are you using the separate build tools distribution when you have VS installed? This is thoroughly non-standard and weird. Just install the proper C++ tools? The path issue that lead to optlink rather than MS link should be trivial to resolve, then you will not have linking problems.
Re: Visual D 0.50.0 released
On Tuesday, 3 September 2019 at 07:06:03 UTC, Rainer Schuetze wrote: I just released a bug fix version 0.50.1 with a few enhancements: - fixes some integration issues with VS 2019 16.2 - mago: improve function call in watch window - better version highlighting for files not in project Full list of changes as usual here: https://rainers.github.io/visuald/visuald/VersionHistory.html Thanks Rainer :)
Re: Visual D 0.50.0 released
On Tue, Sep 3, 2019 at 12:10 AM Rainer Schuetze via Digitalmars-d-announce wrote: > > > > On 23/06/2019 19:58, Rainer Schuetze wrote: > > Hi, > > > > today a new version of Visual D has been released. Its main new features are > > > > - additional installer available that includes DMD and LDC > > > > - now checks for updates for Visual D, DMD and LDC, assisted download > > and install > > > > - debugger improvements: better support for dynamic type of classes, > > show exception messages, conditional breakpoints > > > > - highlight references to symbol at caret (experimental) > > > > See https://rainers.github.io/visuald/visuald/VersionHistory.html for > > the complete list of changes > > > > Visual D is a Visual Studio extension that adds D language support to > > VS2008-2019. It is written in D, its source code can be found on github: > > https://github.com/D-Programming-Language/visuald, pull requests welcome. > > > > The installers can be found at > > http://rainers.github.io/visuald/visuald/StartPage.html > > > > Visual D is now also available in the Visual Studio Marketplace: > > https://marketplace.visualstudio.com/items?itemName=RainerSchuetze.visuald > > > > Happy coding, > > Rainer > > > > I just released a bug fix version 0.50.1 with a few enhancements: > > - fixes some integration issues with VS 2019 16.2 > - mago: improve function call in watch window > - better version highlighting for files not in project > > Full list of changes as usual here: > https://rainers.github.io/visuald/visuald/VersionHistory.html Thanks again Rainer!
Re: Visual D 0.50.0 released
On 23/06/2019 19:58, Rainer Schuetze wrote: > Hi, > > today a new version of Visual D has been released. Its main new features are > > - additional installer available that includes DMD and LDC > > - now checks for updates for Visual D, DMD and LDC, assisted download > and install > > - debugger improvements: better support for dynamic type of classes, > show exception messages, conditional breakpoints > > - highlight references to symbol at caret (experimental) > > See https://rainers.github.io/visuald/visuald/VersionHistory.html for > the complete list of changes > > Visual D is a Visual Studio extension that adds D language support to > VS2008-2019. It is written in D, its source code can be found on github: > https://github.com/D-Programming-Language/visuald, pull requests welcome. > > The installers can be found at > http://rainers.github.io/visuald/visuald/StartPage.html > > Visual D is now also available in the Visual Studio Marketplace: > https://marketplace.visualstudio.com/items?itemName=RainerSchuetze.visuald > > Happy coding, > Rainer > I just released a bug fix version 0.50.1 with a few enhancements: - fixes some integration issues with VS 2019 16.2 - mago: improve function call in watch window - better version highlighting for files not in project Full list of changes as usual here: https://rainers.github.io/visuald/visuald/VersionHistory.html
Re: Visual D 0.50.0 released
On 26/06/2019 04:35, Bart wrote: > On Tuesday, 25 June 2019 at 19:47:40 UTC, Rainer Schuetze wrote: >> >> >> On 25/06/2019 15:53, a11e99z wrote: >>> On Tuesday, 25 June 2019 at 12:24:03 UTC, a11e99z wrote: On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: > today a new version of Visual D has been released. and now I have some issues with new VD 0.50: and now main troubles: I cant build any D project any more from VS. - compiling as "LDC x64": again used OPTLINK. why? LDC has own lld-link. >>> >>> I deinstalled Build Tools, installed VC++ from VS-Installer to Community >>> folder as 99% does. >>> same problems. >>> deinstalled VD0.50, install it again, all settings restored from olds (I >>> want to do clean installation) >>> deinstalled VD0.50, installed 0.49.2, same problems and same old >>> settings. >>> pic of LDC x64 w OPTLINK https://pasteboard.co/Il3uc0E.png >>> well, now i can not compile D projects at all with any version of VD. >> >> "Image not found" for the link. >> >> I suspect that there is something wrong with the order of folders in >> the PATH environment variable. You can check the generated batch >> (*.cmd) in the output folder. > > > Maybe what might help is for VD to output all relevant information such > as the locations of the compiler, linker, library imports, etc... all in > an easily one per line file. > > I tend to have trouble parsing the logs and such because the information > is not easily readable unless one knows exactly what they are looking > for. Specially with large projects. > > This may not help with the compiler and linker itself unless you were to > monitor the file system for changes(like process monitor) and then > report what it is using but that would be a bit of work. > > On my comp LDC does not work and I just get a crash but I don't know > why. I simply don't use LDC for now. > > For example, if you could override all the file commends in VD (e.g., if > you use std.file you could hijack it) and then output all open files to > a log along with VD's __FILE__ and __LINE__ info to get the source where > they are being used at. Would also require doing it with the shell but > you basically already do it... just maybe pretty print the info so it is > more readable. E.g., > > VD Options > --- > > Paths: > Libraries: C:\Lib > Imports: C:\Imports > Compiler: C:\dmd\bin > > Import libraries: > C:\libraries\ > D:\foxtrot\tango.m > ... > Command line options: > -m64 > -g > -IC:\libraries\ > ... > ... > > Opened Files: > C:\project\happy.m > D:\projects\dance.m > > > The point is to be as verbose as possible to provide as much contextual > information for figuring out problems. > > > > or whatever... > > > If you setup the framework you could slowly convert everything over time > by simply logging stuff and as you come across old usage you can update > it. Maybe get the most relevant first and then the rest of the stuff > could follow. > > There are dll injection libraries that can be used to inject in to a > process to monitor file system access... could be used on the compiler > and linker and all the files it uses could be stored(the log file would > be very large but it would be helpful). > > You can already find all this information in the output/intermediate folder, e.g. the dep/lnkdep files are from monitoring compiler and linker, respectively. The logs are not as verbose as the ones generated by msbuild, but that makes them easier to digest.
Re: Visual D 0.50.0 released
On Wednesday, 26 June 2019 at 02:35:53 UTC, Bart wrote: On Tuesday, 25 June 2019 at 19:47:40 UTC, Rainer Schuetze wrote: Before I told about problems with VD on my laptop. Most of time I use desktop with VS2019 and VD0.49.2 - its working. I dont have a few days for "debugging" my installation for now so I put my laptop in case and I am afraid install new VD to desktop. I will deeply plunge to this jungle at July. I filled some issues/enhancement to bugtracker yesterday. In any case thanks for VD, I like it and I need it.
Re: Visual D 0.50.0 released
On Wednesday, 26 June 2019 at 08:28:13 UTC, a11e99z wrote: On Wednesday, 26 June 2019 at 02:35:53 UTC, Bart wrote: On Tuesday, 25 June 2019 at 19:47:40 UTC, Rainer Schuetze wrote: Before I told about problems with VD on my laptop. Most of time I use desktop with VS2019 and VD0.49.2 - its working. I dont have a few days for "debugging" my installation for now so I put my laptop in case and I am afraid install new VD to desktop. I will deeply plunge to this jungle at July. I filled some issues/enhancement to bugtracker yesterday. In any case thanks for VD, I like it and I need it. oops! to Rainer Schuetze :)
Re: Visual D 0.50.0 released
On Tuesday, 25 June 2019 at 19:47:40 UTC, Rainer Schuetze wrote: On 25/06/2019 15:53, a11e99z wrote: On Tuesday, 25 June 2019 at 12:24:03 UTC, a11e99z wrote: On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: today a new version of Visual D has been released. and now I have some issues with new VD 0.50: and now main troubles: I cant build any D project any more from VS. - compiling as "LDC x64": again used OPTLINK. why? LDC has own lld-link. I deinstalled Build Tools, installed VC++ from VS-Installer to Community folder as 99% does. same problems. deinstalled VD0.50, install it again, all settings restored from olds (I want to do clean installation) deinstalled VD0.50, installed 0.49.2, same problems and same old settings. pic of LDC x64 w OPTLINK https://pasteboard.co/Il3uc0E.png well, now i can not compile D projects at all with any version of VD. "Image not found" for the link. I suspect that there is something wrong with the order of folders in the PATH environment variable. You can check the generated batch (*.cmd) in the output folder. Maybe what might help is for VD to output all relevant information such as the locations of the compiler, linker, library imports, etc... all in an easily one per line file. I tend to have trouble parsing the logs and such because the information is not easily readable unless one knows exactly what they are looking for. Specially with large projects. This may not help with the compiler and linker itself unless you were to monitor the file system for changes(like process monitor) and then report what it is using but that would be a bit of work. On my comp LDC does not work and I just get a crash but I don't know why. I simply don't use LDC for now. For example, if you could override all the file commends in VD (e.g., if you use std.file you could hijack it) and then output all open files to a log along with VD's __FILE__ and __LINE__ info to get the source where they are being used at. Would also require doing it with the shell but you basically already do it... just maybe pretty print the info so it is more readable. E.g., VD Options --- Paths: Libraries: C:\Lib Imports: C:\Imports Compiler: C:\dmd\bin Import libraries: C:\libraries\ D:\foxtrot\tango.m ... Command line options: -m64 -g -IC:\libraries\ ... ... Opened Files: C:\project\happy.m D:\projects\dance.m The point is to be as verbose as possible to provide as much contextual information for figuring out problems. or whatever... If you setup the framework you could slowly convert everything over time by simply logging stuff and as you come across old usage you can update it. Maybe get the most relevant first and then the rest of the stuff could follow. There are dll injection libraries that can be used to inject in to a process to monitor file system access... could be used on the compiler and linker and all the files it uses could be stored(the log file would be very large but it would be helpful).
Re: Visual D 0.50.0 released
On 25/06/2019 15:53, a11e99z wrote: > On Tuesday, 25 June 2019 at 12:24:03 UTC, a11e99z wrote: >> On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: >>> today a new version of Visual D has been released. >> >> and now I have some issues with new VD 0.50: >> and now main troubles: I cant build any D project any more from VS. >> - compiling as "LDC x64": again used OPTLINK. why? LDC has own lld-link. > > I deinstalled Build Tools, installed VC++ from VS-Installer to Community > folder as 99% does. > same problems. > deinstalled VD0.50, install it again, all settings restored from olds (I > want to do clean installation) > deinstalled VD0.50, installed 0.49.2, same problems and same old settings. > pic of LDC x64 w OPTLINK https://pasteboard.co/Il3uc0E.png > well, now i can not compile D projects at all with any version of VD. "Image not found" for the link. I suspect that there is something wrong with the order of folders in the PATH environment variable. You can check the generated batch (*.cmd) in the output folder.
Re: Visual D 0.50.0 released
On 25/06/2019 15:38, a11e99z wrote: > On Tuesday, 25 June 2019 at 12:24:03 UTC, a11e99z wrote: > and should exists total uninstallation with removing ALL setting and > folders. > probably its good for updating to new version but should exist > possibility to make clean new installation with removing all old settings. > for now uninstall & new install restore all old settings. dunno where it > stores. I remove folder in program files, appdata\roaming and > some keys from registry but it doesnt helps. probably I missed something. The problem is that Visual Studio keeps the settings in a private registry that is only mounted when you run VS. This private registry is not accessible by the installer. Adding a "Reset all settings to default" sounds like a good idea, though. I'll see if it can be added in the next release. You could try running "devenv /ResetSettings" for a global reset.
Re: Visual D 0.50.0 released
On 25/06/2019 14:24, a11e99z wrote: > On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: >> today a new version of Visual D has been released. > > before I used VS2017 with VD 0.49. was ok. then I uninstalled it both. > then installed VS2019 (.NET only), installed VD 0.50, installed Build > Tools for 2019 (C++), installed DMD & LDC as unpack distros to some > folder and added PATH to their bin dirs That's where your troubles start. > - CLI is working now. > > and now I have some issues with new VD 0.50: > - (weird but can live with it) mode "betterC" looks in settings like > "remove some runtime info and helper functions" That's the description given by dmd in the CLI help. - not clear too much coz > I thoughts that this option decrease compiled EXE size. please give to > it more clear text like "betterC" I can add betterC/worseD to the description if that helps. The VC++ integration already calls the option "Better C". > - (in concert) Visual D Settings\Updates\Base directory > for what needed that directory? for D projects? (oh, we are in tab > "Updates") then what I should point here DMD directory (that can be in > ProgramFiles if i used DMD installer)? LDC directory (that can be in any > other user dir)? or I should point just "C:\"? weird name and option. There is not a lot of space for verbose descriptions in this dialog, the installer explains it a bit less terse. But I'll try to cover it in a line above or below the option. > - Path to VS Linker exists only in DMD Directories tab for x64. What for > GDC and LDC in case I dont install DMD at all? GDC uses ld and LDC the Microsoft linker, nothing from the dmd installation. > > and now main troubles: I cant build any D project any more from VS. > - compiling as "DMD x64": OPTLINK can not build EXE coz VD gives to it > probably weird option. OPTLINK points to "/OUT:.." option and I dont > used any nonASCII chars. dunno whats wrong. DMD still can build EXE from > CLI. That's probably because link.exe cannot be found in the standard locations (Build tools not supported, as probably C++ integration doesn't do aswell). Then PATH is searched, but the dmd folder contains some badly named executables, link.exe being the worst. > - compiling as "LDC x64": again used OPTLINK. why? LDC has own lld-link. > - ok. remove DMD from VS options and from PATH var. LDC tried to use > link.exe. why? it has own lld-link again. see next point. lld-link is pretty new, and is unlikely to work well enough in combination with C++. For example, Microsoft keeps adding new debug information records. > - coz I installed Build Tools(C++) separate form VS my folder to libs > and tools located at "C:\Program Files (x86)\Microsoft Visual > Studio\2019\BuildTools" not in the "..\Community". Probably its MS > problem but I have what I have. so using VCINSTALLDIR is not good option > for all cases. Try to check folder BuildTools too and VCINSTALLDIR for > lastest build tools and libs. I can point VD settings manually but VD > can do it automatically - just to check two folders instead one. Sorry, can't support all possible combinations of installations. I think it's not too bad if you can still configure the odd cases.
Re: Visual D 0.50.0 released
On 25/06/2019 08:49, Bart wrote: > On Tuesday, 25 June 2019 at 05:32:37 UTC, Rainer Schuetze wrote: >> >> >> On 24/06/2019 21:58, Bart wrote: >>> On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: Hi, today a new version of Visual D has been released. Its main new features are [...] >>> >>> >>> Did you break showing interfaces in the debug window? None of my >>> interfaces are able to be expanded as the objects they are after >>> updating. Was working fine right before. >> >> I think the bug has been in there since beta1, but doesn't always show >> up (never in a debug build). The class name is cached for a >> vtbl-pointer, but that cached value can be overwritten if there are >> uninitialized references evaluated afterwards. Fixed for the next >> release. > > Never in a debug build? I'm using debug build ;/ Before sometimes it > woudln't show up but after the update no interface was expandable(well, > at least when I noticed it I could not expand any) I was talking about the debug build of the debugger extension.
Re: Visual D 0.50.0 released
On Tuesday, 25 June 2019 at 12:24:03 UTC, a11e99z wrote: On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: today a new version of Visual D has been released. and now I have some issues with new VD 0.50: and now main troubles: I cant build any D project any more from VS. - compiling as "LDC x64": again used OPTLINK. why? LDC has own lld-link. I deinstalled Build Tools, installed VC++ from VS-Installer to Community folder as 99% does. same problems. deinstalled VD0.50, install it again, all settings restored from olds (I want to do clean installation) deinstalled VD0.50, installed 0.49.2, same problems and same old settings. pic of LDC x64 w OPTLINK https://pasteboard.co/Il3uc0E.png well, now i can not compile D projects at all with any version of VD.
Re: Visual D 0.50.0 released
On Tuesday, 25 June 2019 at 12:24:03 UTC, a11e99z wrote: and should exists total uninstallation with removing ALL setting and folders. probably its good for updating to new version but should exist possibility to make clean new installation with removing all old settings. for now uninstall & new install restore all old settings. dunno where it stores. I remove folder in program files, user>appdata\roaming and some keys from registry but it doesnt helps. probably I missed something.
Re: Visual D 0.50.0 released
On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: today a new version of Visual D has been released. before I used VS2017 with VD 0.49. was ok. then I uninstalled it both. then installed VS2019 (.NET only), installed VD 0.50, installed Build Tools for 2019 (C++), installed DMD & LDC as unpack distros to some folder and added PATH to their bin dirs - CLI is working now. and now I have some issues with new VD 0.50: - (weird but can live with it) mode "betterC" looks in settings like "remove some runtime info and helper functions" - not clear too much coz I thoughts that this option decrease compiled EXE size. please give to it more clear text like "betterC" - (in concert) Visual D Settings\Updates\Base directory for what needed that directory? for D projects? (oh, we are in tab "Updates") then what I should point here DMD directory (that can be in ProgramFiles if i used DMD installer)? LDC directory (that can be in any other user dir)? or I should point just "C:\"? weird name and option. - Path to VS Linker exists only in DMD Directories tab for x64. What for GDC and LDC in case I dont install DMD at all? and now main troubles: I cant build any D project any more from VS. - compiling as "DMD x64": OPTLINK can not build EXE coz VD gives to it probably weird option. OPTLINK points to "/OUT:.." option and I dont used any nonASCII chars. dunno whats wrong. DMD still can build EXE from CLI. - compiling as "LDC x64": again used OPTLINK. why? LDC has own lld-link. - ok. remove DMD from VS options and from PATH var. LDC tried to use link.exe. why? it has own lld-link again. see next point. - coz I installed Build Tools(C++) separate form VS my folder to libs and tools located at "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools" not in the "..\Community". Probably its MS problem but I have what I have. so using VCINSTALLDIR is not good option for all cases. Try to check folder BuildTools too and VCINSTALLDIR for lastest build tools and libs. I can point VD settings manually but VD can do it automatically - just to check two folders instead one.
Re: Visual D 0.50.0 released
On Tuesday, 25 June 2019 at 05:32:37 UTC, Rainer Schuetze wrote: On 24/06/2019 21:58, Bart wrote: On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: Hi, today a new version of Visual D has been released. Its main new features are [...] Did you break showing interfaces in the debug window? None of my interfaces are able to be expanded as the objects they are after updating. Was working fine right before. I think the bug has been in there since beta1, but doesn't always show up (never in a debug build). The class name is cached for a vtbl-pointer, but that cached value can be overwritten if there are uninitialized references evaluated afterwards. Fixed for the next release. Never in a debug build? I'm using debug build ;/ Before sometimes it woudln't show up but after the update no interface was expandable(well, at least when I noticed it I could not expand any)
Re: Visual D 0.50.0 released
On 24/06/2019 21:58, Bart wrote: > On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: >> Hi, >> >> today a new version of Visual D has been released. Its main new >> features are >> >> [...] > > > Did you break showing interfaces in the debug window? None of my > interfaces are able to be expanded as the objects they are after > updating. Was working fine right before. I think the bug has been in there since beta1, but doesn't always show up (never in a debug build). The class name is cached for a vtbl-pointer, but that cached value can be overwritten if there are uninitialized references evaluated afterwards. Fixed for the next release.
Re: Visual D 0.50.0 released
On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: Hi, today a new version of Visual D has been released. Its main new features are [...] Did you break showing interfaces in the debug window? None of my interfaces are able to be expanded as the objects they are after updating. Was working fine right before.
Re: Visual D 0.50.0 released
Thanks Rainer!
Re: Visual D 0.50.0 released
On Monday, 24 June 2019 at 05:25:32 UTC, Rainer Schuetze wrote: On 24/06/2019 00:25, Greatsam4sure wrote: Visual D works for VS 2008 up to VS 2019. The new project dialog in VS 2019 makes it hard to discover the new projects because the categories are hardcoded and cannot be extended. You have to scroll down the list of "All" project templates. Once used the project types appear in the recently used projects list. Thanks, I just installed the package with DMD and LDC but my old version of DMD was not replaced. Is there a reason for this? I now have two versions of DMD on my laptop now-dmd 2.086 and 2.086.1 It doesn't (yet) delete old versions of the compilers because of I didn't want to break existing setups. In case something fails to compile for your code with the new compiler release, you can easily go back to the previous one. The compiler update also doesn't change your environment as the DMD installer (optionally) does, so you have to set PATH yourself. It just works out of the box. It is ok for me. I am really happy with the experience, no error thrown at all. It will be nice to have an integrated terminal in the visual studio just as in vs code. Thanks for all the great works
Re: Visual D 0.50.0 released
On 24/06/2019 00:25, Greatsam4sure wrote: >> >> Visual D works for VS 2008 up to VS 2019. The new project dialog in VS >> 2019 makes it hard to discover the new projects because the categories >> are hardcoded and cannot be extended. You have to scroll down the list >> of "All" project templates. Once used the project types appear in the >> recently used projects list. > > > Thanks, I just installed the package with DMD and LDC but my old version > of DMD was not replaced. Is there a reason for this? I now have two > versions of DMD on my laptop now-dmd 2.086 and 2.086.1 It doesn't (yet) delete old versions of the compilers because I didn't want to break existing setups. In case something fails to compile for your code with the new compiler release, you can easily go back to the previous one. The compiler update also doesn't change your environment as the DMD installer (optionally) does, so you have to set PATH yourself.
Re: Visual D 0.50.0 released
On Sunday, 23 June 2019 at 21:49:49 UTC, Rainer Schuetze wrote: On 23/06/2019 21:06, Greatsam4sure wrote: On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: [...] Thanks to all, who make this possible. Which version of dmd and ldc is bundle with visual-D 0.50 and which version of visual studio 2019 does it support. dmd 2.086.1 and ldc 1.16.0 are bundled. These are mentioned in the filename of the download, but that isn't obvious on the front page. I guess this should be shown there, too. The latest version studio 2019 I have does not support previous version of visual D. I could not create a Dlang project with it Visual D works for VS 2008 up to VS 2019. The new project dialog in VS 2019 makes it hard to discover the new projects because the categories are hardcoded and cannot be extended. You have to scroll down the list of "All" project templates. Once used the project types appear in the recently used projects list. Thanks, I just installed the package with DMD and LDC but my old version of DMD was not replaced. Is there a reason for this? I now have two versions of DMD on my laptop now-dmd 2.086 and 2.086.1
Re: Visual D 0.50.0 released
On 23/06/2019 21:06, Greatsam4sure wrote: > On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: >> Hi, >> >> today a new version of Visual D has been released. Its main new >> features are >> >> - additional installer available that includes DMD and LDC >> >> - now checks for updates for Visual D, DMD and LDC, assisted download >> and install >> >> - debugger improvements: better support for dynamic type of classes, >> show exception messages, conditional breakpoints >> >> - highlight references to symbol at caret (experimental) >> >> See https://rainers.github.io/visuald/visuald/VersionHistory.html for >> the complete list of changes >> >> Visual D is a Visual Studio extension that adds D language support to >> VS2008-2019. It is written in D, its source code can be found on >> github: https://github.com/D-Programming-Language/visuald, pull >> requests welcome. >> >> The installers can be found at >> http://rainers.github.io/visuald/visuald/StartPage.html >> >> Visual D is now also available in the Visual Studio Marketplace: >> https://marketplace.visualstudio.com/items?itemName=RainerSchuetze.visuald >> >> >> Happy coding, >> Rainer > > > Thanks to all, who make this possible. > > Which version of dmd and ldc is bundle with visual-D 0.50 and which > version of visual studio 2019 does it support. dmd 2.086.1 and ldc 1.16.0 are bundled. These are mentioned in the filename of the download, but that isn't obvious on the front page. I guess this should be shown there, too. > The latest version studio > 2019 I have does not support previous version of visual D. I could not > create a Dlang project with it > Visual D works for VS 2008 up to VS 2019. The new project dialog in VS 2019 makes it hard to discover the new projects because the categories are hardcoded and cannot be extended. You have to scroll down the list of "All" project templates. Once used the project types appear in the recently used projects list.
Re: Visual D 0.50.0 released
On Sunday, 23 June 2019 at 17:58:27 UTC, Rainer Schuetze wrote: Hi, today a new version of Visual D has been released. Its main new features are - additional installer available that includes DMD and LDC - now checks for updates for Visual D, DMD and LDC, assisted download and install - debugger improvements: better support for dynamic type of classes, show exception messages, conditional breakpoints - highlight references to symbol at caret (experimental) See https://rainers.github.io/visuald/visuald/VersionHistory.html for the complete list of changes Visual D is a Visual Studio extension that adds D language support to VS2008-2019. It is written in D, its source code can be found on github: https://github.com/D-Programming-Language/visuald, pull requests welcome. The installers can be found at http://rainers.github.io/visuald/visuald/StartPage.html Visual D is now also available in the Visual Studio Marketplace: https://marketplace.visualstudio.com/items?itemName=RainerSchuetze.visuald Happy coding, Rainer Thanks to all, who make this possible. Which version of dmd and ldc is bundle with visual-D 0.50 and which version of visual studio 2019 does it support. The latest version studio 2019 I have does not support previous version of visual D. I could not create a Dlang project with it
Visual D 0.50.0 released
Hi, today a new version of Visual D has been released. Its main new features are - additional installer available that includes DMD and LDC - now checks for updates for Visual D, DMD and LDC, assisted download and install - debugger improvements: better support for dynamic type of classes, show exception messages, conditional breakpoints - highlight references to symbol at caret (experimental) See https://rainers.github.io/visuald/visuald/VersionHistory.html for the complete list of changes Visual D is a Visual Studio extension that adds D language support to VS2008-2019. It is written in D, its source code can be found on github: https://github.com/D-Programming-Language/visuald, pull requests welcome. The installers can be found at http://rainers.github.io/visuald/visuald/StartPage.html Visual D is now also available in the Visual Studio Marketplace: https://marketplace.visualstudio.com/items?itemName=RainerSchuetze.visuald Happy coding, Rainer
