WPF Databinding intellisense
Ok, so I have a general question about WPF. I've messed a little with ASP.NET MVC and in the markup it has intellisense on your viewmodel object so you don't mistype it( i love it).
Enter WPF, I love it, I'm utilizing the MVVM approach and one annoying thing that I have to do is make sure I'm binding correctly to my viewmodel. So I type something up in my xaml, then I either
1) if I'm lazy just run the app and click around
2) If i'm not lazy
a)Look at the current DataContext of the control I'm working with.
b)Go to that ViewModel class look at the properties
c)Find my property and then click back to my view and make sure that I spelled it correctly.
I believe that you can look at your trace output for incorrect bindings at run time, but is there something in the horizon to allow intellisense in xaml. The View needs to know about my ViewModel, so why not expose that in xaml.
I think it would be nice for the IDE to do that for me, meaning, when I type "{Binding " it should go up the visual tree find the first non-null DataContext and display the properties, let me select one and there you have it.
Am I missing something? Are there any alternatives. Any insight?
EDIT:
Regarding the comments below there is a way to set the datacontext at design time e.g.
<Window.Resources>
<DesignTimeData:DesignTimeCustomers x:Key="designTimeCustomersDS" />
</Window.Resources>
which is a snippet from this blog:
http://karlshifflett.wordpress.com/2008/10/11/viewing-design-time-data-in-visual-studio-2008-cider-designer-in-wpf-and-silverlight-projects/
All it does is reference a class within xaml.
So with that in place could not the designer then utilize reflection on the datacontext to give you all of the properties for that class?
wpf data-binding mvvm intellisense
edited Aug 1 '11 at 16:19
Dave Clemmer
2,977114371
asked Jun 3 '09 at 14:10
Jose
6,009185482
add a comment |
Ok, so I have a general question about WPF. I've messed a little with ASP.NET MVC and in the markup it has intellisense on your viewmodel object so you don't mistype it( i love it).
Enter WPF, I love it, I'm utilizing the MVVM approach and one annoying thing that I have to do is make sure I'm binding correctly to my viewmodel. So I type something up in my xaml, then I either
1) if I'm lazy just run the app and click around
2) If i'm not lazy
a)Look at the current DataContext of the control I'm working with.
b)Go to that ViewModel class look at the properties
c)Find my property and then click back to my view and make sure that I spelled it correctly.
I believe that you can look at your trace output for incorrect bindings at run time, but is there something in the horizon to allow intellisense in xaml. The View needs to know about my ViewModel, so why not expose that in xaml.
I think it would be nice for the IDE to do that for me, meaning, when I type "{Binding " it should go up the visual tree find the first non-null DataContext and display the properties, let me select one and there you have it.
Am I missing something? Are there any alternatives. Any insight?
EDIT:
Regarding the comments below there is a way to set the datacontext at design time e.g.
<Window.Resources>
<DesignTimeData:DesignTimeCustomers x:Key="designTimeCustomersDS" />
</Window.Resources>
which is a snippet from this blog:
http://karlshifflett.wordpress.com/2008/10/11/viewing-design-time-data-in-visual-studio-2008-cider-designer-in-wpf-and-silverlight-projects/
All it does is reference a class within xaml.
So with that in place could not the designer then utilize reflection on the datacontext to give you all of the properties for that class?
wpf data-binding mvvm intellisense
edited Aug 1 '11 at 16:19
Dave Clemmer
2,977114371
asked Jun 3 '09 at 14:10
Jose
6,009185482
In some ways WPF really shines - in others it's a POS. This is one of those others.
– Jonathan C Dickinson
Jun 3 '09 at 14:13
That's why I'm using tests to validate all (well, almost all) view bindings against corresponding ViewModels.
– Snowbear
Feb 28 '11 at 11:44
As already suggested below, use Resharper (with d:DataContext set), it will save you a lot of time. you can directly generate viewmodel properties from xaml with alt+enter
– Boklucius
Aug 1 '13 at 9:52
add a comment |
Ok, so I have a general question about WPF. I've messed a little with ASP.NET MVC and in the markup it has intellisense on your viewmodel object so you don't mistype it( i love it).
Enter WPF, I love it, I'm utilizing the MVVM approach and one annoying thing that I have to do is make sure I'm binding correctly to my viewmodel. So I type something up in my xaml, then I either
1) if I'm lazy just run the app and click around
2) If i'm not lazy
a)Look at the current DataContext of the control I'm working with.
b)Go to that ViewModel class look at the properties
c)Find my property and then click back to my view and make sure that I spelled it correctly.
I believe that you can look at your trace output for incorrect bindings at run time, but is there something in the horizon to allow intellisense in xaml. The View needs to know about my ViewModel, so why not expose that in xaml.
I think it would be nice for the IDE to do that for me, meaning, when I type "{Binding " it should go up the visual tree find the first non-null DataContext and display the properties, let me select one and there you have it.
Am I missing something? Are there any alternatives. Any insight?
EDIT:
Regarding the comments below there is a way to set the datacontext at design time e.g.
<Window.Resources>
<DesignTimeData:DesignTimeCustomers x:Key="designTimeCustomersDS" />
</Window.Resources>
which is a snippet from this blog:
http://karlshifflett.wordpress.com/2008/10/11/viewing-design-time-data-in-visual-studio-2008-cider-designer-in-wpf-and-silverlight-projects/
All it does is reference a class within xaml.
So with that in place could not the designer then utilize reflection on the datacontext to give you all of the properties for that class?
wpf data-binding mvvm intellisense
edited Aug 1 '11 at 16:19
Dave Clemmer
2,977114371
asked Jun 3 '09 at 14:10
Jose
6,009185482
Ok, so I have a general question about WPF. I've messed a little with ASP.NET MVC and in the markup it has intellisense on your viewmodel object so you don't mistype it( i love it).
Enter WPF, I love it, I'm utilizing the MVVM approach and one annoying thing that I have to do is make sure I'm binding correctly to my viewmodel. So I type something up in my xaml, then I either
1) if I'm lazy just run the app and click around
2) If i'm not lazy
a)Look at the current DataContext of the control I'm working with.
b)Go to that ViewModel class look at the properties
c)Find my property and then click back to my view and make sure that I spelled it correctly.
I believe that you can look at your trace output for incorrect bindings at run time, but is there something in the horizon to allow intellisense in xaml. The View needs to know about my ViewModel, so why not expose that in xaml.
I think it would be nice for the IDE to do that for me, meaning, when I type "{Binding " it should go up the visual tree find the first non-null DataContext and display the properties, let me select one and there you have it.
Am I missing something? Are there any alternatives. Any insight?
EDIT:
Regarding the comments below there is a way to set the datacontext at design time e.g.
<Window.Resources>
<DesignTimeData:DesignTimeCustomers x:Key="designTimeCustomersDS" />
</Window.Resources>
which is a snippet from this blog:
http://karlshifflett.wordpress.com/2008/10/11/viewing-design-time-data-in-visual-studio-2008-cider-designer-in-wpf-and-silverlight-projects/
All it does is reference a class within xaml.
So with that in place could not the designer then utilize reflection on the datacontext to give you all of the properties for that class?
wpf data-binding mvvm intellisense
wpf data-binding mvvm intellisense
edited Aug 1 '11 at 16:19
Dave Clemmer
2,977114371
asked Jun 3 '09 at 14:10
Jose
6,009185482
edited Aug 1 '11 at 16:19
Dave Clemmer
2,977114371
asked Jun 3 '09 at 14:10
Jose
6,009185482
edited Aug 1 '11 at 16:19
Dave Clemmer
2,977114371
edited Aug 1 '11 at 16:19
Dave Clemmer
2,977114371
edited Aug 1 '11 at 16:19
Dave Clemmer
2,977114371
2,977114371
asked Jun 3 '09 at 14:10
Jose
6,009185482
asked Jun 3 '09 at 14:10
Jose
6,009185482
asked Jun 3 '09 at 14:10
Jose
6,009185482
6,009185482
In some ways WPF really shines - in others it's a POS. This is one of those others.
– Jonathan C Dickinson
Jun 3 '09 at 14:13
That's why I'm using tests to validate all (well, almost all) view bindings against corresponding ViewModels.
– Snowbear
Feb 28 '11 at 11:44
As already suggested below, use Resharper (with d:DataContext set), it will save you a lot of time. you can directly generate viewmodel properties from xaml with alt+enter
– Boklucius
Aug 1 '13 at 9:52
add a comment |
In some ways WPF really shines - in others it's a POS. This is one of those others.
– Jonathan C Dickinson
Jun 3 '09 at 14:13
That's why I'm using tests to validate all (well, almost all) view bindings against corresponding ViewModels.
– Snowbear
Feb 28 '11 at 11:44
As already suggested below, use Resharper (with d:DataContext set), it will save you a lot of time. you can directly generate viewmodel properties from xaml with alt+enter
– Boklucius
Aug 1 '13 at 9:52
In some ways WPF really shines - in others it's a POS. This is one of those others.
– Jonathan C Dickinson
Jun 3 '09 at 14:13
In some ways WPF really shines - in others it's a POS. This is one of those others.
– Jonathan C Dickinson
Jun 3 '09 at 14:13
That's why I'm using tests to validate all (well, almost all) view bindings against corresponding ViewModels.
– Snowbear
Feb 28 '11 at 11:44
That's why I'm using tests to validate all (well, almost all) view bindings against corresponding ViewModels.
– Snowbear
Feb 28 '11 at 11:44
As already suggested below, use Resharper (with d:DataContext set), it will save you a lot of time. you can directly generate viewmodel properties from xaml with alt+enter
– Boklucius
Aug 1 '13 at 9:52
As already suggested below, use Resharper (with d:DataContext set), it will save you a lot of time. you can directly generate viewmodel properties from xaml with alt+enter
– Boklucius
Aug 1 '13 at 9:52
add a comment |
5 Answers
5
active
oldest
votes
So with that in place could not the
designer then utilize reflection on
the datacontext to give you all of the
properties for that class?
Resharper 6 has this feature and can show you members of the d:DataContext in the intellisense, if you set the d:DataContext on the View.
answered Jun 17 '11 at 8:54
Liviu Trifoi
2,36611527
add a comment |
VS 2013:
IntelliSense with resolved DataContext
IntelliSense with design time DataContext
answered Feb 15 '15 at 15:50
RAM
7,61243658
Nice, this fixed it for me using VS2017. Had to add a reference to the namespace in my Window: xmlns:vm="clr-namespace:my.viewmodel.namespace" and then set the design time viewmodel on the Window: d:DataContext="{d:DesignInstance Type=vm:MyViewModel}". I now have intellisense on my bindings even though the DataContext is initialised in external code.
– Richard Moore
Oct 29 at 19:49
add a comment |
Visual Studio 2010 will support intellisense on Bindings. However, this is limited to the properties of the Binding object itself. For example after typing "{Binding " into the XAML editor I then get intellisense on the remaining properties (Path, ElementName, etc.).
I don't think the type of intellisense regarding the data context you specified would be possible as the data context is set at run-time. I've tried experimenting in VS 2010 by setting the data context directly in the constructor but did not have any luck.
answered Jun 3 '09 at 15:46
Richard McGuire
7,18482633
Here's the link for the MIX09 video that goes over some of this, fast forward to around 20min to get into the Resource Picker and intellisence: videos.visitmix.com/MIX09/T73M
– rmoore
Jun 3 '09 at 15:48
Given that the DataContext is set a run time, I doubt that it's possible to implement intellisense for bindings, unfortunately. Just because the type of the variable set as the DataContext is Foo, it could really be a Bar and Bar's properties are fair game to use for bindings. How could Visual Studio know this to be the case?
– Andy
Jun 3 '09 at 17:29
I made some updates above that basically indicates that we can assign the datacontext in design time. But from your comments, it seems this isn't on the horizon.
– Jose
Jun 4 '09 at 16:22
add a comment |
According to :
http://blogs.msdn.com/b/visualstudio/archive/2013/08/09/xaml-editor-improvements-in-visual-studio-2013.aspx
Visual studio 2013 xaml Editor now is supporting IntelliSense for Data Binding
answered Jun 3 '14 at 14:09
M.Sabaa
1137
add a comment |
In Visual Studio 2010 there is a binding builder which you can enable
http://blogs.msdn.com/b/wpfsldesigner/archive/2010/06/14/how-to-enable-using-the-binding-builder-in-wpf-and-silverlight-applications.aspx
but you still don't get intellisense which is weird.
answered Feb 28 '11 at 11:41
Jeremy Thomas
14914
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f944987%2fwpf-databinding-intellisense%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
So with that in place could not the
designer then utilize reflection on
the datacontext to give you all of the
properties for that class?
Resharper 6 has this feature and can show you members of the d:DataContext in the intellisense, if you set the d:DataContext on the View.
answered Jun 17 '11 at 8:54
Liviu Trifoi
2,36611527
add a comment |
So with that in place could not the
designer then utilize reflection on
the datacontext to give you all of the
properties for that class?
Resharper 6 has this feature and can show you members of the d:DataContext in the intellisense, if you set the d:DataContext on the View.
answered Jun 17 '11 at 8:54
Liviu Trifoi
2,36611527
add a comment |
So with that in place could not the
designer then utilize reflection on
the datacontext to give you all of the
properties for that class?
Resharper 6 has this feature and can show you members of the d:DataContext in the intellisense, if you set the d:DataContext on the View.
answered Jun 17 '11 at 8:54
Liviu Trifoi
2,36611527
So with that in place could not the
designer then utilize reflection on
the datacontext to give you all of the
properties for that class?
Resharper 6 has this feature and can show you members of the d:DataContext in the intellisense, if you set the d:DataContext on the View.
answered Jun 17 '11 at 8:54
Liviu Trifoi
2,36611527
answered Jun 17 '11 at 8:54
Liviu Trifoi
2,36611527
answered Jun 17 '11 at 8:54
Liviu Trifoi
2,36611527
answered Jun 17 '11 at 8:54
Liviu Trifoi
2,36611527
2,36611527
add a comment |
add a comment |
VS 2013:
IntelliSense with resolved DataContext
IntelliSense with design time DataContext
answered Feb 15 '15 at 15:50
RAM
7,61243658
Nice, this fixed it for me using VS2017. Had to add a reference to the namespace in my Window: xmlns:vm="clr-namespace:my.viewmodel.namespace" and then set the design time viewmodel on the Window: d:DataContext="{d:DesignInstance Type=vm:MyViewModel}". I now have intellisense on my bindings even though the DataContext is initialised in external code.
– Richard Moore
Oct 29 at 19:49
add a comment |
VS 2013:
IntelliSense with resolved DataContext
IntelliSense with design time DataContext
answered Feb 15 '15 at 15:50
RAM
7,61243658
Nice, this fixed it for me using VS2017. Had to add a reference to the namespace in my Window: xmlns:vm="clr-namespace:my.viewmodel.namespace" and then set the design time viewmodel on the Window: d:DataContext="{d:DesignInstance Type=vm:MyViewModel}". I now have intellisense on my bindings even though the DataContext is initialised in external code.
– Richard Moore
Oct 29 at 19:49
add a comment |
VS 2013:
IntelliSense with resolved DataContext
IntelliSense with design time DataContext
answered Feb 15 '15 at 15:50
RAM
7,61243658
VS 2013:
IntelliSense with resolved DataContext
IntelliSense with design time DataContext
answered Feb 15 '15 at 15:50
RAM
7,61243658
answered Feb 15 '15 at 15:50
RAM
7,61243658
answered Feb 15 '15 at 15:50
RAM
7,61243658
answered Feb 15 '15 at 15:50
RAM
7,61243658
7,61243658
Nice, this fixed it for me using VS2017. Had to add a reference to the namespace in my Window: xmlns:vm="clr-namespace:my.viewmodel.namespace" and then set the design time viewmodel on the Window: d:DataContext="{d:DesignInstance Type=vm:MyViewModel}". I now have intellisense on my bindings even though the DataContext is initialised in external code.
– Richard Moore
Oct 29 at 19:49
add a comment |
Nice, this fixed it for me using VS2017. Had to add a reference to the namespace in my Window: xmlns:vm="clr-namespace:my.viewmodel.namespace" and then set the design time viewmodel on the Window: d:DataContext="{d:DesignInstance Type=vm:MyViewModel}". I now have intellisense on my bindings even though the DataContext is initialised in external code.
– Richard Moore
Oct 29 at 19:49
Nice, this fixed it for me using VS2017. Had to add a reference to the namespace in my Window: xmlns:vm="clr-namespace:my.viewmodel.namespace" and then set the design time viewmodel on the Window: d:DataContext="{d:DesignInstance Type=vm:MyViewModel}". I now have intellisense on my bindings even though the DataContext is initialised in external code.
– Richard Moore
Oct 29 at 19:49
Nice, this fixed it for me using VS2017. Had to add a reference to the namespace in my Window: xmlns:vm="clr-namespace:my.viewmodel.namespace" and then set the design time viewmodel on the Window: d:DataContext="{d:DesignInstance Type=vm:MyViewModel}". I now have intellisense on my bindings even though the DataContext is initialised in external code.
– Richard Moore
Oct 29 at 19:49
add a comment |
Visual Studio 2010 will support intellisense on Bindings. However, this is limited to the properties of the Binding object itself. For example after typing "{Binding " into the XAML editor I then get intellisense on the remaining properties (Path, ElementName, etc.).
I don't think the type of intellisense regarding the data context you specified would be possible as the data context is set at run-time. I've tried experimenting in VS 2010 by setting the data context directly in the constructor but did not have any luck.
answered Jun 3 '09 at 15:46
Richard McGuire
7,18482633
Here's the link for the MIX09 video that goes over some of this, fast forward to around 20min to get into the Resource Picker and intellisence: videos.visitmix.com/MIX09/T73M
– rmoore
Jun 3 '09 at 15:48
Given that the DataContext is set a run time, I doubt that it's possible to implement intellisense for bindings, unfortunately. Just because the type of the variable set as the DataContext is Foo, it could really be a Bar and Bar's properties are fair game to use for bindings. How could Visual Studio know this to be the case?
– Andy
Jun 3 '09 at 17:29
I made some updates above that basically indicates that we can assign the datacontext in design time. But from your comments, it seems this isn't on the horizon.
– Jose
Jun 4 '09 at 16:22
add a comment |
Visual Studio 2010 will support intellisense on Bindings. However, this is limited to the properties of the Binding object itself. For example after typing "{Binding " into the XAML editor I then get intellisense on the remaining properties (Path, ElementName, etc.).
I don't think the type of intellisense regarding the data context you specified would be possible as the data context is set at run-time. I've tried experimenting in VS 2010 by setting the data context directly in the constructor but did not have any luck.
answered Jun 3 '09 at 15:46
Richard McGuire
7,18482633
Here's the link for the MIX09 video that goes over some of this, fast forward to around 20min to get into the Resource Picker and intellisence: videos.visitmix.com/MIX09/T73M
– rmoore
Jun 3 '09 at 15:48
Given that the DataContext is set a run time, I doubt that it's possible to implement intellisense for bindings, unfortunately. Just because the type of the variable set as the DataContext is Foo, it could really be a Bar and Bar's properties are fair game to use for bindings. How could Visual Studio know this to be the case?
– Andy
Jun 3 '09 at 17:29
I made some updates above that basically indicates that we can assign the datacontext in design time. But from your comments, it seems this isn't on the horizon.
– Jose
Jun 4 '09 at 16:22
add a comment |
Visual Studio 2010 will support intellisense on Bindings. However, this is limited to the properties of the Binding object itself. For example after typing "{Binding " into the XAML editor I then get intellisense on the remaining properties (Path, ElementName, etc.).
I don't think the type of intellisense regarding the data context you specified would be possible as the data context is set at run-time. I've tried experimenting in VS 2010 by setting the data context directly in the constructor but did not have any luck.
answered Jun 3 '09 at 15:46
Richard McGuire
7,18482633
Visual Studio 2010 will support intellisense on Bindings. However, this is limited to the properties of the Binding object itself. For example after typing "{Binding " into the XAML editor I then get intellisense on the remaining properties (Path, ElementName, etc.).
I don't think the type of intellisense regarding the data context you specified would be possible as the data context is set at run-time. I've tried experimenting in VS 2010 by setting the data context directly in the constructor but did not have any luck.
answered Jun 3 '09 at 15:46
Richard McGuire
7,18482633
answered Jun 3 '09 at 15:46
Richard McGuire
7,18482633
answered Jun 3 '09 at 15:46
Richard McGuire
7,18482633
answered Jun 3 '09 at 15:46
Richard McGuire
7,18482633
7,18482633
Here's the link for the MIX09 video that goes over some of this, fast forward to around 20min to get into the Resource Picker and intellisence: videos.visitmix.com/MIX09/T73M
– rmoore
Jun 3 '09 at 15:48
Given that the DataContext is set a run time, I doubt that it's possible to implement intellisense for bindings, unfortunately. Just because the type of the variable set as the DataContext is Foo, it could really be a Bar and Bar's properties are fair game to use for bindings. How could Visual Studio know this to be the case?
– Andy
Jun 3 '09 at 17:29
I made some updates above that basically indicates that we can assign the datacontext in design time. But from your comments, it seems this isn't on the horizon.
– Jose
Jun 4 '09 at 16:22
add a comment |
Here's the link for the MIX09 video that goes over some of this, fast forward to around 20min to get into the Resource Picker and intellisence: videos.visitmix.com/MIX09/T73M
– rmoore
Jun 3 '09 at 15:48
Given that the DataContext is set a run time, I doubt that it's possible to implement intellisense for bindings, unfortunately. Just because the type of the variable set as the DataContext is Foo, it could really be a Bar and Bar's properties are fair game to use for bindings. How could Visual Studio know this to be the case?
– Andy
Jun 3 '09 at 17:29
I made some updates above that basically indicates that we can assign the datacontext in design time. But from your comments, it seems this isn't on the horizon.
– Jose
Jun 4 '09 at 16:22
Here's the link for the MIX09 video that goes over some of this, fast forward to around 20min to get into the Resource Picker and intellisence: videos.visitmix.com/MIX09/T73M
– rmoore
Jun 3 '09 at 15:48
Here's the link for the MIX09 video that goes over some of this, fast forward to around 20min to get into the Resource Picker and intellisence: videos.visitmix.com/MIX09/T73M
– rmoore
Jun 3 '09 at 15:48
Given that the DataContext is set a run time, I doubt that it's possible to implement intellisense for bindings, unfortunately. Just because the type of the variable set as the DataContext is Foo, it could really be a Bar and Bar's properties are fair game to use for bindings. How could Visual Studio know this to be the case?
– Andy
Jun 3 '09 at 17:29
Given that the DataContext is set a run time, I doubt that it's possible to implement intellisense for bindings, unfortunately. Just because the type of the variable set as the DataContext is Foo, it could really be a Bar and Bar's properties are fair game to use for bindings. How could Visual Studio know this to be the case?
– Andy
Jun 3 '09 at 17:29
I made some updates above that basically indicates that we can assign the datacontext in design time. But from your comments, it seems this isn't on the horizon.
– Jose
Jun 4 '09 at 16:22
I made some updates above that basically indicates that we can assign the datacontext in design time. But from your comments, it seems this isn't on the horizon.
– Jose
Jun 4 '09 at 16:22
add a comment |
According to :
http://blogs.msdn.com/b/visualstudio/archive/2013/08/09/xaml-editor-improvements-in-visual-studio-2013.aspx
Visual studio 2013 xaml Editor now is supporting IntelliSense for Data Binding
answered Jun 3 '14 at 14:09
M.Sabaa
1137
add a comment |
According to :
http://blogs.msdn.com/b/visualstudio/archive/2013/08/09/xaml-editor-improvements-in-visual-studio-2013.aspx
Visual studio 2013 xaml Editor now is supporting IntelliSense for Data Binding
answered Jun 3 '14 at 14:09
M.Sabaa
1137
add a comment |
According to :
http://blogs.msdn.com/b/visualstudio/archive/2013/08/09/xaml-editor-improvements-in-visual-studio-2013.aspx
Visual studio 2013 xaml Editor now is supporting IntelliSense for Data Binding
answered Jun 3 '14 at 14:09
M.Sabaa
1137
According to :
http://blogs.msdn.com/b/visualstudio/archive/2013/08/09/xaml-editor-improvements-in-visual-studio-2013.aspx
Visual studio 2013 xaml Editor now is supporting IntelliSense for Data Binding
answered Jun 3 '14 at 14:09
M.Sabaa
1137
answered Jun 3 '14 at 14:09
M.Sabaa
1137
answered Jun 3 '14 at 14:09
M.Sabaa
1137
answered Jun 3 '14 at 14:09
M.Sabaa
1137
1137
add a comment |
add a comment |
In Visual Studio 2010 there is a binding builder which you can enable
http://blogs.msdn.com/b/wpfsldesigner/archive/2010/06/14/how-to-enable-using-the-binding-builder-in-wpf-and-silverlight-applications.aspx
but you still don't get intellisense which is weird.
answered Feb 28 '11 at 11:41
Jeremy Thomas
14914
add a comment |
In Visual Studio 2010 there is a binding builder which you can enable
http://blogs.msdn.com/b/wpfsldesigner/archive/2010/06/14/how-to-enable-using-the-binding-builder-in-wpf-and-silverlight-applications.aspx
but you still don't get intellisense which is weird.
answered Feb 28 '11 at 11:41
Jeremy Thomas
14914
add a comment |
In Visual Studio 2010 there is a binding builder which you can enable
http://blogs.msdn.com/b/wpfsldesigner/archive/2010/06/14/how-to-enable-using-the-binding-builder-in-wpf-and-silverlight-applications.aspx
but you still don't get intellisense which is weird.
answered Feb 28 '11 at 11:41
Jeremy Thomas
14914
In Visual Studio 2010 there is a binding builder which you can enable
http://blogs.msdn.com/b/wpfsldesigner/archive/2010/06/14/how-to-enable-using-the-binding-builder-in-wpf-and-silverlight-applications.aspx
but you still don't get intellisense which is weird.
answered Feb 28 '11 at 11:41
Jeremy Thomas
14914
edited Jul 8 '11 at 2:51
answered Feb 28 '11 at 11:41
Jeremy Thomas
14914
answered Feb 28 '11 at 11:41
Jeremy Thomas
14914
answered Feb 28 '11 at 11:41
Jeremy Thomas
14914
14914
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f944987%2fwpf-databinding-intellisense%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
In some ways WPF really shines - in others it's a POS. This is one of those others.
– Jonathan C Dickinson
Jun 3 '09 at 14:13
That's why I'm using tests to validate all (well, almost all) view bindings against corresponding ViewModels.
– Snowbear
Feb 28 '11 at 11:44
As already suggested below, use Resharper (with d:DataContext set), it will save you a lot of time. you can directly generate viewmodel properties from xaml with alt+enter
– Boklucius
Aug 1 '13 at 9:52