.NET Framework Development Quiz - ASP.NET and Windows Forms

In Windows Forms MDI (Multiple Document Interface) applications, child forms are assigned to the MdiParent property of the container form. The parent form (FormD) must have IsMdiContainer set to true. Option B correctly describes setting the MdiParent property on child forms and IsMdiContainer on the parent. Options A and C incorrectly use IsMdiChild which isn't a standard property, and option D incorrectly uses IsMdiParent instead of IsMdiContainer.

The BrowsableAttribute controls whether a property appears in the Properties window at design time. Setting [Browsable(true)] makes it visible, while [Browsable(false)] hides it. DebuggerBrowsable is for debugger display, ComVisible relates to COM interoperability, and DisplayBrowsable is not a standard .NET attribute.

In Windows Forms, the ampersand (&) character before a letter creates an access key (shortcut). Writing "&Go" makes ALT+G trigger the button. The @ prefix in option A is for verbatim strings in C# and doesn't create shortcuts. Using && (option C) would display a literal ampersand. Option D uses @ incorrectly in this context.

The Launch Conditions Editor in Visual Studio setup projects lets you specify prerequisites that must be met before installation proceeds. You can add conditions to check for .NET Framework versions and display messages or redirect users to download the required framework. Registry Editor checks registry values, File System Editor manages file installation, and Required Components Editor isn't a standard deployment editor.

In .NET, calling the Complete() method on a TransactionScope tells the transaction manager that all operations within the scope completed successfully, committing the transaction when the scope is disposed. Properties like Completed or methods like Commit() do not exist on the TransactionScope class.

In ADO.NET SQL parameters, the @ prefix is the standard notation for named parameters in SqlCommand objects. You write "@CustomerName" in the SQL query and then add the parameter value to the Parameters collection. The ? prefix is used by some other database systems (like ODBC), % is typically for wildcards, and # is used in some SQL dialects for temporary tables or comments.

XmlReader provides the core functionality for reading XML documents, while XmlValidatingReader specifically validates against schemas. XmlReader alone can validate when used with schema validation enabled, making it the correct choice for XML-schema validation in .NET.

Installing assemblies into the Global Assembly Cache (GAC) requires administrative privileges and Windows Installer technology. A Setup project builds an MSI installer capable of performing this registration. ClickOnce applications run in a security sandbox and cannot write to the GAC, while XCOPY deployment lacks registration capabilities.

UserControl is designed for creating composite controls by combining existing Windows controls. It provides a container that can host multiple child controls and be reused across applications, while Control is the base class for all controls but doesn't provide composition features.

WebClient provides HTTP functionality for accessing websites in .NET. HttpClient is modern but not available in older .NET versions, while InetClient and SoapClient are not valid .NET classes for web access.

The Web.config file is the primary configuration file for ASP.NET applications, used to store application-level settings, connection strings, custom errors, and global variables. While it can configure IIS web server settings locally, its primary role is managing application configurations rather than the general web browser or server.

SelectedIndexChanged event execution depends on AutoPostBack being True for ListBox controls. AutoEventWireup affects event-wireup behavior, not postback execution, and other options are unrelated to this specific issue.

Visual Studio adds a default event handler for the Click event when adding server controls to a Web Form. Event registration and control members are added manually, while a default class inheritance doesn't happen.

ControlToValidate attribute specifies which control should be validated by the validator control. This is a required attribute for validator controls to work properly in ASP.NET.

When Windows authentication is enabled in ASP.NET, the current request gets a WindowsPrincipal object attached to it via HttpContext.User. This object represents the Windows security context and identity of the user making the request. Option C is incorrect - WindowsDataset is not a security object, and serialization is unrelated to authentication.

All ASP.NET Web Forms inherit from System.Web.UI.Page by default. This base class provides essential functionality for page lifecycle events, view state management, and server controls. Options A and D are incorrect because System.Web.Form and System.Web.UI.Form don't exist in the .NET framework class hierarchy.

Custom controls must override the Render() method to generate their HTML output. This method receives a HtmlTextWriter object that you use to write the control's markup. Options A and B don't exist in the ASP.NET control lifecycle, and overriding constructors is optional, not required for basic control functionality.

@OutputCache enables page output caching with support for varying by parameters, headers, and browser type. The directive offers attributes like VaryByParam, VaryByHeader, and VaryByCustom to control cache variations. Options B, C, and D are not valid ASP.NET directives.

Application.Lock() and Application.UnLock() ensure thread-safe access to Application variables by blocking other requests. Always call Lock() before reading or modifying Application state, then UnLock() afterward. Option C is incomplete - using Lock() alone would permanently block access. Options A and D are not valid Application methods.