ASP.NET 3.5 Interview questions

My organization went through the approval process of supporting the .NET Framework 2.0 in production. Do we need to go through the same process all over again for the .NET Framework 3.0? Do I need to do any application compatibility testing for my .NET Framework 2.0 applications? Because the .NET Framework 3.0 only adds new components to the .NET Framework 2.0 without changing any of the components released in the .NET Framework 2.0, the applications you've built on the .NET Framework 2.0 will not be affected. You don’t need to do any additional testing for your .NET Framework 2.0 applications when you install the .NET Framework 3.0.

When you install the .NET Framework 3.0, the installer will check to see whether you already have the .NET Framework 2.0 (released version) installed. If not, the .NET Framework 3.0 installer will install the .NET Framework 2.0 for you, and then install the new .NET Framework 3.0 components. If you do have the .NET Framework 2.0 installed, the .NET Framework 3.0 installer will only install the new components of the .NET Framework 3.0.

The .NET Framework 3.0 is an additive release to the .NET Framework 2.0. The .NET Framework 3.0 adds four new technologies to the .NET Framework 2.0: Windows Presentation Foundation (WPF), Windows Workflow Foundation (WF), Windows Communication Foundation (WCF), and Windows CardSpace. There are no changes to the version of the .NET Framework 2.0 components included in the .NET Framework 3.0. This means that the millions of developers who use .NET today can use the skills they already have to start building .NET Framework 3.0 applications. It also means that applications that run on the .NET Framework 2.0 today will continue to run on the .NET Framework 3.0. Here's a look at the structure of the .NET Framework 3.0:

The WinFX technologies will now be released under the name .NET Framework 3.0. There are no changes to the WinFX technologies or ship schedule the same technologies you're familiar with now simply have a new name.

The .NET Framework 3.0 is Microsoft's managed code programming model. It is a superset of the .NET Framework 2.0, combining .NET Framework 2.0 components with new technologies for building applications that have visually stunning user experiences, seamless and secure communication, and the ability to model a range of business processes. In addition to the .NET Framework 2.0, it includes Windows Presentation Foundation (WPF), Windows Workflow Foundation (WF), Windows Communication Foundation (WCF), and Windows CardSpace.

Windows SharePoint Services is a component of Windows Server 2003 and conforms to the Windows Server 2003 licensing model. Organizations simply need to own Windows Server 2003 licenses to have the rights to also use Windows SharePoint Services. Learn more about licensing Windows Server 2003 and Windows SharePoint Services on the SharePoint licensing page .

Windows SharePoint Services is a key component of Microsoft SharePoint Products and Technologies, which include: Windows SharePoint Services , formerly named SharePoint Team Services, a versatile technology in Windows Server 2003. In addition to its collaborative features, Windows SharePoint Services also exposes platform services and a common framework for document storage and management, as well as search, workflow, rights management, administration, and deployment features. These services provide the foundation for building scalable business applications. Office SharePoint Server 2007 , an integrated suite of easy-to-use server applications that help people and teams improve their efficiency and effectiveness. Office SharePoint Server 2007 connects sites, people, and business processes—facilitating knowledge sharing by offering ready-to-go, enterprise-wide functionality for records management, search, workflows, portals, personalized sites, and more. Office SharePoint Server 2007 ex

Through a set of Web services and documented application interfaces, Windows SharePoint Services can be easily integrated with smart client tools. Users easily adopt these new tools because of their similarity to other familiar environments, such as the Microsoft Office system. For example, Microsoft Office Word, Microsoft Office Excel, Microsoft Office PowerPoint, Microsoft Office InfoPath, Microsoft Office Project, and Microsoft Office OneNote can use information in SharePoint sites natively. Users can create workspaces, post and edit documents, and assign tasks, all while working on documents stored in SharePoint sites. With Microsoft Office Outlook 2007, users can view calendars and contact lists stored on SharePoint sites and can create and manage sites for editing documents and organizing meetings.

Windows SharePoint Services 3.0 offers many new and enhanced features that help business organizations of all sizes further improve individual and team productivity, and the efficiency of their business processes. These new and improved features help employees to implement and manage workspaces and team sites more easily without help from IT, simplify and improve the management and maintenance of documents stored on SharePoint sites, and provide more robust and easy-to-use collaboration tools that encourage information sharing within the organization. Windows SharePoint Services 3.0 also provides IT departments with enhanced control of company resources and a more flexible and robust foundation for building new, Web-based applications and services that can connect to and capitalize on existing line-of-business applications.

