Main menu

Tag Archives: 70-502-CSHARP notes

Windows and navigation applications are installed on a desktop computer. These applications can also run under the full trust environment and have full access to the resources of the computer being used.

A XAML browser application runs in Windows Internet Explorer. It runs under a limited set of permissions allowed by the Internet security zone. It can access isolated storage available in the zone. It cannot use a desktop computer’s resources such as the file system, databases, and the Windows registry.

A WPF standalone application is installed on a client computer. Hence, it does not require a Web browser. It behaves like a Windows Form application and presents a non-navigational interface to a user. It can also be used by offline users.

The event route for a particular event (for example, the Click event) can travel from the source element, which bubbles upwards through the element tree of its parent element until it reaches the element tree root (can be a page or a window).

The Click event is raised when the Button control is clicked.

The private void OnChildElementMouseDown(object sender, MouseButtonEventArgs e) {} code segment in the scenario will simply execute the mouse event and the bubbling or tunneling routing process will continue. If you have written e.Handled = true; inside the code statement, the bubbling or tunneling routing process would have been stopped and has marked the event as handled in the event handler.

Windows and navigation applications are installed on a desktop computer. These applications can also run under the full trust environment and have full access to the resources of the computer being used.

A XAML browser application runs in Windows Internet Explorer. It runs under a limited set of permissions allowed by the Internet security zone. It can access isolated storage available in the zone. It cannot use a desktop computer’s resources such as the file system, databases, and the Windows registry.

A WPF standalone application is installed on a client computer. Hence, it does not require a Web browser. It behaves like a Windows Form application and presents a non-navigational interface to a user. It can also be used by offline users.

The event route for a particular event (for example, the Click event) can travel from the source element, which bubbles upwards through the element tree of its parent element until it reaches the element tree root (can be a page or a window).

The Click event is raised when the Button control is clicked.

The private void OnChildElementMouseDown(object sender, MouseButtonEventArgs e) {} code segment in the scenario will simply execute the mouse event and the bubbling or tunneling routing process will continue. If you have written e.Handled = true; inside the code statement, the bubbling or tunneling routing process would have been stopped and has marked the event as handled in the event handler.