Thread overview
VisualD IDE for Windows Visual Studio
Jun 15, 2010
Larry Luther
Jun 16, 2010
theambient
Jun 17, 2010
Rainer Schuetze
Jun 22, 2010
Patrick Kreft
June 15, 2010
The IDE question has appeared multiple times.
If using Windows, my recommendation is VisualD for MS Visual Studio.
I've had difficulties with SlickEdit, D-IDE, and Eclipse plug ins.
VisualD:
  * All the features of typical C++ development and debugging.
  * Good editor
  * D 2.0 support
  * Single step debugging.
  * Breakpoints etc.
  * Examine variables while single stepping.
  * Pausing over variables reveals their value.
  * The only thing negative I've noticed is that the
    symbolic names of enum variables are not printed out.

Larry


June 16, 2010
yes, I really  liked it since I revealed it.
very good, simple and easy configurable ide

by the way you can mix project of different languages in solution!
-- 
--
Ruslan Mullakhmetov

"Larry Luther" <larry.luther@dolby.com> 
> The IDE question has appeared multiple times.
> If using Windows, my recommendation is VisualD for MS Visual Studio.
> I've had difficulties with SlickEdit, D-IDE, and Eclipse plug ins.
> VisualD:
>  * All the features of typical C++ development and debugging.
>  * Good editor
>  * D 2.0 support
>  * Single step debugging.
>  * Breakpoints etc.
>  * Examine variables while single stepping.
>  * Pausing over variables reveals their value.
>  * The only thing negative I've noticed is that the
>    symbolic names of enum variables are not printed out.
> 
> Larry 
> 
> 
June 17, 2010
Larry Luther wrote:
> The IDE question has appeared multiple times.
> If using Windows, my recommendation is VisualD for MS Visual Studio.
> I've had difficulties with SlickEdit, D-IDE, and Eclipse plug ins.
> VisualD:
>   * All the features of typical C++ development and debugging.
>   * Good editor
>   * D 2.0 support
>   * Single step debugging.
>   * Breakpoints etc.
>   * Examine variables while single stepping.
>   * Pausing over variables reveals their value.

Thanks for promoting Visual D :-)

>   * The only thing negative I've noticed is that the
>     symbolic names of enum variables are not printed out.

I've been looking into it: even though the enum type is specified in the debug info, the variables type information is lost somewhere in the code generation stages of DMD. I'm trying to create a patch...

Rainer
June 22, 2010
I hope that code completion get some improvement ;)