XAML Intellisense for Properties

Topics: Questions
Aug 5, 2013 at 12:02 PM
Hello together,

no idea if its a feature of Resharper or already built in Visual Studio.
I used to have a static resource to a viewmodel of a view which I defined in my App.xaml.cs
Bound that to my datacontext of the window...that enabled intellisense for properties if I wanted to bind a property in xaml.
No idea if its a bad coding style, but I'm doing that since i'm coding with WPF and got used to it, to have properties suggested in xaml.

Now I just started to use my first mvvm framwork, got to know of catel from a .net magazine.
...and well, I'm mindblown I have to admit, impressive piece of work you've done there, really great job!
....could have saved me lots of hours and nerves in previous projects.

Wondering now If I shall still use the static resource to the Viewmodels or is it really a bad coding style. Are there alternatives?
Aug 7, 2013 at 4:19 PM
Sorry for the late reply, missed this one.

As far as I remember, this is a resharper feature. As long as the d:DesignDataContext has a specific type, it should automatically fill the intellisense.
Aug 8, 2013 at 5:32 AM
Thanks a lot for your reply, did as you suggested and its working now.