www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.ide - Visual D 0.3.26 released

reply Rainer Schuetze <r.sagitario gmx.de> writes:
Hi,

I'd like to announce the release of a new version of Visual D:

2011-08-25 Version 0.3.26

* fixed regression in last version: single file compilation did not 
build any d files
* single file compilation: avoid relinking every time
* separate compile and link: no longer trashes dependencies in link step
* goto definition, search symbol: now line number adjusted according to 
changes since last successful build
* fix: resource files in sub folders would not build because the same 
folders were expected in the intermediate directory
* global settings: split page into directories/settings pages to make 
option "Show build time" accessible
* global settings: added option to disable sorting projects
* parser now accepts "do {} while(condition)" without trailing ';'
* project options macro $(PROJECTNAME) now uses the name in the solution 
instead of the project file name
* fixed bad indentation of first contract
* fixed colorization of first token after debug condition without arguments
* "is" now always colored as operator, not as keyword
* updated to build with dmd 2.055beta

Visual D provides seamless integration of the D programming language 
into Visual Studio. It can be downloaded here: 
http://www.dsource.org/projects/visuald/

Best,
Rainer
Aug 25 2011
next sibling parent reply =?ISO-8859-1?Q?Alex_R=F8nne_Petersen?= <xtzgzorex gmail.com> writes:
On 25-08-2011 09:28, Rainer Schuetze wrote:
 Hi,

 I'd like to announce the release of a new version of Visual D:

 2011-08-25 Version 0.3.26

 * fixed regression in last version: single file compilation did not
 build any d files
 * single file compilation: avoid relinking every time
 * separate compile and link: no longer trashes dependencies in link step
 * goto definition, search symbol: now line number adjusted according to
 changes since last successful build
 * fix: resource files in sub folders would not build because the same
 folders were expected in the intermediate directory
 * global settings: split page into directories/settings pages to make
 option "Show build time" accessible
 * global settings: added option to disable sorting projects
 * parser now accepts "do {} while(condition)" without trailing ';'
 * project options macro $(PROJECTNAME) now uses the name in the solution
 instead of the project file name
 * fixed bad indentation of first contract
 * fixed colorization of first token after debug condition without arguments
 * "is" now always colored as operator, not as keyword
 * updated to build with dmd 2.055beta

 Visual D provides seamless integration of the D programming language
 into Visual Studio. It can be downloaded here:
 http://www.dsource.org/projects/visuald/

 Best,
 Rainer

Awesome news! One question:
 * fixed bad indentation of first contract

What exactly does this fix? Can you give an example? - Alex
Aug 25 2011
parent reply Rainer Schuetze <r.sagitario gmx.de> writes:
On 25.08.2011 15:34, Alex Rønne Petersen wrote:
 On 25-08-2011 09:28, Rainer Schuetze wrote:
 Hi,

 I'd like to announce the release of a new version of Visual D:

 2011-08-25 Version 0.3.26
[...]

One question:
 * fixed bad indentation of first contract

What exactly does this fix? Can you give an example?

reindenting a function with contracts used to produce something like this: int foo(int x) in { assert(x > 0); } body { return -x; } Now, the in contract is aligned with the function declaration and the body: int foo(int x) in { assert(x > 0); } body { return -x; }
Aug 26 2011
parent reply =?ISO-8859-1?Q?Alex_R=F8nne_Petersen?= <xtzgzorex gmail.com> writes:
On 26-08-2011 09:20, Rainer Schuetze wrote:
 On 25.08.2011 15:34, Alex Rønne Petersen wrote:
 On 25-08-2011 09:28, Rainer Schuetze wrote:
 Hi,

 I'd like to announce the release of a new version of Visual D:

 2011-08-25 Version 0.3.26
 [...]

One question:
 * fixed bad indentation of first contract

What exactly does this fix? Can you give an example?

reindenting a function with contracts used to produce something like this: int foo(int x) in { assert(x > 0); } body { return -x; } Now, the in contract is aligned with the function declaration and the body: int foo(int x) in { assert(x > 0); } body { return -x; }

Oh, great! It seems that it still happens while you type out the function, though. Can anything be done about that? - Alex
Aug 26 2011
parent reply Rainer Schuetze <r.sagitario gmx.de> writes:
On 26.08.2011 09:58, Alex Rønne Petersen wrote:
 On 26-08-2011 09:20, Rainer Schuetze wrote:
 On 25.08.2011 15:34, Alex Rønne Petersen wrote:
 On 25-08-2011 09:28, Rainer Schuetze wrote:
 Hi,

 I'd like to announce the release of a new version of Visual D:

 2011-08-25 Version 0.3.26
 [...]

One question:
 * fixed bad indentation of first contract

What exactly does this fix? Can you give an example?

reindenting a function with contracts used to produce something like this: int foo(int x) in { assert(x > 0); } body { return -x; } Now, the in contract is aligned with the function declaration and the body: int foo(int x) in { assert(x > 0); } body { return -x; }

Oh, great! It seems that it still happens while you type out the function, though. Can anything be done about that? - Alex

