by jfisch
30. August 2010 08:40
I just ran into a situation where I couldn't uninstall my version of silverlight because it was missing the right .msi. I ended up looking in the right column of Programs and Features (control panel), looking up the silverlight installer location for that version in the Silverlight Release History, starting the installation just to extract the msi, look in C:\ for the install folder (named something like C:\75e0fa898bd7ca6), pointing the uninstaller's browse box at that directory for the correct version of the uninstaller. I kept getting an error on a windows update after the uninstaller browse box would display and I'd cancel it, not knowing why it kept popping up. Good luck to anyone with this issue! Hopefully this gives some work-around steps.
Jeff
by tman
1. June 2009 07:31
You should be able to bind a combo box to an entity list and then in the xaml set the DisplayMemberPath property to the descriptor. You can set the ItemSource and SelectedItem properties in your XAML or in your code behind, depending on what you're doing in your view model. Here's an example of one I have
<ComboBox x:Name="GenderComboBox" Path=Gender}" />
In the code behind, I chose to do it this way...
this.GenderComboBox.ItemsSource = viewModel.GenderList;
this.GenderComboBox.SelectedItem = viewModel.SelectedPatient.Gender;
I could have done it in the XAML, but the way I have my view model set up doesn’t, it won’t let me. The GenderList is an entity collection and each item has an ID property as well. The ID is what EF uses to build the FK relationships in the black box. ID from Gender is in the Person entinty so EF knows that when I submit my changes, it needs to build the FK relationship between the Gender entity and the Person entity and set the appropriate value.
Subscribe