Databases
StackOverflow2013
Usersdbo
USDonald Airey
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USDonald Airey
    primarykey
    data
    text
    plurals
    1. PO
      singulars
      1. PTAnswer
    2. POXAML And Dependency Injection
      singulars
      1. PTQuestion
    3. PO
      singulars
      1. PTAnswer
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI wish to extend my apologies to devdigital. The discussion of a Repository was a red-herring, but his design is essentially correct. The View Model is created using DI, then the XAML code binds to exposed elements of the View Model. The XAML elements themselves should not, and can not, be given their own view models. I wanted to make the controls self-contained so they could be re-used, but this is unrealistic in an MVVM design. Best design is to make the control view models reusable, but they'll always need to be exposed through the owner view model.
      singulars
      1. PO
      1. USDonald Airey
    2. COThe original poster has a valid question involving ListCollectionView and has already turned on virtualization. I am running into this same problem: the Refresh appears to recreate the items. I've already confirmed that virtualization is working by scrolling, but when I filter or sort using the view, WPF recreated all the items in the ListView.
      singulars
      1. PO
      1. USDonald Airey
    3. COCharleh, how about posting that as an answer so we can vote on it. It looks good. In my mind, I was hoping for some re-usability out of the Customer combobox such that I could just drop the same control into any view and have it work. Your approach suggests that I create a re-usable collection of customers and pull it out of the container in each view model, then make it into a property of each view model that has such a combobox. Not as elegant as just dropping in a CustomerComboBox, but I see how it fits the DI architecture better.
      singulars
      1. POXAML And Dependency Injection
      1. USDonald Airey
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload