What are the types of ASP.NET projects?

You can create different types of ASP.net projects in Visual Studio 2010 , they are :

1. Web Sites 
2. Web Applications
3. Web Services
4. AJAX  Server

What is Visual Web Developer and its Features?

Visual Web Developer is a full-featured development environment for creating ASP.NET Web applications

It offers the following features:

•  Web Page Design
•  Page Design Features
•  Code Editing
•  Testing and Debugging (A local Web Server for testing and a debugger that helps you find errors in programs)
•  Deployment (Tools to automate typical task for deploying a Web applications to a hosting server or a hosting provider)

 

Testing and Debugging

•  Visual Web Developer provides an ideal environment in which to build Web sites and the npublish them to a hosting site.
•  Visual Web Developer includes a local Web server that provides all the features you need to test and debug ASP.NET Web pages,without requiring IIS to be installed
•  Finally, you can take the advantage of the built-in suppoert for the File Transfer Protocol(FTP), using the Visual Web Developer , you can connect directly to the host computer and then create and edit files on the server

Introduction to ASP.NET 4.0

• ASP.NET is a Web Platform that provides all the services that we require to build server-based Web applications.
• ASP.NET is built upon .NET Framework, so all .NET features are available to ASP.NET applications.
• ASP.NET applications can be written in any language that is compatible with the CLR , including Visual Basic and C#

• To create ASP.NET Web applications , we can use Visual Studio.
• The tools and options in Visual Studio that are designed for creating Web Applications are referred to as 'Visual Web Developer'.

                                     Learn ASP.net 4.0 from msdn : http://msdn.microsoft.com/en-us/library/dd566231.aspx

SharePoint 2010 export 2010 list items to execl

$Web = WebUrl 
$List = Web.Lists["ListName"] 
$Items = $List.Items 

$Items | Select Title | Export-Csv

SharePoint 2010 Powershell

 Get-Help
 Get-Command
 Get-Command -Noun SP* (you get nothing because sharepoint module is not loaded)
 Get-PSSNapin -registered
 Add-PSSnapin Microsoft.Sharepoint.Powershell(to load sharepoint snapin)
 Get-Command -Noun SP* (now you get all powershell SP commands)
 Get-SPServiceApplication
 Get-SPFarm
 Get-SPWebAppliction
 Get-SPSite
 Get-SPFeature (get all features across farm/web application/sites)

SharePoint 2010 Security model

• Understanding SharePoint security model requires understanding the difference between 'Authentication process and Authorization process'
• Authentication is the mechanism by which systems securely identify the user attempting to access a resource 
• Authorization is the mechanism by which a system determines the level of access the authenticated user 

• SharePoint itself does not perform any authentication.
• The authentication process is handled by an underlying authentication system, For example windows authentication is handled by Windows Server and IIS.
• SharePoint only performs authorization to secured sources contained in sites,lists,libraries...
• SharePoint 2010 offers two different authentication mode : Classic authentication mode and Claims-based authentication mode

  Classic mode Authentication:

•  It refers to the integrated windows authentication
•  You cannot configure the form based application if your web application is using Classic mode authentication 
•  You can convert a web application from Classic mode authentication to Claims-based by only using  Powershell Command and it an irreversible process

Claims-based Authentication:

•  SharePoint 2010 is built upon Windows Identity Foundation 
•  It enables authentication from as well as non-windows based system.
•  This also provides the capability to have multiple authentication in a single URL
•  Claim-based authentication is built upon Windows Identity Framework 

How to create Setup project for Office Outlook Add in

http://blogs.msdn.com/b/mcsuksoldev/archive/2010/10/01/building-and-deploying-an-outlook-2010-add-in-part-2-of-2.aspx