datacontext

I have two properties in my view model: //Relationship has property ReasonForEndingId private Relationship editRelationship; public Relationship EditRelationship { get { return editRelationship; } set { if (editRelationship != value) { editRelationship = value; RaisePropertyChanged(EditRelationshipChangedEventArgs); } } } //ReasonForLeaving has properties Reason & Id private IList<ReasonForLeaving> reasonsComboList { get; set; } public IList<ReasonForLeaving> ReasonsComboList { get { return reasonsComboList; } private set { if (reasonsComboList != value) { reasonsComboList = value;

I need to access the container's DataContext from a UserControl (a grid containing textboxes and a listbox: I need to insert items in this list box) that I created in WPF: which is the best way to do it? I was thinking to pass the DataContext as parameter to user control but think there is a cleaner way to do it. Normally the DataContext will be inherited , just do not explicitly set it on the UserControl and it will get it from its parent. If you have to set it you could still use the Parent property to get the parent, which you then can safe-cast to a FrameworkElement and if it is not null

Hello WPF Pros at least I hope some of you read this! DataContext is a property on FrameworkElement (base class for all WPF Controls) and is implemented as a DependencyProperty. That means all the descendant elements in the logical tree share the same DataContext. So the ContentControl should do it with its descendant elements right? I have a scenario where that is NOT the case and I would like to know WHAT is the cause of that misbehaviour ?! That you understand a bit more about it please read this thread ( dont NOT want to copy everything here) where the trouble starts...: WPF: Can not find

I read somewhere that setting DataContext = this in the constructor of a user control is bad practice (can't find where though). Why is this bad practice? What is the alternative? In general, when someone uses your control they are going to want to set it's data context to their own view model class and bind the properties on your control to their view model. If you start messing around with the data context internally within the control, and rely on it being set to 'this', either you will prevent their binding from working, or your control won't work as expected because you rely on it not

Originally my .xaml form used the following line to set the Designer's DataContext where the view model was a non-generic type (note I'm talking about the Design time DataContext not the actual DataContext that will be used at runtime) . <Window ... xmlns:d="http://schemas.microsoft.com/expression/blend/2008" d:DataContext="{d:DesignInstance Dialogs:CustomerSearchDlogViewModel}" ...> Now instead of CustomerSearchDlogViewModel I have a generic SearchDialogViewModel but I can't figure out what syntax will work in the <Window> tag to let me specify that view model. That is not possible unless the

There seem to be two main ways to define DataContext in WPF: either in code like this: App.xaml.cs (taken from the WPF MVVM Toolkit template ): public partial class App : Application { private void OnStartup(object sender, StartupEventArgs e) { // Create the ViewModel and expose it using the View's DataContext MainView mainView = new MainView(); MainViewModel mainViewModel = new MainViewModel(); mainViewModel.LoadCustomers("c:\\testdata2\\Customers.xml"); mainView.DataContext = mainViewModel; mainView.Show(); } } or in XAML like this: Window1.xaml: <DockPanel> <StackPanel HorizontalAlignment=

Can I use transactions with a datacontext, so that I can rollback the state of the context after an error? And if so, how does that work? I use them in testing all the time :) try { dc.Connection.Open(); dc.Transaction = dc.Connection.BeginTransaction(); dc.SubmitChanges(); } finally { dc.Transaction.Rollback(); } UPDATE This will ALWAYS rollback after the fact. I use this in testing. A DataContext will pick up an ambient transaction by default, so it is just a matter of ensuring there is a Transaction in scope. The details become the main issue: What options do you need (e.g. isolation level)