I didn't think of that. Currently, the line is reindented if you type '{' or '}' as the first non-space on the line. This needs to be extended to "in", "out" and "body" without getting annoying. I'll see what can be done.
Aug 26 2011
parent =?ISO-8859-1?Q?Alex_R=F8nne_Petersen?= <xtzgzorex gmail.com> writes:
On 26-08-2011 17:05, Rainer Schuetze wrote:
 On 26.08.2011 09:58, Alex Rønne Petersen wrote:
 On 26-08-2011 09:20, Rainer Schuetze wrote:
 On 25.08.2011 15:34, Alex Rønne Petersen wrote:
 On 25-08-2011 09:28, Rainer Schuetze wrote:
 Hi,

 I'd like to announce the release of a new version of Visual D:

 2011-08-25 Version 0.3.26
 [...]

One question:
 * fixed bad indentation of first contract

What exactly does this fix? Can you give an example?

reindenting a function with contracts used to produce something like this: int foo(int x) in { assert(x > 0); } body { return -x; } Now, the in contract is aligned with the function declaration and the body: int foo(int x) in { assert(x > 0); } body { return -x; }

Oh, great! It seems that it still happens while you type out the function, though. Can anything be done about that? - Alex

I didn't think of that. Currently, the line is reindented if you type '{' or '}' as the first non-space on the line. This needs to be extended to "in", "out" and "body" without getting annoying. I'll see what can be done.

Great, thanks! - Alex
Aug 26 2011
prev sibling next sibling parent reply Johannes Totz <johannes jo-t.de> writes:
On 25/08/2011 08:28, Rainer Schuetze wrote:
 Hi,
 
 I'd like to announce the release of a new version of Visual D:
 
 2011-08-25 Version 0.3.26
 
 * fixed regression in last version: single file compilation did not
 build any d files
 * single file compilation: avoid relinking every time
 * separate compile and link: no longer trashes dependencies in link step
 * goto definition, search symbol: now line number adjusted according to
 changes since last successful build
 * fix: resource files in sub folders would not build because the same
 folders were expected in the intermediate directory
 * global settings: split page into directories/settings pages to make
 option "Show build time" accessible
 * global settings: added option to disable sorting projects
 * parser now accepts "do {} while(condition)" without trailing ';'
 * project options macro $(PROJECTNAME) now uses the name in the solution
 instead of the project file name
 * fixed bad indentation of first contract
 * fixed colorization of first token after debug condition without arguments
 * "is" now always colored as operator, not as keyword
 * updated to build with dmd 2.055beta
 
 Visual D provides seamless integration of the D programming language
 into Visual Studio. It can be downloaded here:
 http://www.dsource.org/projects/visuald/

I tried it on Visual Studio 2008 but after installation, VS simply hangs at startup. Splash screen is showing but nothing else happening. Task manager shows slowly increasing memory usage. After 15 mins I killed it. I tried it a few times but ultimately had to uninstall it and now everything is back to normal. Ideas on how to figure out what might be wrong?
Aug 26 2011
parent Rainer Schuetze <r.sagitario gmx.de> writes:
On 26.08.2011 15:07, Johannes Totz wrote:
 On 25/08/2011 08:28, Rainer Schuetze wrote:
 Hi,

 I'd like to announce the release of a new version of Visual D:

 2011-08-25 Version 0.3.26

 * fixed regression in last version: single file compilation did not
 build any d files
 * single file compilation: avoid relinking every time
 * separate compile and link: no longer trashes dependencies in link step
 * goto definition, search symbol: now line number adjusted according to
 changes since last successful build
 * fix: resource files in sub folders would not build because the same
 folders were expected in the intermediate directory
 * global settings: split page into directories/settings pages to make
 option "Show build time" accessible
 * global settings: added option to disable sorting projects
 * parser now accepts "do {} while(condition)" without trailing ';'
 * project options macro $(PROJECTNAME) now uses the name in the solution
 instead of the project file name
 * fixed bad indentation of first contract
 * fixed colorization of first token after debug condition without arguments
 * "is" now always colored as operator, not as keyword
 * updated to build with dmd 2.055beta

 Visual D provides seamless integration of the D programming language
 into Visual Studio. It can be downloaded here:
 http://www.dsource.org/projects/visuald/

I tried it on Visual Studio 2008 but after installation, VS simply hangs at startup. Splash screen is showing but nothing else happening. Task manager shows slowly increasing memory usage. After 15 mins I killed it. I tried it a few times but ultimately had to uninstall it and now everything is back to normal. Ideas on how to figure out what might be wrong?

What OS are you working on? A process dump might help to figure out what's going on. You can use procdump from here: http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx to create one while VS is frozen. Please send it to me or make it available somewhere for download.
Aug 26 2011
prev sibling next sibling parent reply =?ISO-8859-1?Q?Alex_R=F8nne_Petersen?= <xtzgzorex gmail.com> writes:
On 25-08-2011 09:28, Rainer Schuetze wrote:
 Hi,

 I'd like to announce the release of a new version of Visual D:

 2011-08-25 Version 0.3.26

 * fixed regression in last version: single file compilation did not
 build any d files
 * single file compilation: avoid relinking every time
 * separate compile and link: no longer trashes dependencies in link step
 * goto definition, search symbol: now line number adjusted according to
 changes since last successful build
 * fix: resource files in sub folders would not build because the same
 folders were expected in the intermediate directory
 * global settings: split page into directories/settings pages to make
 option "Show build time" accessible
 * global settings: added option to disable sorting projects
 * parser now accepts "do {} while(condition)" without trailing ';'
 * project options macro $(PROJECTNAME) now uses the name in the solution
 instead of the project file name
 * fixed bad indentation of first contract
 * fixed colorization of first token after debug condition without arguments
 * "is" now always colored as operator, not as keyword
 * updated to build with dmd 2.055beta

 Visual D provides seamless integration of the D programming language
 into Visual Studio. It can be downloaded here:
 http://www.dsource.org/projects/visuald/

 Best,
 Rainer

Hi, Does anyone know whether this version of Visual D plays nice with 2.055? - Alex
Sep 10 2011
next sibling parent reply Rainer Schuetze <r.sagitario gmx.de> writes:
On 10.09.2011 14:05, Alex Rønne Petersen wrote:
 On 25-08-2011 09:28, Rainer Schuetze wrote:
 Hi,

 I'd like to announce the release of a new version of Visual D:

 2011-08-25 Version 0.3.26

 * fixed regression in last version: single file compilation did not
 build any d files
 * single file compilation: avoid relinking every time
 * separate compile and link: no longer trashes dependencies in link step
 * goto definition, search symbol: now line number adjusted according to
 changes since last successful build
 * fix: resource files in sub folders would not build because the same
 folders were expected in the intermediate directory
 * global settings: split page into directories/settings pages to make
 option "Show build time" accessible
 * global settings: added option to disable sorting projects
 * parser now accepts "do {} while(condition)" without trailing ';'
 * project options macro $(PROJECTNAME) now uses the name in the solution
 instead of the project file name
 * fixed bad indentation of first contract
 * fixed colorization of first token after debug condition without
 arguments
 * "is" now always colored as operator, not as keyword
 * updated to build with dmd 2.055beta

 Visual D provides seamless integration of the D programming language
 into Visual Studio. It can be downloaded here:
 http://www.dsource.org/projects/visuald/

 Best,
 Rainer

Hi, Does anyone know whether this version of Visual D plays nice with 2.055? - Alex

Should be no problem. There is also a brand new 0.3.27rc1 in the download folder, that is actualy built with dmd 2.055very-late-beta. It also fixes the indentation issues.
Sep 10 2011
parent reply =?ISO-8859-1?Q?Alex_R=F8nne_Petersen?= <xtzgzorex gmail.com> writes:
On 10-09-2011 18:53, Rainer Schuetze wrote:
 On 10.09.2011 14:05, Alex Rønne Petersen wrote:
 On 25-08-2011 09:28, Rainer Schuetze wrote:
 Hi,

 I'd like to announce the release of a new version of Visual D:

 2011-08-25 Version 0.3.26

 * fixed regression in last version: single file compilation did not
 build any d files
 * single file compilation: avoid relinking every time
 * separate compile and link: no longer trashes dependencies in link step
 * goto definition, search symbol: now line number adjusted according to
 changes since last successful build
 * fix: resource files in sub folders would not build because the same
 folders were expected in the intermediate directory
 * global settings: split page into directories/settings pages to make
 option "Show build time" accessible
 * global settings: added option to disable sorting projects
 * parser now accepts "do {} while(condition)" without trailing ';'
 * project options macro $(PROJECTNAME) now uses the name in the solution
 instead of the project file name
 * fixed bad indentation of first contract
 * fixed colorization of first token after debug condition without
 arguments
 * "is" now always colored as operator, not as keyword
 * updated to build with dmd 2.055beta

 Visual D provides seamless integration of the D programming language
 into Visual Studio. It can be downloaded here:
 http://www.dsource.org/projects/visuald/

 Best,
 Rainer

Hi, Does anyone know whether this version of Visual D plays nice with 2.055? - Alex

Should be no problem. There is also a brand new 0.3.27rc1 in the download folder, that is actualy built with dmd 2.055very-late-beta. It also fixes the indentation issues.

Oh, cool. Thanks! - Alex
Sep 10 2011
parent reply =?ISO-8859-1?Q?Alex_R=F8nne_Petersen?= <xtzgzorex gmail.com> writes:
On 10-09-2011 20:36, Alex Rønne Petersen wrote:
 On 10-09-2011 18:53, Rainer Schuetze wrote:
 On 10.09.2011 14:05, Alex Rønne Petersen wrote:
 On 25-08-2011 09:28, Rainer Schuetze wrote:
 Hi,

 I'd like to announce the release of a new version of Visual D:

 2011-08-25 Version 0.3.26

 * fixed regression in last version: single file compilation did not
 build any d files
 * single file compilation: avoid relinking every time
 * separate compile and link: no longer trashes dependencies in link
 step
 * goto definition, search symbol: now line number adjusted according to
 changes since last successful build
 * fix: resource files in sub folders would not build because the same
 folders were expected in the intermediate directory
 * global settings: split page into directories/settings pages to make
 option "Show build time" accessible
 * global settings: added option to disable sorting projects
 * parser now accepts "do {} while(condition)" without trailing ';'
 * project options macro $(PROJECTNAME) now uses the name in the
 solution
 instead of the project file name
 * fixed bad indentation of first contract
 * fixed colorization of first token after debug condition without
 arguments
 * "is" now always colored as operator, not as keyword
 * updated to build with dmd 2.055beta

 Visual D provides seamless integration of the D programming language
 into Visual Studio. It can be downloaded here:
 http://www.dsource.org/projects/visuald/

 Best,
 Rainer

Hi, Does anyone know whether this version of Visual D plays nice with 2.055? - Alex

Should be no problem. There is also a brand new 0.3.27rc1 in the download folder, that is actualy built with dmd 2.055very-late-beta. It also fixes the indentation issues.