Key improvements to Windows SharePoint Services in Version 3.0 include: Improvements to collaboration workspaces: SharePoint sites now offer e-mail and directory integration, alerts, RSS publishing, templates for building blogs (also known as weblogs) and wikis (Web sites that can be quickly edited by team members—no special technical knowledge required), event and task tracking, improved usability, enhanced site navigation, and more. Enhancements to content storage: SharePoint lists and libraries now provide per-item security for better data control and integrity, a recycle bin, and enhanced flexibility for storing more types of content. Row and column capacity has also been increased, as has retrieval speed. Windows SharePoint Services 3.0 can be easily integrated with smart client tools. In particular, close integration with Microsoft Office Outlook 2007 provides offline access to events, contacts, discussions, tasks, and documents. Easier provisioning of workspaces: Windows Shar

Windows SharePoint Services offers you benefits in four primary areas: Efficient collaboration: Help your employees and teams to stay connected and productive by providing access to the people, documents, and information they need. Rapid deployment, ease of use: Deploy collaboration applications quickly that are easy to use through integration with familiar productivity tools such as the Microsoft Office system. Manageable infrastructure: Manage the security of your organization’s information resources by deploying a scalable storage infrastructure with powerful administration services and controls. Robust foundation platform for Web-based applications: Increase business process efficiency by creating Web applications and workflow scenarios on a cost-effective, extensible platform.

Windows SharePoint Services is a technology that enables people to collaborate in browser-based workspaces while providing a manageable infrastructure and extensible application platform for improving the efficiency of business processes. A variety of audiences benefit from the enhanced collaboration and productivity provided by Windows SharePoint Services: Organizations, business units, and teams seeking increased productivity and access to the people, documents, and information they need. Organizations of any size that want to start tactical implementation of collaboration tools, standardize existing infrastructure, or invest in strategic use of collaboration systems that integrate well with existing line-of-business applications. IT departments seeking better control over and security of company data, while adding value and efficiency to lines of business. Developers creating rich and scalable Web-based applications.

Windows SharePoint Services is a versatile technology included in Microsoft Windows Server 2003 that enables organizations and business units of all sizes to increase the efficiency of business processes and improve team productivity. With tools for collaboration that help people stay connected across organizational and geographic boundaries, Windows SharePoint Services gives people access to documents and information they need. With a familiar, Web-based interface and close integration with everyday tools including the Microsoft Office system of productivity programs, Windows SharePoint Services is easy to use and can be deployed rapidly. Users can create workspaces and then publish, store, share, and keep track of information, workflow, and documents. Built on Microsoft Windows Server 2003, Windows SharePoint Services also gives organizations a cost-effective foundation platform for building Web-based business applications that can scale easily to meet the changing and growing needs

View QUESTION View QUESTION 2 View You work as the application developer at Certkille... View What's New in ASP.NET View ASP.NET Overview View What's New in Visual Studio 2008 View Improve Application Life-Cycle Management (ALM) View Better Developer Experience View Enable New Web Experiences View Handle Data More Productively View Build Windows Vista Applications View Create Microsoft Office Applications View Develop Smart Client Applications View Overview of Microsoft Visual Studio 2008

View Professional ASP .Net page 3 Professional ASP .Net View Professional ASP .Net page 2 Professional ASP .Net View Professional ASP .Net Professional ASP .Net View SQL Server 2000 FAQs View .Net Interview Prepration FAQs View Inside C# FAQs View Dot Net Framework Essentials FAQs View Developing Web Application With VB .Net And C# .Ne... FAQs View Interview Work Exam For .Net Programmer Interview Work Exam For .Net Programmer View Interview Questions On .Net Interview Questions On .Net View Interview Questions .Net Interview Questions .Net View Interview Questions For .Net

View What's New in ASP.NET and Web Development asp.NET 3.5 View Preprocess Win32 Messages through Windows Forms c# Interview Question View Is it possible to output the command-line used to ... c# Interview Question View How do I get and set Environment variables? c# Interview Question View How do I create a constant that is an array? c# Interview Question View What is the difference between const and static re... c# Interview Question View How can I easily log a message to a file for debug... c# Interview Question View How do I play default Windows sounds? View How do I calculate a MD5 hash from a string? c# Interview Question View How do I send out simple debug messages to help wi... c# Interview Question View What's the

The .NET Framework version 3.5 includes enhancements for ASP.NET in targeted areas. Visual Studio 2008 and Microsoft Visual Web Developer Express Edition also include enhancements and new features for improved Web development. The most significant advances are improved support for developing AJAX-enabled Web sites and support for Language-Integrated Query (LINQ). The advances include new server controls and types, a new object-oriented client type library, and full IntelliSense support in Visual Studio 2008 and Microsoft Visual Web Developer Express Edition for working with ECMAScript (JavaScript or JScript). The following sections of this topic describe the changes in ASP.NET and Visual Web Developer. ASP.NET Enhancements Visual Web Developer Enhancements ASP.NET Enhancements The .NET Framework version 3.5 includes enhancements for ASP.NET in the following areas: New server controls, types, and a client-script library that work together to enable you to

