Monday, December 21, 2009

WSS 3.0 and MOSS 2007

Introduction


 
This Article describes features of windows SharePoint services (WSS 3.0) and MOSS 2007. It describes basic difference between WSS 3.0 and Moss 2007.

Features of WSS 3.0

 
WSS 3.0 is built on top of ASP.NET, and supports Master Page and Site navigation. It is an application framework. WSS improves team productivity.

 
Team site

 
Primarily designed to facilitate collaboration among teams through web sites Secure, Document centric site, tracking process, sharing document, communicating with colleagues, task list, contact list, discussion forums.

 
Administration model enhancements

 
Windows SharePoint Services 3.0 includes several enhancements to the administration model that helps IT organizations implement management plans and performs administrative tasks more effectively and efficiently.

 
Collaborate Easily and Effectively

 
Windows SharePoint Services 3.0 provide a single workspace for teams to coordinate schedules, organize documents, and participate in discussions-within the organization and over the extranet.

 
Windows SharePoint Services are used as a platform to build rich, flexible, and scalable Web-based applications and Internet sites specific to the needs of your organize.

 
Additional Features come with MOSS 2007

 
Take advantage of its integration with Microsoft Office SharePoint Server 2007 that expands platform services and common framework for document management exposed by Windows SharePoint Services to offer enterprise-wide functionality for records management, search, workflows, portals, personalized sites, and more.

 
Use Microsoft Office SharePoint Designer 2007 to quickly and easily customize SharePoint sites and build reporting tools and applications tailored to specific tasks without writing or deploying new code.

 
My site personal site

 
The My Site personal site gives users an opportunity to aggregate information into "for me," "by me," and "about me."

 
User profiles and profile store

 
Allows each user to store profile information.

 
Audience targeting

 
Enables use of Web Part pages, Web Parts, and content to target distribution lists and groups in addition to SharePoint audiences.

 
InfoPath forms services

 
Available in Microsoft Office SharePoint Server 2007 and Microsoft Office Forms Server 2007 InfoPath forms services make it possible to design Web-capable forms in Microsoft Office InfoPath 2007 and distribute them on corporate intranets, extranets, or the Internet. Users can fill out forms in a browser or HTML enabled Mobile device with no download or client components needed.

 
Business Data Catalog (BDC)

 
Business Data Catalog tightly integrates external data into the Office SharePoint Server 2007 user experience, providing access to external data residing within backed LOB applications, and enabling the display of and interaction with external data through a set of Business Data Web Parts.

 
Difference between WSS 3.0 and MOSS 2007

 
WSS 3.0
  • Windows SharePoint Services (WSS3.0) comes free with Windows Server 2003.  
  • WSS 3.0 offers all the standard site templates to build team sites, document workspaces, blank sites, blogs, wikis, and meeting workspaces.  
  • WSS 3.0 can be used to create people and group lists.  
  • It also serves as a platform for application development. Including such IT resources as portals, team workspaces, e-mail, presence awareness, and Web based conferencing, Windows SharePoint Services enables users to locate distributed information quickly and efficiently, as well as connect to and work with others more productively.

MOSS 2007
  • MOSS is not free and it is installed on top of WSS 3.0.MOSS has both a server cost and a client access license (CAL) cost.  
  • You can integrate WSS 3.0 sites with Access 2007, Excel 2007, Outlook 2007, Word 2007 and PowerPoint 2007.  
  • MOSS 2007 offers business intelligence features that allow you to track key performance indicators and build BI dashboards into your team site.  
  • Moss is used as a super powerful content management system, which aims to provide content management, enterprise content services and enterprise search.  
  • Workflow can also be integrated into MOSS 2007.

 
Moss also offers My Sites, which are individual mini-sites that can be set up to show who in your company you're connected to, what your tasks and skills are, your contact information, and more.MOSS 2007 is the portal system, comparable to SharePoint Portal Server 2003. It brings a wealth of built-in functionality and interoperability to a company's intranet over and above the functions of WSS 3.0.

 
Create Site Collection: Select template will give minimum options it's like Collaboration and Meetings.
Create Site Collection:Select template will give more options it's like Collaboration, Meetings, Enterprise, Custom and Publishing Only WSS 3.0


 
Navigation


 
By default both WSS and MOSS have a simple navigation system that uses tabs across the top to access sites along with the quick launch area on the left hand side to access content element within a site.This information presented in site collection.


 
Windows SharePoint Services 3.0 provides the following new features to improve site


 
Navigation through User-aware links; for example, removing the Settings links for users who cannot make particular changes, a capability that is provided through "link trimming".


 
Breadcrumbs to provide users with additional information about their location within a site collection.


 
Customization of the top navigation bar, ranging from adding and removing links to adding Microsoft JScript drop-down menus and fly-outs, which is provided by new shared navigation and master pages. Such menus can only be enabled by modifying a master page; there is no built-in support for enabling these menus.

 

Customization of the left navigation bar, which includes adding and removing links to adding JScript drop-down menus and fly-outs, which is provided through ASP.NET master pages and navigational controls such as the SiteMapPath, Menu and TreeView controls. Such menus can only be enabled by modifying a master page; there is no out-of-box support for enabling these menus.


 
Common navigation bars provided through master pages.

 
Content Management with work flow

Content Characteristics

Microsoft Windows SharePoint Services 3.0 is designed to host content and applications that support such business needs as communication, collaboration, analysis, process, and knowledge management. Across those diverse functions, not all content is created equal. Imagining a spectrum of content characteristics.


 
Content Database is a SQL server 2005 database that maintain all of the webpage definitions, documents, lists and security information.


 
Structured content Unstructured content

 
Made available for long-term consumption Shorter-term lifecycle

 
Little-to-no support for collaboration Support for collaboration

 
Process-driven Process-driven

 

Work Flow

 

 
Work flow is nothing but automated process.The workflow functionality in Windows SharePoint Services 3.0 is built on the Windows Workflow Foundation (WF), a Microsoft Windows platform component that provides a programming frastructure and tools for development and execution of workflow-based applications.

 

 


 

 

 

 

 
The WF run-time engine provides the services that every workflow application needs, such as sequencing, state management, tracking capabilities, and transaction support.

 

 

 
Document libraries also support an event system that you can tap in to programmatically.These events can call into .net assemblies when new document are placed in a library, modified, or deleted.The version of WSS also comes with its own work flow engine based on WWF (Windows workflow foundation), the engine provides simple work flow process such as document approval out of box.

 

 

 
User can develop more sophisticated workflows using the SharePoint designer (Microsoft front page). We can create custom workflows with visual studio 2005 and harness all the power of .NET Framework

 

 

 
List


 
Task list, list of contacts .Previous version of WSS, list used a different underlying infrastructure than document libraries.

 
In the WSS 3.0 version both are same.List also capable of raising events that you can trap in code. List also can participate workflow process.


 
All the files are uploading in respective share point custom list.

 

 

 

Thursday, December 17, 2009

Export To Excel in Asp.Net

protected void btnExportToExcel_Click(object sender, EventArgs e)
{
DataTable dtOriginal = new DataTable();
dtOriginal = BindDataList(); //Return Table consisting data

//Create Tempory Table
DataTable dtTemp = new DataTable();

//Creating Header Row
dtTemp.Columns.Add("FirstName");
dtTemp.Columns.Add("EmpCode");
dtTemp.Columns.Add("Location");
//double dSalary;
//DateTime dtDate;
DataRow drAddItem;
for (int i = 0; i < dtOriginal.Rows.Count; i++)
{
drAddItem = dtTemp.NewRow();
drAddItem[0] = dtOriginal.Rows[i]["FirstName"].ToString();//FirstName
drAddItem[1] = dtOriginal.Rows[i]["EmpCode"].ToString();//EmpCode
drAddItem[2] = dtOriginal.Rows[i]["Location"].ToString();//Location

//Join Date
//dtDate = Convert.ToDateTime(dtOriginal.Rows[i][2].ToString());
//drAddItem[2] = dtDate.ToShortDateString();

//Salary
//dSalary = Convert.ToDouble(dtOriginal.Rows[i][3].ToString());
//drAddItem[3] = dSalary.ToString("C");

dtTemp.Rows.Add(drAddItem);
}

gvEmployee.DataSource = BindDataList();
gvEmployee.DataBind();
ExportToExcelSheet("EmployeeDetails.xls", gvEmployee);
}

private void ExportToExcelSheet(string strFileName, GridView dg)
{
Response.ClearContent();
Response.AddHeader("content-disposition", "attachment; filename=" + strFileName);
Response.ContentType = "application/excel";
System.IO.StringWriter sw = new System.IO.StringWriter();
HtmlTextWriter htw = new HtmlTextWriter(sw);
dg.RenderControl(htw);
Response.Write(sw.ToString());
Response.End();
}
private DataTable BindDataList()
{
string sql = "SELECT TOP 10 * FROM TBL_EMPLOYEES";
SqlDataAdapter da = new SqlDataAdapter(sql, dataObj.GetConnString());
DataTable dt = new DataTable();
da.Fill(dt);
return dt;
}

public override void VerifyRenderingInServerForm(Control control)
{
// Confirms that an HtmlForm control is rendered for the
// specified ASP.NET server control at run time.
// No code required here.
}

Tuesday, December 8, 2009

WCF on IIS7 on Vista or Windows 7 - Adding .svc Handler

WCF on IIS7 on Vista or Windows 7 - Adding .svc Handler

I’ve just formatted and reinstalled my computer yesterday. When I started to build a WCF Service on IIS 7 on my Vista machine, I got the following message:

Server Error in Application “Default Web Site/...”
HTTP Error 404.3 - Not Found



The page you are requesting cannot be served because of the extension of the configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.

This is what I did to have it work:

Start the command window (cmd) as an Administrator.
Navigate to:
C:\windows\Microsoft.Net\Framework\v3.0\Windows Communication Foundation\

In case you are running on a 64Bit machine, than navigate to: C:\windows\Microsoft.Net\Framework64\v3.0\Windows Communication Foundation\


Run the following command: ServiceModelReg –i

After some messages on the console window…




your service should now work.

Saturday, December 5, 2009

Installation Tips for Silverlight Tools Beta 1 for Visual Studio 2008

Installation Tips for Silverlight Tools Beta 1 for Visual Studio 2008
Published Thursday, March 06, 2008 1:52 AM
As many of you know Silverlight 2 Beta 1 was release today at MIX08. What an awesome day. The new applications under development based on Silverlight 2 are truly incredible! Check out http://www.microsoft.com/silverlight/
To get started with Silverlight 2 you can download "Silverlight Tools Beta 1 for Visual Studio 2008" here.
The Silverlight Tools installer will install everything needed to start working with Silverlight 2 in Visual Studio 2008.
It installs the following:
• Silverlight 2 Beta 1
• Silverlight 2 SDK Beta 1
• KB949325 for Visual Studio 2008
• Silverlight Tools Beta 1 for Visual Studio 2008
Even if you've previously installed Silverlight 1.0 or Silverlight 2 Beta 1 the installer will proceed and install the additional components.
That's it! You're now ready to start creating rich Internet applications with Silverlight 2 and Visual Studio 2008.
While the installation is that simple in most cases, there have been some installation issues reported. I've listed below the issues and solutions I've run into so far. I'll update this post if new issues are reported.
Installation Error
If you do run into an installation error, it's most like due to a previous installation of Silverlight 1.1 Alpha or any of the Silverlight SDKs, including the Silverlight 2 Beta 1 SDK. You must uninstall all these components before installing Silverlight Tools Beta1 for VS08. If you don't uninstall these products first you'll get this error dialog from the installer.

If you see this dialog, be sure to uninstall all the dependent components and restart the installer.
Can't Find KB949325 to Uninstall?
If you ever need to uninstall KB949325, you can do this through Add and Remove Programs. However it does not show up by default in Add and Remove Programs.
Instead you need to select "View Installed Updates"

Now you'll see all the updates and patches installed to applications on your computers. Scroll down and you'll find KB949325. It will be listed as:

It should not come as a surprise that if you uninstall KB949325, you will not be able to use Silverlight projects in Visual Studio. Only uninstall KB949325 if you're planning on returning VS08 to its RTM condition or if you're attempting to reinstall Silverlight Tools.
Prompt for installation source media
In some cases you may get a prompted for the installation CD-ROM for Visual Studio 2008.

Heath Stewart has an excellent blog post on some of the issues users are encountering when installing patches for Visual Studio 2008. You can read his entire post here. Heath has a new post specific to this prompt when installing Silverlight Tools here.
One of the scenarios causing this to happen with the Silverlight Tools installer is when Visual C++ is not installed. The other component that will cause this to happen is if you don't have the "Microsoft Visual Studio Web Authoring Component".
You can manually get around this. First you'll need to extract the individual installers from the Silverlight Tools Beta 1 for VS08 chained installer. To do this download and save the Silverlight Tools chained installer from here and save it locally.
To extract the individual installers run this command: silverlight_chainer.exe /extract
This will extract the following installers, along with other support files.
1. Silverlight.2.0.exe
2. VS90-KB949325.msp
3. silverlight_sdk.msi
4. VS_SilverlightTools_Beta1_Setup.exe
It critical that you install these components in the order listed above. (Silverlight 2, KB949325, SDK, Tools) To install KB949325 w/o being prompted for media run this command:
msiexec /p VS90-KB949325.msp /L*vx VS90-KB949325.log REINSTALL=ALL
Note: this command will require administrative rights and it does not add the KB to Add/Remove Programs.
To list these Silverlight tools in Visual Studio's Help->About dialog and to be able to uninstall these tools from Add/Remove Programs (ARP), install the patch again using the following command:
msiexec /p VS90-KB949325.msp /L*vx VS90-KB949325-2.log ADDLOCAL=KB947520,KB949325
Finally run the VS_SilverlightTools_Beta1_Setup.exe installer to complete the Silverlight Tools installation.
The project type is not supported by this installation
Even when installed successfully, some users have seen this error:



This is happening for users who have installed previous builds of Silverlight Tools and for one reason or another the Silverlight package for Visual Studio has been disabled. You can re-enable the Silverlight package by running the following command.
devenv.exe /resetskippkgs
The ASP.NET Silverlight controls show appear in the Toolbox for .aspx pages
This happens if the Silverlight SDK is installed before KB949325. As listed above the install order is important. To fix this uninstall the Silverlight SDK and re-install it.
Help Files don't show up in Visual Studio
To integrate the VS help files included in the Silverlight 2 SDK follow the instructions in this readme.txt installed with the SDK.
[Program Files]\Microsoft SDKs\Silverlight\v2.0\Documentation\VS-Help\Readme.txt
The installer is hung?
At the end of the installation process the installer appears to be hung.

The installer can take up to 10 minutes at the end of the installation process. What's going on? The last thing the installer does is merge the help dictionaries. If you've installed the help files for VS locally this can take some time. Don't kill the process, it's not hung.
Where to go for Installation Help?
Be sure to check out the Silverlight 2 Beta 1 readme for known issues.
If you run into installation issues not covered here please post your question in the "Installation and Setup" forum here: http://silverlight.net/forums/13.aspx