Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can write a wrapper around xamDataGrid that has a dependencyproperty called filename. The viewmodel can then bind to this property. When the xamDataGrid detects a change on the filename property it can then execute the code you suggested. Afterwards reset the filename property for further notification.</p> <p>This solution keeps out the code from you code behind and makes the xamDataGrid responsible for exporting its data.</p> <p>-------edit---------</p> <p>A second solution can make use of the MVVM light messenger class. In stead of declaring a dependency property, make your wrapper listen to a message. When the viewmodel sends the message (which could for example have the filename as parameter) the wrapper can then execute the code.</p> <p>eg</p> <pre><code>public class ExportableXamDataGrid: XamDataGrid { public ExportableXamDataGrid():base() { Messenger.Default.Register&lt;string&gt;(this,"ExportExcel",ExportFile); } private void ExportFile(string file) { xamDataGridExcelExporter.xamDataGridExcelExporter xamDataGridExcelExporter1 = new xamDataGridExcelExporter.xamDataGridExcelExporter(); xamDataGridExcelExporter1.Export(**this.xamDataGrid1**, @"C:\Excel\ExportFile.xls"); } } </code></pre> <p>Then in your viewmodel you can do:</p> <pre><code> Messenger.Default.Send(@"C:\Excel\ExportFile.xls","ExportExcel"); </code></pre> <p>There are many solutions to your problem, all of which you do not have to start writing logic in your view.</p> <p><a href="http://www.lucbos.net/2011/06/using-codebehind-in-mvvm.html" rel="nofollow">http://www.lucbos.net/2011/06/using-codebehind-in-mvvm.html</a></p>
    singulars
    1. This table or related slice is empty.
    1. POTrue MVVM and third party controls
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USLuc Bos
    1. USLuc Bos
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTrue MVVM and third party controls
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    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. COBoth solution1 and solution2 looks to be a good fit here. Could you provide a code snipet for solution2.
      singulars
      1. PO
      1. USPradeep
    2. COI edited my answer. I do not have the infragistics library so your implementation might differ a bit though the grand scheme of things should be the same. Should the XamDatagrid be sealed then you can make a wrapper. The down side off using a wrapper is that you'll have to declare all the dependency properties you use in xaml and pass them trough.
      singulars
      1. PO
      1. USLuc Bos
    3. COThanks @Luc Bos. Thats a clean solution and shall be useful not only in this case but where ever the third party control is not MVVM compatible.
      singulars
      1. PO
      1. USPradeep
 

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