Why does the application class (application) have both xaml and code behind files?

In WPF applications, all views are inherited from System.Windows.Window and have an associated xaml and codebehind file. It seems logical.

However, I am confused why the application file inherited from System.Windows.Application has the xaml file? Although this application is not a view (it is not visible)? I know that this file is usually used to determine application resources, etc., And xaml provides an efficient way to determine them. But this can also be done programmatically. Then what is the use of wpf developers due to the availability of both xaml and file code for the "App"? Wouldn't one of them be enough?

+3
source share
2 answers

, , System.Windows.Application, xaml? , ( )?

, XAML - , . , WPF SilverLigth, - .

, , Workflow (XOML XAML), SharePoint XAML , XAML - - ( , HTML).

, , ( ), :

  • ( xaml)
  • ( )
+5

- . - . , TextBox ( ) , App.xaml .

+1

All Articles