Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, it depends. If you are writing a pure model library, it makes no sense to expose WPF-specific interfaces; this would force the users link against WPF libraries even if they don't need to. Even if it were not, it exposes something that the users are not going to need, which is not a good design IMHO.</p> <p>If your library is not limited to model usage, I would split it into several parts: core needed for all usage scenarios, WPF-dependent part with WPF-specific interfaces, maybe ASP-specific part with ASP-specific features and so on. The users will pick the parts they need and use them.</p> <hr> <p>Edit: as @Julien's comment states, <code>ObservableCollection&lt;T&gt;</code> is now as part of core, so including it won't make the users depend from the WPF-specific libraries. Nevertheless, the idea stays the same. For WPF usage, you often need to offer/work with specific features (<code>ObservableCollection</code>, <code>INotifyPropertyChanged</code>/<code>DependencyObject</code>, dependency properties, notifications in UI thread only and so on). This means that they belong to a separate, WPF-specific part of the project.</p> <p>So you can make the library consist of several parts: Library.Core.dll containing functions needed for generic/model development, Library.WPF.dll dealing with WPF-specific stuff and using Library.Core.dll, maybe Library.Console.dll and Library.ASP.dll as well. Users of WPF will use Library.Core.dll and Library.WPF.dll, console programs might need Library.Core.dll and Library.Console.dll and so on.</p>
    singulars
    1. This table or related slice is empty.
    1. POC# Class library collections ObservableCollection<T> vs Collection<T>
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USVlad
    1. USVlad
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI agree with your post but would like to precise that since .NET 4, `ObservableCollection` and other similar types have been moved from WindowsBase.dll to System.dll, so they're not really WPF specific anymore.
      singulars
      1. PO
      1. USJulien Lebosquain
    2. CO@Julien: I see, thanks! I'll update my answer.
      singulars
      1. PO
      1. USVlad
    3. COSo then... if ObservableCollection is not WPF specific and nobody is adding event handlers to the INotifyCollectionChanged interface perhaps the idea of using this type as the collection type is not so bad after all?
      singulars
      1. PO
      1. USRon Jacobs
 

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