Oh, cool. Thanks! - Alex

Just to confirm: All indentation and white space issues I had pointed out seem gone. Thanks a lot! - Alex
Sep 10 2011
parent Rainer Schuetze <r.sagitario gmx.de> writes:
On 20.12.2011 23:27, Froglegs wrote:
 Is there any way to make it so that suggestions are automatic, like in
 Visual Assist?

 What I mean is that in Visual D if I want suggestions I have to hit
 cntrl-space while typing, but in VA they just appear under me as I type,
 and if I want to accept one I just hit enter.

I was also wondering whether I like that VA feature or whether I hate it. It can sometimes get annoying because you have to hit the escape key to get your cursor functions back.
 Also is Visual D open source, can others help out?

Sure, you can find build instructions here: http://www.dsource.org/projects/visuald/wiki/Build_from_source
Dec 21 2011
prev sibling parent "Froglegs" <lugtug gmail.com> writes:
Is there any way to make it so that suggestions are automatic, 
like in Visual Assist?

What I mean is that in Visual D if I want suggestions I have to 
hit cntrl-space while typing, but in VA they just appear under me 
as I type, and if I want to accept one I just hit enter.

Also is Visual D open source, can others help out?
Dec 20 2011
prev sibling next sibling parent reply "Mr. Anonymous" <mailnew4ster gmail.com> writes:
Thanks for your work!

A small thing:
When debugging/running a console app using C++, the console window does 
not automatically close, but shows a text like "press any key to exit.."
When using D, it's quite annoying when I want to test a snippet and the 
console exits, I have to write readf(); or similar to keep it open.
Dec 24 2011
next sibling parent reply Rainer Schuetze <r.sagitario gmx.de> writes:
Hi,

On 24.12.2011 20:19, Mr. Anonymous wrote:
 Thanks for your work!

 A small thing:
 When debugging/running a console app using C++, the console window does
 not automatically close, but shows a text like "press any key to exit.."

I have never seen something like that in Visual Studio for C++ projects. Is it happening for Managed-C++? Is there an option to activate/deactivate that behaviour? I just tried it with C# and Managed C++ console projects in VS11, and they close the console window immediately.
 When using D, it's quite annoying when I want to test a snippet and the
 console exits, I have to write readf(); or similar to keep it open.

Dec 26 2011
parent reply "Mr. Anonymous" <mailnew4ster gmail.com> writes:
On 26.12.2011 11:05, Rainer Schuetze wrote:
 Hi,

 On 24.12.2011 20:19, Mr. Anonymous wrote:
 Thanks for your work!

 A small thing:
 When debugging/running a console app using C++, the console window does
 not automatically close, but shows a text like "press any key to exit.."

I have never seen something like that in Visual Studio for C++ projects. Is it happening for Managed-C++? Is there an option to activate/deactivate that behaviour? I just tried it with C# and Managed C++ console projects in VS11, and they close the console window immediately.
 When using D, it's quite annoying when I want to test a snippet and the
 console exits, I have to write readf(); or similar to keep it open.


Steps to reproduce: * Create a new "Visual C++: Win32 Console Application" project. * Create the project with default settings. * You'll get an empty _tmain() function, add printf("test\n"); above return 0; * Press Ctrl+F5 to run it. * Screenshot: http://i.imgur.com/VuhHJ.png
Dec 29 2011
parent reply Rainer Schuetze <r.sagitario gmx.de> writes:
On 29.12.2011 13:27, Mr. Anonymous wrote:
 On 26.12.2011 11:05, Rainer Schuetze wrote:
 Hi,

 On 24.12.2011 20:19, Mr. Anonymous wrote:
 Thanks for your work!

 A small thing:
 When debugging/running a console app using C++, the console window does
 not automatically close, but shows a text like "press any key to exit.."

I have never seen something like that in Visual Studio for C++ projects. Is it happening for Managed-C++? Is there an option to activate/deactivate that behaviour? I just tried it with C# and Managed C++ console projects in VS11, and they close the console window immediately.
 When using D, it's quite annoying when I want to test a snippet and the
 console exits, I have to write readf(); or similar to keep it open.


Steps to reproduce: * Create a new "Visual C++: Win32 Console Application" project. * Create the project with default settings. * You'll get an empty _tmain() function, add printf("test\n"); above return 0; * Press Ctrl+F5 to run it. * Screenshot: http://i.imgur.com/VuhHJ.png

Ok, it does not happen when running the program in the debugger, but when starting it without the debugger. I can mimic that (probably optional as it might not make much sense for a non-console application). I've also added an option to redirect stdout to the debug output window (only supported by the Visual Studio debugger, not mago).
Dec 29 2011
next sibling parent reply Rainer Schuetze <r.sagitario gmx.de> writes:
On 07.06.2013 22:59, Diggory wrote:
 Thanks for your great plugin! The integration with VS is great,
 especially the debugging.

Thanks.
 There are a few things I think could be improved though:
 - I couldn't get it to work properly on VS 2012, the functionality seems
 to be there but it doesn't hook up with the buttons properly. For
 example, "Start Debugging" fails, and so does "Build -> Build Solution"
 with "The method or operation is not implemented", whereas
 right-clicking in the solution explorer and choosing "Build" works just
 fine. It seems all toolbar actions and actions on the main menu bar
 don't work, whereas right-click actions do. It works fine in VS 2010.

