Bug 13888 – VisualD project settings use the same property grid as C/C++ projects?

Is it possible for VisualD to use the same property grid that C/C++ projects use for the project settings? There are some subtle differences in behaviour, and I think it would go a long way to making the experience feel a lot more 'real'. The distinction from the MSVC projects gives an impression to new users that the D ecosystem lives 'outside'/separately, and doesn't really integrate well. This is all about user impressions, and familiarity + usability.

The property grid is generated when you use the standard msbuild project setting mechanism. I'd hate to do that because that makes writing it in D almost impossible. It could be mimicked to some extend, but that will probably not really feel the same. It would probably also be hard to emulate the VC++ bugs when the dialog elements move out at the top in VS2013 ;-)

Oh, I see. Do you still think writing VisualD in D was a good idea? Or would you reconsider deviating from the standard approach retrospect? :) 2013? I've never tried that IDE yet. Still on 2010, perhaps I need to get with the times...

My first attempt at Visual D was adapting a C# project, but I hated it. Maybe I'd be more relaxed today ,-) Writing it in D caused a number of problems, especially with the redesign of VS starting with 2010 that completely embraced C#. A lot of features could be integrated easier when using C#, some don't work at all without C#. That's why Visual D has a helper extension to interface with WPF. Still, I believe D was the better choice, as I wouldn't use D that much if it weren't for Visual D. The good thing about VS2013: there is a free community version of it available, so we'd probably don't have to care for the shell versions, missing linker support or other binaries for debugging.

I guess you got the requested grid with the new VC project integration.