In the unmanaged world, it was quite common to intercept Win32 messages as they were plucked off the message queue. In that rare case in which you wish to do so from a managed Windows Forms application, your first step is to build a helper class which implements the IMessageFilter interface. The sole method, PreFilterMessage(), allows you to get at the underlying message ID, as well as the raw WPARAM and LPARAM data. By way of a simple example: public class MyMessageFilter : IMessageFilter { public bool PreFilterMessage(ref Message m) { // Intercept the left mouse button down message. if (m.Msg == 513) { MessageBox.Show("WM_LBUTTONDOWN is: " + m.Msg); return true; } return false; } } At this point you must register your helper class with the Application type: public class mainForm : System.Windows.Forms.Form { private MyMessageFilter msgFliter = new MyMessageFilter(); public mainForm() { // Register message filter. Applicati

Now that Whidbey has been out in Beta for more than a few months, it seems worth revisiting some frequently asked questions which have different (better?) answers now. In Everett (v7.1) the answer used to be No. However, in Whidbey (v8.0), the answer is Yes (and No). For the yes part of the answer, after building, go to the Output Window, select "Show Output from: Build", and about half way down you will see a section like this: Target "Compile" in project "ConsoleApplication1.csproj" Task "Csc" Csc.exe /noconfig /warn:4 /define:DEBUG;TRACE /debug+ /optimize- /out:obj\Debug\ConsoleApplication1.exe /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.31125\System.Data.dll, C:\WINDOWS.0\Microsoft.NET\Framework\v2.0.31125\System.XML.dll, C:\WINDOWS\Microsoft.NET\Framework\v2.0.31125\System.dll /target:exe /win32icon:App.ico AssemblyInfo.cs Class1.cs The task is invoking the IDE's in-process compiler to perform the equivalent of the above command-l

Use the System.Environment class.Specifically the GetEnvironmentVariable and SetEnvironmentVariable methods. Admitedly, this is not a question specific to C#, but it is one I have seen enough C# programmers ask, and the ability to set environment variables is new to the Whidbey release, as is the EnvironmentVariableTarget enumeration which lets you separately specify process, machine, and user.

Strictly speaking you can't, since const can only be applied to a field or local whose value is known at compile time. In both the lines below, the right-hand is not a constant expression (not in C#). const int [] constIntArray = newint [] {2, 3, 4}; // error CS0133: The expression being assigned to 'constIntArray' must be constant const int [] constIntArrayAnother = {2, 3, 4}; // error CS0623: Array initializers can only be used in a variable or field // initializer. Try using a new expression instead. However, there are some workarounds, depending on what it is you want to achieve. If want a proper .NET array (System.Array) that cannot be reassigned, then static readonly will do for you. static readonly int [] constIntArray = new int[] {1, 2, 3}; The constIntArray field will be initialized before it its first use. If, on the other hand, you really need a const set of values (say as an argument to an attribute constructor), then - if you can limit yourself

The difference is that the value of a static readonly field is set at run time, and can thus be modified by the containing class, w hereas the value of a const field is set to a compile time constant. In the static readonly case, the containing class is allowed to modify it only in the variable declaration (through a variable initializer) in the static constructor (instance constructors, if it's not static) static readonly is typically used if the type of the field is not allowed in a const declaration, or when the value is not known at compile time. Instance readonly fields are also allowed. Remember that for reference types, in both cases (static and instance) the readonly modifier only prevents you from assigning a new reference to the field. It specifically does not make immutable the object pointed to by the reference. class Program { public static readonly Test test = new Test (); static void Main ( string [] args) { test.Name = "Program"; test = new T

Often, you need a way to monitor your applications once they are running on the server or even at the customer site -- away from your Visual Studio debugger. In those situations, it is often helpful to have a simple routine that you can use to log messages to a text file for later analysis. Here’s a simple routine that has helped me a lot for example when writing server applications without an user interface: using System.IO; public string GetTempPath() { string path = System.Environment.GetEnvironmentVariable("TEMP"); if (!path.EndsWith("\\")) path += "\\"; return path; } public void LogMessageToFile(string msg) { System.IO.StreamWriter sw = System.IO.File.AppendText( GetTempPath() + "My Log File.txt"); try { string logLine = System.String.Format( "{0:G}: {1}.", System.DateTime.Now, msg); sw.WriteLine(logLine); } finally { sw.Close(); } } With th