A Krunal Jani's Blog

Problem  At some point SharePoint developers will need to trace, log and debug their code when they get tripped up with bugs or any weird things when building custom solutions, applications, or components for SharePoint. Solution SharePoint hides the real detailed error messages and debug /tracing information which relate to the error. In order to display it we can debug SharePoint Applications & Solutions using the detailed steps below:  Enable debug information and tracing over bugs and exceptions on WSS (Windows SharePoint Services) 3.0 & MOSS (Microsoft Office SharePoint Server) 2007 -  Part 1 . Enable debug information and tracing over bugs and exceptions on SharePoint 2010 -  Part 2 . Enable debug information and tracing over bugs and exceptions on SharePoint 2010 : In WSS 3.0 / MOSS 2007, to allow debugging, we have to modify only the  Web.Config  which relates to your web application. But in SharePoint 2010, we have to modify two different Web.Config file

You can greatly simplify debugging by using Visual Studio extensions for Windows SharePoint Services. This topic includes procedures that explain the following: Debugging with Visual Studio extensions for Windows SharePoint Services Performing manual debugging Performing remote debugging Debugging with Visual Studio extensions for Windows SharePoint Services Press the F5 key to begin debugging with Visual Studio extensions for Windows SharePoint Services. The following procedure demonstrates how to enable F5 debugging. To enable F5 debugging Locate and open the target SharePoint application's Web.config file. By default, it is located in C:\Inetpub\wwwroot\wss\VirtualDirectories\80. Find the following line of code and change the  debug  attribute to  true . Save the changes to the Web.config file. In Visual Studio, right-click the SharePoint project, and then click  Properties . Click the  Debug  tab, and then type the target SharePoint URL in t

Allow Debugging for SharePoint Problem At some point SharePoint developers will need to trace, log and debug their code when they get tripped up with bugs or any weird things when building custom solutions, applications, or components for SharePoint.             Solution SharePoint hides the real detailed error messages and debug /tracing information which relate to the error. In order to display it we can debug SharePoint Applications & Solutions using the detailed steps below : Enable debug information and tracing over bugs and exceptions on WSS (Windows SharePoint Services) 3.0 & MOSS (Microsoft Office SharePoint Server) 2007 -  Part 1 . Enable debug information and tracing over bugs and exceptions on SharePoint 2010 -  Part 2 . 1.  Enable debug information and tracing over bugs and exceptions on WSS (Windows SharePoint Services) 3.0 & MOSS (Microsoft Office SharePoint Server) 2007: We can allow debugging/tracing in SharePoint 2007 by using the multiple

Prerequisites for migrating SharePoint 2007 site to SharePoint 2010: 1. Check  whether the  packages  (wsp features etc) in  source  server are same as in the target server (if not please install). 2.  Check  the web.config modifications made in the MOSS 2007 site (source site), if any do the same modifications on MOSS 2010 site (target site) accordingly. Migration process: The only process to migrate the site from SharePoint 2007 to SharePoint 2010 is the migrating contentDB of source site to target site. Steps to follow for migrating ContentDB: 1. Take the backup of the source site contentDB and restore the same on target server. 2. Create the web  application  in SharePoint 2010, and then create the site collection (it doesn’t matter what site template you are using for creating site collection). 3. Once finished creating the SharePoint 2010 site, go to central administration --> Manage content  databases  --> select the web application you created for migration --

Configuring Sharepoint service provider is one of the important task when you are setting up a sharepoint server (MOSS 2007). The following steps will help you in creating and configuring SSP. What are the prerequisites for configuration? The important one is the user account . More details use the link- http://technet2.microsoft.com/Office/en-us/library/f07768d4-ca37-447a-a056-1a67d93ef5401033.mspx?mfr=true Configuring the SSP (Shared Service Provider) 1. Start > Programs > Microsoft Office Server > SharePoint 3.0 Central Administration > menu from the application server. This will open SharePoint central administration site in internet explorer. 2. In SharePoint central administration site click on Shared Service Administration, this will open Share service administration page. 3. Click on New SSP 4. Click on Create a new Web Application 5. Select Create a new IIS web site. 6. Give a Port number other than 80 7. Select NTLM under Authentication p