Databases
StackOverflow2013
Postsdbo
POStartup displaying a modal window followed by a standard window
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POStartup displaying a modal window followed by a standard window
    primarykey
    data
    text
    <p>I am launching an MVVM application with code in the App.xaml.cs like so:</p> <pre><code>protected override void OnStartup(StartupEventArgs e) { base.OnStartup(e); //Set data directory string baseDir = Environment.GetFolderPath(Environment.SpecialFolder.CommonApplicationData) + @"\BlowTrial"; if (!Directory.Exists(baseDir)) { Directory.CreateDirectory(baseDir); } AppDomain.CurrentDomain.SetData("DataDirectory", baseDir); //Application initialisation AutoMapperConfiguration.Configure(); //Security CustomPrincipal customPrincipal = new CustomPrincipal(); AppDomain.CurrentDomain.SetThreadPrincipal(customPrincipal); // Create the ViewModel to which // the main window binds. var mainWindowVm = new MainWindowViewModel(); MainWindow window = new MainWindow(mainWindowVm); // When the ViewModel asks to be closed, // close the window. EventHandler handler = null; handler = delegate { window.Close(); if (!window.IsLoaded) //in case user cancelled close event { mainWindowVm.RequestClose -= handler; } }; mainWindowVm.RequestClose += handler; window.Show(); } </code></pre> <p>I would like to test for the existence of entities containing important data for running the application, and if these do not exist, run a wizard (as a dialog) which obtains these settings:</p> <pre><code>if (BlowTrialDataService.GetBackupDetails().BackupData == null || !_repository.LocalStudyCentres.Any()) { DisplayAppSettingsWizard(); } static void DisplayAppSettingsWizard() { //testfor and display starup wizard var wizard = new GetAppSettingsWizard(); GetAppSettingsViewModel appSettings = new GetAppSettingsViewModel(); wizard.DataContext = appSettings; EventHandler wizardHandler = null; wizardHandler = delegate { wizard.Close(); wizard = null; appSettings.RequestClose -= wizardHandler; }; appSettings.RequestClose += wizardHandler; wizard.ShowDialog(); } </code></pre> <p>When I place this code in the MainWindow.xaml.cs, the application runs correctly. When it is placed in either the App.xaml.cs (before the code to instantiate the instance of MainWindow), or in the constructor for MainWindowViewModel, the wizard displays correctly, but the application ends without displaying the MainWindow on completion of the wizard. If there is no cause to display the wizard, MainWindow displays correctly in all cases.</p> <p>Examining the debug output, there are no errors of note (a few first chance exceptions related to sql commands).</p> <p>Is there a reason for this - having the code in the code behind MainWindow.xaml does not seem the most logical place (which to my mind would be the app.xaml.cs).</p> <p>Thank you for your expertise.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USWill
    1. USBrent
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POStartup displaying a modal window followed by a standard window
      1. This table or related slice is empty.
      1. VTDownMod
    1. COFeel free to comment on the downvote - that way I can improve future questions
      singulars
      1. POStartup displaying a modal window followed by a standard window
      1. USBrent
 

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