I test it with the VS 2012 Shell from time to time, and it works for me. I also think other use it successfully. The context menu items refer to the project only, while the buttons are for the solution, so maybe this is the difference. Does building the project from the menu work? Maybe you have some addin/extension that hooks the build command and somehow conflicts with Visual D?
 - I couldn't find a way to get it to play nicely with a hierarchical
 folder structure. I can add a folder in VS but it's actually a filter
 rather than a folder, and if I create a subfolder with a .d file in and
 then add it to the project it just shows up in the top level. Since D's
 modules work based on folder structure it would be nice if Visual D
 worked the same way.

If the filter actually matches the folder on disk, there is some link between the project and the disk. You can also drag a folder into the project and Visual D will add all files in the directory rebuilding the folder hierarchy. If you use the new item dialog and select the package, both a folder and disk and a filter in the project are created.
 - It would be nice if ctrl-shift-space showed the parameters expected
 like in other languages in VS. Visual D seems to already have that
 information because when you hover over a function name it shows the
 signature.

It does that to some extent if you generate JSON information with the project build. Unfortunately a recent version of dmd changed the format making it tedious to get the parameter names, so you only see the types ATM. Long term, it should be merged with the semantic analysis that also drives the tool tips.
Jun 11 2013
parent Rainer Schuetze <r.sagitario gmx.de> writes:
On 07.08.2013 22:57, PhilE wrote:
 Apologies if this is totally the wrong place for my questions. I'm
 trying to get started with D and I'm using Visual D. I can't work out
 how to run unit tests in any module other than that containing main,
 either in static libraries or even other modules in the same library.
 How is this done? I have the command line parameter -unittest set, which
 runs unit tests in the file containing main, but no others.

Running unittests built into libraries is a known problem: http://d.puremagic.com/issues/show_bug.cgi?id=4669 A workaround that is also used in the standard runtime library is to build an executable with the library modules to run the unittests. In Visual D you can make a copy of the project configuration and switch it to output type "executable". Adding "-main" to the additional command line options takes advantage of a feature introduced in dmd 2.063 that avoids having to add "void main() {}" somewhere.
Aug 10 2013
prev sibling parent Rainer Schuetze <r.sagitario gmx.de> writes:
On 15.02.2014 01:00, Michael wrote:
 I seem to be absolutely useless.

 I installed the exe which installs dmd and visualD.

 I create a project and try running it as the hello world code is
 still in.

 I click build and visual studio crashes.

 I am running windows 8.1 x64 and visual studio 2013 professional.
 This issue is on both my laptop and desktop.

I have the same setup here. I suspect there is some bad interaction with other installed extensions. Please try the latest beta, it improved cooperation with the NuGet package manager and probably other extensions: https://github.com/D-Programming-Language/visuald/releases
Feb 14 2014
prev sibling next sibling parent "Marco Leise" <Marco.Leise gmx.de> writes:
Am 26.12.2011, 10:05 Uhr, schrieb Rainer Schuetze <r.sagitario gmx.de>:

 Hi,

 On 24.12.2011 20:19, Mr. Anonymous wrote:
 Thanks for your work!

 A small thing:
 When debugging/running a console app using C++, the console window does
 not automatically close, but shows a text like "press any key to exit.."

I have never seen something like that in Visual Studio for C++ projects. Is it happening for Managed-C++? Is there an option to activate/deactivate that behaviour? I just tried it with C# and Managed C++ console projects in VS11, and they close the console window immediately.
 When using D, it's quite annoying when I want to test a snippet and the
 console exits, I have to write readf(); or similar to keep it open.


A little unrelated: In Eclipse the console is a permanent dockable window, that gets cleared when you restart the program. It also highlights stderr in red. It is not always better than opening a separate window and usually has a small visible area, but it solves this problem very well. The nice thing is that is always switches as you start the compiler or a program that needs a console and then stays open when the process exits.
Dec 26 2011
prev sibling next sibling parent "Brad" <fraksworld hotmail.com> writes:
There is a company called Sapphire Steel that makes Visual Studio 
add-ons for Ruby and ActionScript. I asked the owner by email if 
he would be interested in extending his product line for D but he 
says that he does not think there would be a big enough user base 
to justify the work. So I think it would be worth just taking a 
look at the features he offers for Ruby and AS and see if at the 
very least we can get ideas from it:
http://www.sapphiresteel.com/
Aug 28 2012
prev sibling next sibling parent "Diggory" <diggsey googlemail.com> writes:
Thanks for your great plugin! The integration with VS is great, 
especially the debugging.

There are a few things I think could be improved though:
- I couldn't get it to work properly on VS 2012, the 
functionality seems to be there but it doesn't hook up with the 
buttons properly. For example, "Start Debugging" fails, and so 
does "Build -> Build Solution" with "The method or operation is 
not implemented", whereas right-clicking in the solution explorer 
and choosing "Build" works just fine. It seems all toolbar 
actions and actions on the main menu bar don't work, whereas 
right-click actions do. It works fine in VS 2010.

- I couldn't find a way to get it to play nicely with a 
hierarchical folder structure. I can add a folder in VS but it's 
actually a filter rather than a folder, and if I create a 
subfolder with a .d file in and then add it to the project it 
just shows up in the top level. Since D's modules work based on 
folder structure it would be nice if Visual D worked the same way.

- It would be nice if ctrl-shift-space showed the parameters 
expected like in other languages in VS. Visual D seems to already 
have that information because when you hover over a function name 
it shows the signature.
Jun 07 2013
prev sibling next sibling parent "PhilE" <theotherphil hotmail.com> writes:
On Tuesday, 11 June 2013 at 20:47:45 UTC, Rainer Schuetze wrote:
 On 07.06.2013 22:59, Diggory wrote:
 Thanks for your great plugin! The integration with VS is great,
 especially the debugging.

Thanks.
 There are a few things I think could be improved though:
 - I couldn't get it to work properly on VS 2012, the 
 functionality seems
 to be there but it doesn't hook up with the buttons properly. 
 For
 example, "Start Debugging" fails, and so does "Build -> Build 
 Solution"
 with "The method or operation is not implemented", whereas
 right-clicking in the solution explorer and choosing "Build" 
 works just
 fine. It seems all toolbar actions and actions on the main 
 menu bar
 don't work, whereas right-click actions do. It works fine in 
 VS 2010.

I test it with the VS 2012 Shell from time to time, and it works for me. I also think other use it successfully. The context menu items refer to the project only, while the buttons are for the solution, so maybe this is the difference. Does building the project from the menu work? Maybe you have some addin/extension that hooks the build command and somehow conflicts with Visual D?
 - I couldn't find a way to get it to play nicely with a 
 hierarchical
 folder structure. I can add a folder in VS but it's actually a 
 filter
 rather than a folder, and if I create a subfolder with a .d 
 file in and
 then add it to the project it just shows up in the top level. 
 Since D's
 modules work based on folder structure it would be nice if 
 Visual D
 worked the same way.

If the filter actually matches the folder on disk, there is some link between the project and the disk. You can also drag a folder into the project and Visual D will add all files in the directory rebuilding the folder hierarchy. If you use the new item dialog and select the package, both a folder and disk and a filter in the project are created.
 - It would be nice if ctrl-shift-space showed the parameters 
 expected
 like in other languages in VS. Visual D seems to already have 
 that
 information because when you hover over a function name it 
 shows the
 signature.

It does that to some extent if you generate JSON information with the project build. Unfortunately a recent version of dmd changed the format making it tedious to get the parameter names, so you only see the types ATM. Long term, it should be merged with the semantic analysis that also drives the tool tips.

Apologies if this is totally the wrong place for my questions. I'm trying to get started with D and I'm using Visual D. I can't work out how to run unit tests in any module other than that containing main, either in static libraries or even other modules in the same library. How is this done? I have the command line parameter -unittest set, which runs unit tests in the file containing main, but no others.
Aug 07 2013
prev sibling next sibling parent "PhilE" <theotherphil hotmail.com> writes:
On Saturday, 10 August 2013 at 09:29:01 UTC, Rainer Schuetze 
wrote:
 On 07.08.2013 22:57, PhilE wrote:
 Apologies if this is totally the wrong place for my questions. 
 I'm
 trying to get started with D and I'm using Visual D. I can't 
 work out
 how to run unit tests in any module other than that containing 
 main,
 either in static libraries or even other modules in the same 
 library.
 How is this done? I have the command line parameter -unittest 
 set, which
 runs unit tests in the file containing main, but no others.

Running unittests built into libraries is a known problem: http://d.puremagic.com/issues/show_bug.cgi?id=4669 A workaround that is also used in the standard runtime library is to build an executable with the library modules to run the unittests. In Visual D you can make a copy of the project configuration and switch it to output type "executable". Adding "-main" to the additional command line options takes advantage of a feature introduced in dmd 2.063 that avoids having to add "void main() {}" somewhere.

Thanks.
Aug 10 2013
prev sibling next sibling parent "Frustrated" <c1514843 drdrb.com> writes:
On Friday, 7 June 2013 at 21:00:00 UTC, Diggory wrote:
 Thanks for your great plugin! The integration with VS is great, 
 especially the debugging.

 There are a few things I think could be improved though:
 - I couldn't get it to work properly on VS 2012, the 
 functionality seems to be there but it doesn't hook up with the 
 buttons properly. For example, "Start Debugging" fails, and so 
 does "Build -> Build Solution" with "The method or operation is 
 not implemented", whereas right-clicking in the solution 
 explorer and choosing "Build" works just fine. It seems all 
 toolbar actions and actions on the main menu bar don't work, 
 whereas right-click actions do. It works fine in VS 2010.

I just had this issue when it was recently working. Using 2013 and latest Visual D. Installed about two months ago fresh and everything worked. Installex Xmarion studio with monoD about a week ago and started using that but since I couldn't debug I just went back to visual D. Now I have the exact problem described here. Even my old projects that used to work fine have this issue. Somehow either something got corrupt or changed. Seems like it is a visual D/visual studio issue though and having to do with the menu's and keyboards. I tried reinstalled Visual D with no luck.
Jan 27 2014
prev sibling next sibling parent "Frustrated" <c1514843 drdrb.com> writes:
On Monday, 27 January 2014 at 15:02:46 UTC, Frustrated wrote:
 On Friday, 7 June 2013 at 21:00:00 UTC, Diggory wrote:
 Thanks for your great plugin! The integration with VS is 
 great, especially the debugging.

 There are a few things I think could be improved though:
 - I couldn't get it to work properly on VS 2012, the 
 functionality seems to be there but it doesn't hook up with 
 the buttons properly. For example, "Start Debugging" fails, 
 and so does "Build -> Build Solution" with "The method or 
 operation is not implemented", whereas right-clicking in the 
 solution explorer and choosing "Build" works just fine. It 
 seems all toolbar actions and actions on the main menu bar 
 don't work, whereas right-click actions do. It works fine in 
 VS 2010.

I just had this issue when it was recently working. Using 2013 and latest Visual D. Installed about two months ago fresh and everything worked. Installex Xmarion studio with monoD about a week ago and started using that but since I couldn't debug I just went back to visual D. Now I have the exact problem described here. Even my old projects that used to work fine have this issue. Somehow either something got corrupt or changed. Seems like it is a visual D/visual studio issue though and having to do with the menu's and keyboards. I tried reinstalled Visual D with no luck.

uninstalled visual studio, reinstalled, reinstalled visual D. Was able to build and debug from menu and use shortcuts. Was getting the same error in the output of the build but said something about nuget throwing the error(no dialog box this time). Uninstalled nuget and the error went away. Everything *seems* to work as expected now. BTW, recently every post I have made is flagged as spam. This is very annoying.
Jan 28 2014
prev sibling next sibling parent "Michael " <mike43110 outlook.com> writes:
I seem to be absolutely useless.

I installed the exe which installs dmd and visualD.

I create a project and try running it as the hello world code is
still in.

I click build and visual studio crashes.

I am running windows 8.1 x64 and visual studio 2013 professional.
This issue is on both my laptop and desktop.

Thanks
Feb 14 2014
prev sibling parent "volax" <volax yandex.ru> writes:
Re,

 I am running windows 8.1 x64 and visual Please try the latest 
 beta, it improved cooperation with the NuGet package manager 
 and probably other extensions: 
 https://github.com/D-Programming-Language/visuald/releases

Thank you! It really solves all debug issues.
Apr 07 2014
prev sibling next sibling parent reply "Paul Jurczak" <pauljurczak yahoo.com> writes:
On Thursday, 25 August 2011 at 07:28:57 UTC, Rainer Schuetze 
wrote:
 Hi,

 I'd like to announce the release of a new version of Visual D:

 2011-08-25 Version 0.3.26

Thank you for this very useful tool. I'm curious, is it is possible to use non-ASCII (e.g. Greek letters) characters in D literals with Visual D in WYSIWYG fashion?
Aug 18 2013
parent Rainer Schuetze <r.sagitario gmx.de> writes:
On 19.08.2013 04:03, Paul Jurczak wrote:
 On Thursday, 25 August 2011 at 07:28:57 UTC, Rainer Schuetze wrote:
 Hi,

 I'd like to announce the release of a new version of Visual D:

 2011-08-25 Version 0.3.26

Thank you for this very useful tool. I'm curious, is it is possible to use non-ASCII (e.g. Greek letters) characters in D literals with Visual D in WYSIWYG fashion?

Should be no problem, the text encoding is set to utf8 in the editor by Visual D. (see "Advanced Save Options").
Aug 19 2013
prev sibling next sibling parent "Derek" <derekbrowncmu gmail.com> writes:
I'm trying to use Visual D with the Windows API bindings (from
here: http://dsource.org/projects/bindings/wiki/WindowsApi), but
I'm getting linking errors for the functions declared in windef.d:

Error	1	Error 42: Symbol Undefined _D5win326windef8MAKELONGFttZk
(uint win32.windef.MAKELONG(ushort,
ushort))	C:\Users\Derek\Documents\Visual Studio
2012\Projects\WindowsApp1\WindowsApp1\	

(One example)

I reckon this means that I need to build a library for this and
probably other files, but I haven't found any instructions to do
so. Furthermore, all of the function in winuser.d link perfectly
fine, so this just confuses me.

So what do I need to do to make this compile and link correctly?
Apr 10 2014
prev sibling next sibling parent "evilrat" <evilrat666 gmail.com> writes:
On Friday, 11 April 2014 at 02:40:25 UTC, Derek wrote:
 I'm trying to use Visual D with the Windows API bindings (from
 here: http://dsource.org/projects/bindings/wiki/WindowsApi), but
 I'm getting linking errors for the functions declared in 
 windef.d:

 Error	1	Error 42: Symbol Undefined _D5win326windef8MAKELONGFttZk
 (uint win32.windef.MAKELONG(ushort,
 ushort))	C:\Users\Derek\Documents\Visual Studio
 2012\Projects\WindowsApp1\WindowsApp1\	

 (One example)

 I reckon this means that I need to build a library for this and
 probably other files, but I haven't found any instructions to do
 so. Furthermore, all of the function in winuser.d link perfectly
 fine, so this just confuses me.

 So what do I need to do to make this compile and link correctly?

everything on dsource is quite outdated. try this instead https://github.com/AndrejMitrovic/DWinProgramming/tree/master/WindowsAPI
Apr 10 2014
prev sibling next sibling parent "Derek" <derekbrowncmu gmail.com> writes:
On Friday, 11 April 2014 at 04:07:55 UTC, evilrat wrote:
 everything on dsource is quite outdated. try this instead

 https://github.com/AndrejMitrovic/DWinProgramming/tree/master/WindowsAPI

