[lloyd]

I blogged about it there!
http://www.galador.net/codeblog/post/2011/05/20/D-for-NET-programmer.aspx

I find out one problem, I reckon (toward the bottom, when linking) the Libraries path seems not to work!

[sagitario]

Nice introduction and interesting report.

One comment: DFL is not only D1, maybe you did not get hold of the latest version. But the designer might not generate D2 code, I don't know.

There is also a global options page for Visual D, where you can setup system wide import and library paths. This avoids adding absolute paths to the project configuration.

So what could be done to improve the experience?

- the error message emitted by dmd when it does not find an import is one of the least comprehensible of the compiler. But I don't think Visual D is the place to fix it.

- the symbol names in linker errors can be intimidating. Visual D could try to translate the output to readable names, but this might make it more difficult to investigate problems on the object file level.

- The library search path option in the project configuration page at least needs some hint that more needs to be done to make the option work.

[lloyd]

Indeed I have to give a new try at DFL now that I can compile something!
Although.. DGUI looks good too!

[lloyd]

I posted some more!
http://galador.net/codeblog/post/2011/05/23/Discovering-D-and-Visual-Studio-(continued%E2%80%A6).aspx

This time I build DGui myself and linked my test project to "my" DGui project.
Worked a treat, yoohoo!!

Next time I will actually write some code hopefully!

[sagitario]

Nice blog. I'm thinking about putting a link somewhere on the Visual D page to help beginners get going. Sounds good for you?

BTW: if you have a dependency on a library project, you don't need to add the library and its path to the configuration of the depndent project. The library is automatically added to the link.

[lloyd]

Thanks! you are very welcome to link to it hey!
BTW, you can use the 'D' category to filter to ... D!