Software Development and Management

WebParts can be closed by users and removed permanently by page owners. They can also be minimized to reduce screen space while remaining on the page. WebParts cannot be individually disabled - they must be closed or removed from the page.

Feature.xml defines the feature itself including properties and activation scope. Elements.xml contains the feature's actual elements like site columns, content types, or list templates. Schema.xml defines list views and forms, while Manifest.xml is for solution packages.

The Microsoft.SharePoint.dll is located in the ISAPI folder under the 12 hive: 'Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI'. This is the correct location to add references when developing SharePoint solutions.

Email alert templates in SharePoint 2007 are stored in and can be modified through the AlertTemplates.xml file located in the SharePoint hive. This file contains all the email notification templates used by SharePoint alerts.

When files are edited using SharePoint Designer, they become customized files stored in the Content Database rather than on the file system. This customization model allows SharePoint to maintain version history and track unghosted (customized) pages separately from the site definition files on disk.

When resetting a customized page to site definition: (A) Any Web Part Zones added during customization are removed, (B) Web Parts within zones that existed in the original site definition retain their content because those zones are part of the template, (D) Additional Web Parts added to original zones are not removed. Option C is incorrect because custom zones are indeed removed during reset.

When creating a Site Collection named 'zzz' based on the Team Site template, SharePoint automatically creates three default SharePoint groups: zzz Members (Contribute permissions), zzz Owners (Full Control permissions), and zzz Visitors (Read permissions). There is no 'zzz Readers' group created.

SharePoint Features require two XML files: Feature.xml contains metadata (name, ID, scope, description) and Elements.xml contains the feature's actual definitions (lists, modules, content types). Schema.xml is for list definitions, not features. Manifest.xml is not a SharePoint term.

When resetting a customized page to site definition: (A) Web Part Zones added to the customized page are removed, (B) Contents of Web Parts that were part of the original site definition are not changed, and (D) Additional web parts added in zones from the original definition are not removed. Option C is incorrect because added zones ARE removed during reset.

When creating a Site Collection named 'zzz' using the Team Site template, SharePoint automatically creates three groups: zzz Members (for contributors), zzz Owners (for administrators), and zzz Visitors (for readers). There is no 'Readers' group - that's what Visitors is for.

To create a feature in SharePoint 2007, you need two XML files: Feature.xml (which defines the feature itself - its ID, name, scope, etc.) and Elements.xml (which defines what the feature does - the actual elements like site columns, content types, etc.). Schema.xml is for list definitions, Manifest.xml is not used for features.

ASP.NET stores session IDs in cookies by default, allowing the server to identify users across HTTP requests. Option B is correct - cookies are the default storage mechanism for session IDs. Options A, C, and D represent alternative storage methods but are not the default behavior.

IIS (Internet Information Services) is not required to develop ASP.NET 2.0 web applications. You can develop and test ASP.NET applications locally using the built-in ASP.NET Development Server (Cassini) or Visual Studio's built-in web server without needing IIS installed on your development machine.

In ASP.NET page lifecycle, Init() is the first method fired during page load, followed by Load(), then other events like PreRender(). Unload() is called much later when the page is destroyed.

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.