I downloaded that and ran dmd_build.bat, it produced dmd_win32_x32.lib which I put in the dmd2/windows/lib folder. I then added it to my linker library files. This made MAKELONG link, but LOWORD and HIWORD still don't link (again, really weird because they're defined in the same file): Error 1 Error 42: Symbol Undefined _D5win326windef6LOWORDFmZt (ushort win32.windef.LOWORD(ulong)) C:\Users\Derek\Documents\Visual Studio 2012\Projects\WindowsApp1\WindowsApp1\ Error 2 Error 42: Symbol Undefined _D5win326windef6HIWORDFmZt (ushort win32.windef.HIWORD(ulong)) C:\Users\Derek\Documents\Visual Studio 2012\Projects\WindowsApp1\WindowsApp1\
Apr 10 2014
prev sibling next sibling parent "evilrat" <evilrat666 gmail.com> writes:
On Friday, 11 April 2014 at 04:31:42 UTC, Derek wrote:
 On Friday, 11 April 2014 at 04:07:55 UTC, evilrat wrote:
 everything on dsource is quite outdated. try this instead

 https://github.com/AndrejMitrovic/DWinProgramming/tree/master/WindowsAPI

I downloaded that and ran dmd_build.bat, it produced dmd_win32_x32.lib which I put in the dmd2/windows/lib folder. I then added it to my linker library files. This made MAKELONG link, but LOWORD and HIWORD still don't link (again, really weird because they're defined in the same file): Error 1 Error 42: Symbol Undefined _D5win326windef6LOWORDFmZt (ushort win32.windef.LOWORD(ulong)) C:\Users\Derek\Documents\Visual Studio 2012\Projects\WindowsApp1\WindowsApp1\ Error 2 Error 42: Symbol Undefined _D5win326windef6HIWORDFmZt (ushort win32.windef.HIWORD(ulong)) C:\Users\Derek\Documents\Visual Studio 2012\Projects\WindowsApp1\WindowsApp1\

if they are templates try make them plain function
Apr 10 2014
prev sibling next sibling parent "Derek" <derekbrowncmu gmail.com> writes:
On Friday, 11 April 2014 at 04:55:58 UTC, evilrat wrote:
 if they are templates try make them plain function

// Links. uint MAKELONG(ushort a, ushort b) { return cast(uint) ((b << 16) | a); } // Does not link. uint MAKELONG(uint a, uint b) { assert((a & 0xFFFF0000) == 0); assert((b & 0xFFFF0000) == 0); return MAKELONG(cast(ushort)a, cast(ushort)b); } // Does not link. ushort LOWORD(ulong l) { return cast(ushort) l; } // Does not link. ushort HIWORD(ulong l) { return cast(ushort) (l >>> 16); } I grepped to see if MAKELONG was defined somewhere else as well, but it's not.
Apr 10 2014
prev sibling next sibling parent "Derek" <derekbrowncmu gmail.com> writes:
On Friday, 11 April 2014 at 05:14:56 UTC, Derek wrote:
 On Friday, 11 April 2014 at 04:55:58 UTC, evilrat wrote:
 if they are templates try make them plain function

// Links. uint MAKELONG(ushort a, ushort b) { return cast(uint) ((b << 16) | a); } // Does not link. uint MAKELONG(uint a, uint b) { assert((a & 0xFFFF0000) == 0); assert((b & 0xFFFF0000) == 0); return MAKELONG(cast(ushort)a, cast(ushort)b); } // Does not link. ushort LOWORD(ulong l) { return cast(ushort) l; } // Does not link. ushort HIWORD(ulong l) { return cast(ushort) (l >>> 16); } I grepped to see if MAKELONG was defined somewhere else as well, but it's not.

I've found another I believe related example. The constant RICHEDIT_CLASS in richedit.d. Trying to use it gives the linking error: Error 1 Error 42: Symbol Undefined _D5win328richedit14RICHEDIT_CLASSxAa (const(char[]) win32.richedit.RICHEDIT_CLASS) C:\Users\Derek\Documents\Visual Studio 2012\Projects\WindowsApp1\WindowsApp1\ It is defined in richedit.d as: version(Unicode) { const wchar[] RICHEDIT_CLASS = "RichEdit20W"; } else { const char[] RICHEDIT_CLASS = "RichEdit20A"; } (And FTR my project is compiling in ANSI mode)
Apr 10 2014
prev sibling next sibling parent "evilrat" <evilrat666 gmail.com> writes:
On Friday, 11 April 2014 at 06:25:19 UTC, Derek wrote:
 It is defined in richedit.d as:

 version(Unicode) {
 	const wchar[] RICHEDIT_CLASS = "RichEdit20W";
 } else {
 	const char[] RICHEDIT_CLASS  = "RichEdit20A";
 }

 (And FTR my project is compiling in ANSI mode)

and this could be rewritted as enum instead of array. but why all this start happens on 2.065?
Apr 11 2014
prev sibling parent "Derek" <derekbrowncmu gmail.com> writes:
On Saturday, 12 April 2014 at 04:45:14 UTC, evilrat wrote:
 and this could be rewritted as enum instead of array. but why 
 all this start happens on 2.065?

I figured out my problem. When I changed the win32 library I was using I replaced the src dir, but not the import dir, and as a result the symbols that weren't linking had different types in the import files versus the library. So fixing it was just a matter of replacing the import directory with the correct version. For the record, I figured this out by using libunres -d to look for the missing symbols in the library, and then a short demangling program I wrote (using std.demangle) to reveal the types of the library symbols and the expected symbols, this pointed me in the right direction to realize that there import and src directories were different. It's building now, thanks for your help.
Apr 11 2014