GUI and Web Frameworks

The Insertable Objects pane provides access to Source (data sources), Data Item (query items), and Toolbox (lists, crosstabs, charts) for report design.

Report Studio supports List (tabular), Map (geographic), and Repeater (custom repeating layouts) report types. View is a database concept, not a Report Studio report type.

In AWT (Abstract Window Toolkit), only a Frame can have a MenuBar. The Frame class has a setMenuBar() method that allows you to attach a MenuBar. Panel is a generic container and cannot have a MenuBar directly attached to it. Class and JVM are not GUI containers at all.

Mapplets in Informatica are reusable sets of transformations that can be used across multiple mappings. They represent a collection of transformations and can be reused. When a mapping containing a mapplet executes, the Informatica Server expands the mapplet inline at runtime.

Test Impact View was introduced as a new feature in VSTS 2010 to help developers understand which tests are affected by code changes. It analyzes code coverage and dependencies to recommend which tests should be run after a code modification. Test View and Test List Editor existed in earlier versions, making Test Impact View the standout new feature in the 2010 release.

To use a WCF service in a test project, you use the "Add Service Reference" option which generates proxy classes and configuration for consuming the service. Add Reference is for .NET assemblies, Add Service as Existing Item adds files to the project, and Add Service as Existing Project adds entire projects - only Add Service Reference properly sets up WCF service connectivity with the necessary proxy generation and configuration.

svcutil.exe generates a service proxy class file (Service.cs) and an output configuration file (output.config) containing endpoint settings when working with WCF services. The other options either use incorrect filenames (Services.cs) or reference the wrong configuration file (App.config is the application's existing config, not the generated one).

Migration planning must start with assessment - understanding the application's architecture, dependencies, controls, and complexity. Jumping straight into tools (Option A) or rewriting (Option C) without assessment risks missing critical dependencies and architectural mismatches. Gathering new requirements (Option D) is premature when the existing requirements aren't understood.

ADO can be used in VB.NET via COM Interop without re-architecting - the .NET framework provides COM interopability to call legacy components. DHTML pages, ActiveX documents, and OLE controls are deeply tied to VB6's runtime model and have no direct .NET equivalents - they require architectural redesign or replacement.

Options A, C, and E are compelling reasons to migrate - they represent technical debt (A), architectural risk (C), and scalability limitations (E). Option B (third-party dependencies) is actually a reason to AVOID migration unless you can replace those controls. Option D (stable business processes) means the application works - if nothing is broken and requirements aren't changing, migration has low ROI.

Visual Basic 2005 included many new features: Debugger ToolTips, code snippets, and snap lines for visual design were all out-of-the-box. Refactoring (extract method, rename, encapsulate field, etc.) was NOT included in VB 2005 - it was added in later versions (available in C# earlier).

The Page_Unload event is the final stage in the ASP.NET Web Forms page lifecycle, occurring after the page has been rendered to the client and just before the page object is discarded from memory. PreRender comes before rendering, LoadComplete happens after Load, and InitComplete occurs after initialization - all well before the final cleanup.

Web Pages in the .NET Framework belong to the System.Web.UI.Page class, which is the base class for all ASP.NET page objects. System.Web.Control is for individual controls, System.Web.UserControl is for user controls, and RootBuilder is an internal parser class, not the page class hierarchy.

XAML (Extensible Application Markup Language) is case-sensitive, like XML upon which it is based. Element names, property names, and attribute values must match the exact casing defined in the XAML schema and CLR types they reference.

In the XAML code, there are two objects: the StackPanel container and the Button control it contains. Content is a property of the Button (set via attribute syntax), not a separate object. The correct answer identifies the actual XAML elements/objects instantiated.