GUI and Web Frameworks

Activity designers in WF4.0 are built using Windows Presentation Foundation (WPF). WPF provides the visual designer surface, the property grid, and all the UI components that make up the workflow designer experience. Silverlight and Windows are not used for WF activity designers.

To associate a custom designer with an activity in WF4.0, you apply the Designer attribute to the activity class. This attribute specifies which designer class should be used to visually represent the activity. The attribute typically points to a class derived from ActivityDesigner. The other options are not valid mechanisms for designer association.

In Windows Workflow Foundation, an Activity Designer is a customized WPF control. It consists of both a XAML file defining the user interface layout and a corresponding code-behind file (like C# or VB.NET) to implement the runtime interaction logic, making the statement false.

Bookmarks in WF4.0 are a mechanism that allows an activity to pause its execution at a specific point and wait for an external event to resume it. The activity 'hangs' (waits) at the bookmark position until ResumeBookmark is called with matching bookmark name. Bookmarks enable long-running workflows that can wait for user input or external events without blocking threads.

StateInitialization is a WF3.0 activity that was NOT carried forward to WF4.0. In WF4.0, state machine workflows were completely absent initially and when reintroduced in WF4.5, they use different activity types (State, Assign, etc.). The other options (WriteLine, Assign, Flowchart) are all valid built-in WF4.0 activities.

In WF 4.0, the available control flow constructs are FlowChart and Sequence activities. StateMachine was not part of the initial WF 4.0 release - it was reintroduced later in WF 4.5. The other options incorrectly include StateMachine or don't list both available types.

The Pick activity in WF 4.0 is specifically designed for event-driven scenarios. Each branch in a Pick contains a Trigger activity (like ReceiveEvent) that waits for a specific event, and an Action activity that executes when that event occurs. This makes Pick the primary event-handling construct in WF 4.0.

WCF defines ServiceContract, OperationContract, DataContract, MessageContract, and FaultContract as standard contract types. There is no BehaviourContract in WCF - behaviors are specified using attributes like [ServiceBehavior] and [OperationBehavior], which are not contracts.

Android user interfaces are built hierarchically using View and ViewGroup objects. Dialogs and menus are window components that contain view hierarchies rather than being the direct structural building blocks.

FrameLayout, TableLayout, and RelativeLayout are all standard Android layout classes. SystemLayout does not exist in the Android SDK, making it the correct non-layout object.

All four options (Button, TextView, EditText, CheckBox) are fully implemented UI widgets in the Android SDK. These are basic View classes available from API Level 1 and are commonly used in Android application development for user interaction.

A submenu is a floating list of menu items opened by pressing an item in another menu (like the Options Menu). Side menu, active menu, and indirect menu are not standard terms for this Android UI component.

In the legacy Google Maps library for Android, the MapController class is specifically designed to control and navigate map locations (such as panning and zooming). MapView displays the map, and MapActivity manages the lifecycle of map views.

In the Flex component lifecycle, the initialize event is dispatched after the component and all its children have been created but before the component's size has been determined. Option C accurately describes this stage - creation is complete, but layout calculation has not occurred yet. The preinitialize event fires earlier, and creationComplete fires after layout.

AdvancedDataGrid extends DataGrid to provide built-in support for grouped and hierarchical data display. While regular DataGrid shows flat data, AdvancedDataGrid can group data by fields and display it in an expandable tree format within the tabular structure. SummaryRow is used within AdvancedDataGrid but is not a standalone grouping control.