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.

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.

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.

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.

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.

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?

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").

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.

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.

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