Sharepoint and .NET

Search Using JSOM – SharePoint 2013

2014-11-19T00:06:00.000-08:00

We can use JSOM for Keyword query search in SharePoint 2013. I’ll explain basics of this using a CEWP and jquery.

Prerequisites: Search should be configured and working in the system.
Solution:

Create a web part page in your SharePoint 2013 or Office 365 SharePoint Site.
Add Content Editor web part on the page.

3. Open any text editor/visual studio and write JS file ‘Search_JSOM.js’, code is copied below:

JS explained:
JS starts with required script references (jquery, sp.js, sp.search.js etc.) and style for search results table. Followed by java script function ‘executeSearch’ to get client context, read ‘keyword’ and then execute search query on keyword. ‘onQuerySuccess’ function will handle success case and create a table with search results that will be displayed on the page. ‘onQueryFailed’ will display error message if ‘executeQueryAsync’ fails. Finally a text box to provide ‘keyword’, button to search and div for search results are added as html.

4. Now upload this ‘Search_JSOM.js’ to site assets or any other library of SharePoint site.
5. Edit Content Editor Web part on page and provide URL of ‘Search_JSOM.js’ file as Content Link. Save the page, it will look like:

6. Enter a valid text which exists in SharePoint and already crawled, and click on search button; relevant results will be displayed as a table.

Thank you...

Customize Display templates – SharePoint 2013 & SharePoint Online

2014-11-17T20:35:00.002-08:00

In SharePoint 2013 we have display templates to handle the display of search results in web parts. I would recommend to read this msdn article to understand display templates first.

I will give a walk through on how do we customize a display template for a particular requirement (in this case to display e-mail address of person).

Prerequisites: Search should be configured and working in the system.

Solution:

1. Create a web part page “MySearch.aspx”, and added “Search Box” & “Search Results” web parts.

2. Configure both the web parts that search box query goes to search result.

3. Go to Site Settings -> Master Page Gallery -> Display Templates -> Search

4. Download “Item_Person.html” file, the display template for People Item.

5. Change html to display Email – add the highlighted code as below:

6. Upload the updated file to display template library and publish the file.

7. Go to the MySearch page -> Edit Page-> Edit ‘Search Results’ Web part

8. Under ‘Display Templates’, chose ‘Use a single template to display items’ and select ‘People Item’.

9. Save and exit the Page.

10. Search name in search box, it should return email id with People data.

PowerShell: Script to update solution

2014-07-06T00:37:00.000-07:00

Solution deployment is one important task for SharePoint developer/admin, being it in local environment or any other Production/non-production farm.

Here is a script to automate this job and avoid errors. Only manual task here is to provide “Variable Values”, i.e. – name of WSP, path, web application URL etc.

In this case WSP is already added to farm solution store and deployed. We did some changes in existing code and need to update the solution. The Update-SPSolution cmdlet upgrades a deployed SharePoint solution in the farm. Use this cmdlet only if a new solution contains the same set of files and features as the deployed solution. If files and features are different, the solution must be retracted and redeployed.

1. Copy the script below, save it as PS file, i.e. – UpdateSolution.ps1

2. Edit it in any compatible editor; change Declaration of the Variables section as per your requirement.

3. Open PS prompt/SharePoint management Shell with admin rights.

4. Navigate to the folder where PS file is saved

5. Execute the PS file as .\UpdateSolution.ps1

# ***********Script Start*********************************************

## Function – Solution Update

## Author – Deepak Solanki (deepaksinghsolanki@gmail.com)

## Version – 1.0

## Checks to ensure that Microsoft.SharePoint.Powershell is loaded, if not, adding pssnapin

## Checks if solution is already exists or deployed in Farm and give appropriate message

## The Update-SPSolution cmdlet upgrades a deployed SharePoint solution in the farm.

## Use this cmdlet only if a new solution contains the same set of files and features as the deployed solution.

## If files and features are different, the solution must be retracted and redeployed.

# ********************************************************************

#########################Declaration of the Variables###############################

#Solution Name

$SolutionName = “MySolution.wsp”;

#Literal Path

$SolutionPath = “C:\Deployment\MySolution.wsp”;

############################ Declaration of the (helper) function # ####################

Function UpdateSolution([string] $SolutionName, [string] $SolutionPath)

{

if($SolutionName.ToLower().EndsWith(“.wsp”) -and $SolutionPath.ToLower().EndsWith(“.wsp”))

{

$count = 0

##check to ensure that Microsoft.SharePoint.Powershell is loaded

$snapin = get-pssnapin | where-object{$_.Name -eq “Microsoft.SharePoint.Powershell”} if($snapin -eq $null)

{

write-host “Loading SharePoint snapin”

add-pssnapin “Microsoft.SharePoint.Powershell” }

##check if WSP already exists in Farm

$WSPExist = Get-SPSolution | Where { ($SolutionName -eq $_.Name)}

if($WSPExist -eq $null)

{

Write-Host “$SolutionName Solution does not exist in solution store, can not be updated.” -ForegroundColor Red

}

elseif ((Get-SPSolution $SolutionName).Deployed)

{

Write-Host “$SolutionName Solution already exists in solution store and has been deployed. Starting update…” -ForegroundColor Green

$SolutionTocheck = Get-SPSolution -identity $SolutionName

if ($SolutionToCheck.ContainsGlobalAssembly)

{

Update-SPSolution -Identity $SolutionTocheck -LiteralPath $SolutionPath -GACDeployment

}

else

{

Update-SPSolution -Identity $SolutionTocheck -LiteralPath $SolutionPath

}

Write-Host “Operation completed.”

}

else

{

Write-Host “$SolutionName Solution exists in solution store but has not been deployed, can not be updated” -ForegroundColor Red

}

else

{ Write-Host “Please provide a valid parameter” -ForegroundColor Red }

}

############################Actual Function Call # ###########################

UpdateSolution $SolutionName $SolutionPath;

# ***********Script End here*****************************

PowerShell – Reading from CSV file

2014-07-06T00:25:00.002-07:00

Reading from a csv, and doing some operation on the records returned by csv is one of the most common tasks in PowerShell. I’ll try to explain different cases here with sample code.

Below is the sample csv file “Sourcedata.csv” we’ll be using as example

TaskID, AssignTo, Duration

001, Tom, 55

002, Rand, 230

003, Mat, 86

##Script Starts here

##First declare a variable to store full path of csv file

$SourceFile = “C:\Sourcedata.csv”;

##Use Test-Path to ensure that given file exists

if(Test-Path $SourceFile)

{

## Case 1 – Read the full CSV file and store result in a variable

$allRecords = Import-csv -path $SourceFile

##Case 2 – If csv has huge data and you want selected rows only, you can filter data with where condition

$selectedRecords = Import-csv -path $SourceFile|Where-Object {$_.AssignTo.Contains(“Rand”)}

##Case 3- If csv has data but no column headers and you want to put headers in order to manipulate data later, you can add headers while importing csv

$allRecordswithHeader = Import-csv -Header TaskID, AssignTo, Duration -path $SourceFile

#Now you have data with you and want to start operations on each of the row, simple- iterate through records

foreach($record in $allRecords)

{

$assignTo = $record.AssignTo;

Write-Host $assignTo

## Do your operation here..

}

##Script Ends here

Happy scripting

PowerShell : Create Managed Properties in SharePoint Search Service Application

2014-07-06T00:13:00.002-07:00

A common requirement in SharePoint search is to create Managed Properties and map it to crawled properties so that it can be used in search query.

Below is the approach to write a PS script that can be used to create one or more managed properties using an input XML file.

1. Create an xml file ‘ManagedProperties.xml’ as below and provide details.

2. Write the script in any suitable editor and save it as ”ManagedProperties.ps1′

# ******************************************************************* #

# Function – ManagedProperty Creation #

# Author – Deepak Solanki [deepaksinghsolanki@gmail.com]

# ********************************************************************

######################################################

# make sure to load SharePoint snapin if not defined #######################################################[System.reflection.Assembly]::LoadWithPartialName(“Microsoft.SharePoint”)

$snapin=”Microsoft.SharePoint.PowerShell”

if (get-pssnapin $snapin -ea “silentlycontinue”)

{

write-host -f Green “PSsnapin $snapin is loaded”

}

elseif (get-pssnapin $snapin -registered -ea “silentlycontinue”)

{

write-host -f Green “PSsnapin $snapin is registered” Add-PSSnapin $snapin write-host -f Green “PSsnapin $snapin is loaded”

}

else

{

write-host -f orange “PSSnapin $snapin not found” -foregroundcolor Red

}

#################################################################

# Function definition #

function createManagedProperty($xmlFile,$searchApplicationName)

{

$configXml = [xml]( get-content $xmlFile)

$searchapp = Get-SPEnterpriseSearchServiceApplication $searchApplicationName

$category = Get-SPEnterpriseSearchMetadataCategory -Identity SharePoint -SearchApplication $searchapp

foreach($metaProp in $configXml.managedproperties.managedproperty)

{

Write-Host -ForegroundColor Green “Creating property: ” $metaProp.Name $crawledPropName = $metaProp.crawlproperty

##Check if Managed property already exist

$ManagedProp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Identity $metaProp.name -ErrorAction SilentlyContinue

##Delete existing managed property

if($ManagedProp -ne $null)

{

$ManagedProp.DeleteAllMappings()

Remove-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Identity $metaProp.name -Confirm:$false

}

else

{

##Create Managed property

New-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Name $metaProp.name -Type $metaProp.type -Queryable $true -Retrievable $true

}

$ManagedProp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Identity $metaProp.name

##Check if Crawled Property is available

$crawledproperty = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $searchapp -Name $crawledPropName -ErrorAction SilentlyContinue

##Map managed property to crawl property

if($crawledproperty -ne $null)

{

New-SPEnterpriseSearchMetadataMapping -SearchApplication $searchapp -ManagedProperty $ManagedProp -CrawledProperty $crawledproperty

}

else

{

Write-Host -ForegroundColor Red “Crawled property does not exist: ” $crawledPropName

}

###########################################

# Declaration of the constants #

###########################################

$SearchApplicationName = “Search Service Application”

$configfile = “ManagedProperties.xml”

$executingScriptDirectory = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent

$file = “$executingScriptDirectory/$configfile”

###Actual execution starts here###

Write-Host -foregroundcolor Green “***Script Started***”

createManagedProperty -searchApplicationName $SearchApplicationName -xmlFile $file

Write-Host -foregroundcolor Green “***Script Completed***”

3. Make sure that PS script and XML file are in same directory.

4. Ensure that you have provided correct “$SearchApplicationName” in PS script.

5. Open the PowerShell/SharePoint PowerShell console and run the PS script.

6. While Copying XML and script from this blog, verify if special characters (“-$ etc) are correct.

Happy Scripting!!!

PowerShell - Solution deployment simplified

2012-10-07T04:37:00.001-07:00

As a SharePoint developer or Admin, what we do most frequently in our day-to-day activities; is to play around with SharePoint solutions (WSPs) and Features..

And since we cannot memorize all the available operations, here are simplified PowerShell commands:

SPSolution Operations:

Add Solution to SharePoint Farm- You are ready with solution package (WSP) for deployment and this is a fresh deployment; first time deployment to the farm. SharePoint can consume a solution only if it is uploaded in SP solution store, and the operation to upload a solution is Add-SPSolution

Command:

Add-SPSolution -LiteralPath -Confirm

Parameters:

LiteralPath: Mandatory, Takes full path of WSP as string

Confirm: Optional, Ask for confirmation before operation

Example:

Add-Spsolution -Literalpath "C:\Solutions\MySolution.wsp"

Install Solution - Now solution is available in farm, next step is to use it. Installing a WSP comes with many options based on scope (for specific web application or all) and content (DLL(s) for GAC or files).

Command:

Install-SPSolution -Identity -GACDeployment

Install-SPSolution -Identity -AllWebApplication -GACDeployment

Install-SPSolution -Identity -WebApplication -GACDeployment

Parameters:

Identity: Required, Full name/GUID of WSP as string

AllWebapplications: Optional, If WSP to be used by all webapplications in farm

WebApplication: Optional, If WSP is for specific web application, URL as string

GACDeployment: Optional, If WSP includes some DLL to GAC

Force: this parameter can be used if installation is throwing some error due to feature activation or time job issue.

Confirm: Optional, Ask for confirmation before operation

Example:

Install-SPSolution -Identity "MySolution.wsp" -GACDeployment

Install-SPSolution -Identity "MySolution.wsp" -AllWebApplication -GACDeployment

Install-SPSolution -Identity "MySolution.wsp" -WebApplication "http://mysite.mydomain.com/" -GACDeployment

Upgrade a deployed Solution- Your solution package (WSP) is already deployed and installed; now you did some changes in code and want to deploy the latest, here comes Update-SPSolution. This command will upgrade the deployed solution with latest DLL(s) and files.

Command:

Update-SPSolution -Identity -LiteralPath -GACDeployment

Parameters:

Identity: Required, Full name/GUID of WSP as string

LiteralPath: Mandatory, Takes full path of WSP as string

GACDeployment: Optional, If WSP includes some DLL to GAC

Force: this parameter can be used if installation is throwing some error due to feature activation or time job issue.

Confirm: Optional, Ask for confirmation before operation

Example:

Update-SPSolution -Identity MySolution.wsp -LiteralPath "C:\Solutions\MySolution.wsp" -GACDeployment

Deployment Rollback: There are scenarios where we may need to rollback the deployment; If the deployment caused some major issue in farm/application or you added a big component (i.e.-site/list definition) in you solution and want a fresh deployment. To rollback a deployment, first retract/uninstall the WSP and then remove it from farm.

Retract Solution - Similar to installation, uninstalling a WSP comes with many options based on scope (for specific web application or all).

Command:

Uninstall-SPSolution -Identity -Confirm

Uninstall-SPSolution -Identity -AllWebApplication -Confirm

Uninstall-SPSolution -Identity -WebApplication -Confirm

Parameters:

Identity: Required, Full name/GUID of WSP as string

AllWebapplications: Required, If WSP to be retracted from all webapplications in farm

WebApplication: Required, If WSP is for specific web application, URL as string

Confirm: Optional, Ask for confirmation before operation

Example:

Uninstall-SPSolution -Identity "MySolution.wsp"

Uninstall-SPSolution -Identity "MySolution.wsp" -AllWebApplication -Confirm:$false

Uninstall-SPSolution -Identity "MySolution.wsp" -Webapplication "http://mysite.mydomain.com/" -Confirm:$false

Remove Solution to SharePoint Farm- After retraction, solution can be removed from SharePoint farm solution store.

Command:

Remove-SPSolution -Identity -Confirm

Parameters:

Identity: Required, Full name/GUID of WSP as string

Confirm: Optional, Ask for confirmation before operation

Example:

Remove-SPSolution "MySolution.wsp"

Remove-SPSolution -Identity "Unilever.Global.CDF.wsp" -Confirm:$false

SPFeature Operations:

Install/Uninstall Features in SharePoint Farm- Normally feature installation/un-installation are taken care with SPSolution operations which contains the feature. But we come across situations where features needs to be Installed/Uninstalled separately. Below are the commands and examples.

Install Feature Command:

Install-SPFeature -Path -Force -Confirm

Parameters:

Path: Mandatory, Takes relative path from the folder “$env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\” to the feature as string

Confirm: Optional, Ask for confirmation before operation ($true/$false)

Force: Optional, this parameter can be used for force installation.

Example:

Install-SPFeature -Path "MyFeature"

Un-Install Feature Command:

Uninstall-SPFeature -Path -Force -Confirm

Parameters:

Path: Mandatory, Takes relative path from the folder “$env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\” to the feature as string

Confirm: Optional, Ask for confirmation before operation ($true/$false)

Force: Optional, this parameter can be used for force operation.

Example:

Uninstall-SPFeature -Path "MyFeature"

Activate/Deactivate Feature- Below are the commands and examples.

Activate Feature Command:

Enable-SPFeature –Identity -URL Force -Confirm

Parameters:

Identity: Required, Name or GUID of feature as string

URL: Optional,Site/Web URL depending on feature scope

Confirm: Optional, Ask for confirmation before operation ($true/$false)

Force: Optional, this parameter can be used for force installation.

Example:

Enable-SPFeature –Identity "MyFeature" -URL "http://mysite.mydomain.com"

Deactivate Feature Command:

Disable-SPFeature –Identity -URL Force -Confirm

Parameters:

Identity: Required, Name or GUID of feature as string

URL: Optional,Site/Web URL depending on feature scope

Confirm: Optional, Ask for confirmation before operation ($true/$false)

Force: Optional, this parameter can be used for force operation.

Example:

Disable-SPFeature –Identity "MyFeature" -URL "http://mysite.mydomain.com"

PowerShell : Start up

2012-09-21T18:43:00.002-07:00

Windows PowerShell (PS) is a shell scripting, provided by Microsoft. This is mainly used for Windows and Server administration. This is very powerful tool for administrators. Here we’ll cover basics of PowerShell. Refer http://msdn.microsoft.com/en-us/library/windows/desktop/aa973757(v=vs.85).aspx for more details.
In this post I would give a start-up that how PowerShell is used for SharePoint.
Start: Assuming PowerShell is installed on your machine. Open the PS (PowerShell) console. [Start-> All Programs->Accessories -> Windows PowerShell]
Type Dir on blue console and enter-> Enter : It will show your directory information. Similarly we can do all kind of windows activities from this console. PS is packaged with large number of cmdlets, which are light weight commands to perform different activities, check http://msdn.microsoft.com/en-us/library/windows/desktop/ms714395(v=vs.85).aspx and http://technet.microsoft.com/en-us/scriptcenter/dd772285.aspx for details on PS cmdlets.
So now we know what PowerShell is and how to use it. Now, how to use this for SharePoint? SharePoint cmdlets are available in a snap in which should be added to Windows PS first to use it.
Type below command on console and enter [on SharePoint server]:
Add-PSSnapin Microsoft.SharePoint.PowerShell
Now, we are all set..
Enter Get-SPSite on console, hit Enter and you’ll get list of all the site collections available in your SP Farm.
Some important points:
1. SharePoint 2010 Management Shell is a PS console for SP packaged and installed with SP2010 and can be used directly, no additional snap-in required.
2. Login account need appropriate permissions on SP Server and SP Databases to execute cmdlets/scripts.
It’s just a beginning..
Happy scripting :)

SharePoint Incoming Email Configuration - PowerShell

2012-05-12T09:49:00.000-07:00

PowerShell is a strong windows shell scripting, which is widely used in SharePoint 2010. Here I am sharing small and useful scripts we use for SharePoint Farm administration.

Requirement:
Configure Incoming Email settings in SharePoint farm.

Script:

# *******************************************************************
## Function - Configure Incoming Email settings in SharePoint farm
## Author - Deepak Solanki
## Checks to ensure that Microsoft.SharePoint.Powershell is loaded, if not, adding pssnapin
## Configure Incoming Email settings in SharePoint farm
# ********************************************************************
#Add SharePoint Add-ins
Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue
# if snapin is not installed then use this method
[Void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")

Write-Host "Script started to Configure Incoming Email."

#Variables to get config values
[boolean]$Enabled = $true;
[boolean]$UseAutomaticSettings = $false;
[boolean]$UseDirectoryManagementService = $true;
[boolean]$RemoteDirectoryManagementService = $false;
$ServerAddress = "EXCHANGE.DOMAIN.COM";
[boolean]$DLsRequireAuthenticatedSenders = $true;
[boolean]$DistributionGroupsEnabled = $true;
$ServerDisplayAddress = "sharepoint.company.com";
$DropFolder = "c:\inetpub\mailroot\drop";

#Test the drop folder location exists before proceeding with any changes
$dropLocationTest = Get-Item $DropFolder -ErrorAction SilentlyContinue
if ($dropLocationTest -eq $null)
{
Throw "The drop folder location $DropFolder does not exist - please create the path and try the script again."
}

#Configuring Incoming E-mail Settings
try
{
$type = "Microsoft SharePoint Foundation Incoming E-Mail"
$svcinstance = Get-SPServiceInstance | where { $_.TypeName -eq $type}
$inmail = $svcinstance.Service

if ($inmail -ne $null)
{
Write-Log "Configuring Incoming E-mail Settings."
#Enable sites on this server to receive e-mail
$inmail.Enabled = $Enabled

#Automatic Settings mode
$inmail.UseAutomaticSettings = $UseAutomaticSettings

#Use the SharePoint Directory Management Service to create distribution groups
$inmail.UseDirectoryManagementService = $UseDirectoryManagementService

#Use remote: Directory Management Service
$inmail.RemoteDirectoryManagementService = $RemoteDirectoryManagementService

#SMTP mail server for incoming mail
$inmail.ServerAddress = $ServerAddress

#Accept messages from authenticated users only
$inmail.DLsRequireAuthenticatedSenders = $DLsRequireAuthenticatedSenders

#Allow creation of distribution groups from SharePoint sites
$inmail.DistributionGroupsEnabled = $DistributionGroupsEnabled

#E-mail server display address
$inmail.ServerDisplayAddress = $ServerDisplayAddress

#E-mail drop folder
$inmail.DropFolder = $DropFolder;

$inmail.Update();
Write-Host "Incoming E-mail Settings completed."
}
}
#Report if there is a problem setting Incoming Email
catch { Write-Host "There was a problem setting Incoming Email: $_" }

SharePoint Diagnostic Configuration - PowerShell

2012-05-12T07:14:00.000-07:00

Access Active Directory in .NET

2011-04-15T03:17:00.000-07:00

During one of my client requirements, I played a lot with active directory to display user data in a web application from active directory.

Here goes a generic class with some functions to get get user information from active directory:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Data;
using System.DirectoryServices;
using System.Collections;

namespace Common
{
public class ActiveDirectory
{
string domainPath = "GC://YourGC/DC=YourDomain,dc=YourOU,dc=com";

//Get Single user info
public DataTable GetUserInfo(string sLogonName)
{
/*Getting user data from active directory*/
DirectoryEntry entry = new DirectoryEntry(domainPath);
DirectorySearcher searcher = new DirectorySearcher(entry);
searcher.Filter = "(&(objectClass=user)(sAMAccountName=" + sLogonName + "))";
SearchResult result = searcher.FindOne();

/*Creating a datatable to store user data*/
DataTable resultTable = new DataTable("UserData");
resultTable.Columns.Add("givenname");
resultTable.Columns.Add("sn");
resultTable.Columns.Add("title");
resultTable.Columns.Add("telephoneNumber");
resultTable.Columns.Add("company");
resultTable.Columns.Add("mail");
resultTable.Columns.Add("department");
resultTable.Columns.Add("manager");

DataRow resultRow = resultTable.NewRow();

if (result.Properties.Count > 0)
{
try
{
resultRow["givenname"] = result.Properties["givenname"][0].ToString();
}
catch (Exception)
{
resultRow["givenname"] = string.Empty;
}
try
{
resultRow["sn"] = result.Properties["sn"][0].ToString();
}
catch (Exception)
{
resultRow["sn"] = string.Empty;
}
try
{
resultRow["title"] = result.Properties["title"][0].ToString();
}
catch (Exception)
{
resultRow["title"] = string.Empty;
}
try
{
resultRow["telephoneNumber"] = result.Properties["telephoneNumber"][0].ToString();
}
catch (Exception)
{
resultRow["telephoneNumber"] = string.Empty;
}
try
{
resultRow["company"] = result.Properties["company"][0].ToString();
}
catch (Exception)
{
resultRow["company"] = string.Empty;
}
try
{
resultRow["mail"] = result.Properties["mail"][0].ToString();
}
catch (Exception)
{
resultRow["mail"] = string.Empty;
}
try
{
resultRow["department"] = result.Properties["department"][0].ToString();
}
catch (Exception)
{
resultRow["department"] = string.Empty;
}
try
{
resultRow["manager"] = result.Properties["manager"][0].ToString();
}
catch (Exception)
{
resultRow["manager"] = string.Empty;
}
resultTable.Rows.Add(resultRow);
}
else
{

}
return resultTable;
}

//Get all domain users multiple properties in data table
public DataTable GetAllUserInfo()
{
/*Getting user data from active directory*/
DirectoryEntry entry = new DirectoryEntry(domainPath);
DirectorySearcher searcher = new DirectorySearcher(entry);
searcher.PageSize = 1000;

searcher.Filter = "(&(objectClass=user)(objectCategory=person))"; //to get users only
SearchResultCollection resultCollection = searcher.FindAll();

/*Creating a datatable to store user data*/
DataTable resultTable = new DataTable("UserData");
resultTable.Columns.Add("givenname");
resultTable.Columns.Add("sn");
resultTable.Columns.Add("title");
resultTable.Columns.Add("telephoneNumber");
resultTable.Columns.Add("company");
resultTable.Columns.Add("mail");
resultTable.Columns.Add("department");

SearchResult result;
if (resultCollection != null)
{
for (int counter = 0; counter < resultCollection.Count; counter++)
{
DataRow resultRow = resultTable.NewRow();

result = resultCollection[counter];
if (result.Properties.Contains("givenname"))
{
resultRow["givenname"] = result.Properties["givenname"][0].ToString();
}
if (result.Properties.Contains("sn"))
{
resultRow["sn"] = result.Properties["sn"][0].ToString();
}
if (result.Properties.Contains("title"))
{
resultRow["title"] = result.Properties["title"][0].ToString();
}
if (result.Properties.Contains("telephoneNumber"))
{
resultRow["telephoneNumber"] = result.Properties["telephoneNumber"][0].ToString();
}
if (result.Properties.Contains("company"))
{
resultRow["company"] = result.Properties["company"][0].ToString();
}
if (result.Properties.Contains("mail"))
{
resultRow["mail"] = result.Properties["mail"][0].ToString();
}
if (result.Properties.Contains("department"))
{
resultRow["department"] = result.Properties["department"][0].ToString();
}
resultTable.Rows.Add(resultRow);
}
}
return resultTable;
}

//Get all domain users single property in array list
public ArrayList GetAllADDomainUsers()
{
ArrayList allUsers = new ArrayList();

DirectoryEntry searchRoot = new DirectoryEntry(domainPath);
DirectorySearcher search = new DirectorySearcher(searchRoot);
search.Filter = "(&(objectClass=user)(objectCategory=person))";

SearchResult result;
SearchResultCollection resultCol = search.FindAll();
if (resultCol != null)
{
for (int counter = 0; counter < resultCol.Count; counter++)
{
result = resultCol[counter];
if (result.Properties.Contains("samaccountname"))
{
allUsers.Add((String)result.Properties["samaccountname"][0]);
}
}
}
return allUsers;
}
}
}

Happy Coding!!!

Error & information logging; event viewer or text file

2011-04-13T04:54:00.000-07:00

We can log different errors or information while writing code for any .NET application, here is a generic class written for logging:

Code:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Diagnostics;
using System.IO;
using System.Security.Permissions;

namespace Common
{
/*This Class is used for logging messages to either a custom EventViewer or in a plain text file located on web server.
* Owner : Deepak Solanki
* Year : 2011 */

public class Logging
{
#region "Variables"

private string sLogFormat;
private string sErrorTime;

#endregion

#region "Local methods"

/* Write to Txt Log File*/
public void WriteToLogFile(string sErrMsg)
{
try
{
//sLogFormat used to create log format :
// dd/mm/yyyy hh:mm:ss AM/PM ==> Log Message
sLogFormat = DateTime.Now.ToShortDateString().ToString() + " " + DateTime.Now.ToLongTimeString().ToString() + " ==> ";

//this variable used to create log filename format "
//for example filename : ErrorLogYYYYMMDD
string sYear = DateTime.Now.Year.ToString();
string sMonth = DateTime.Now.Month.ToString();
string sDay = DateTime.Now.Day.ToString();
sErrorTime = sYear + sMonth + sDay;

//writing to log file
string sPathName = "C:\\Logs\\ErrorLog" + sErrorTime;
StreamWriter sw = new StreamWriter(sPathName + ".txt", true);
sw.WriteLine(sLogFormat + sErrMsg);
sw.Flush();
sw.Close();
}
catch (Exception ex)
{
WriteToEventLog("MySite", "Logging.WriteToLogFile", "Error: " + ex.ToString(), EventLogEntryType.Error);
}
}

/* Write to Event Log*/
public void WriteToEventLog(string sLog, string sSource, string message, EventLogEntryType level)
{
//RegistryPermission regPermission = new RegistryPermission(PermissionState.Unrestricted);
//regPermission.Assert();

if (!EventLog.SourceExists(sSource))
EventLog.CreateEventSource(sSource, sLog);

EventLog.WriteEntry(sSource, message, level);
}

#endregion
}
}

Happy Coding!!!

Web part to show data from list

2011-04-13T04:10:00.000-07:00

Requirement is to show news on web page, data saved in custom list . A webpart to get data from list and show on page:

1. Open Visual Studio and create a class file or webpart (if sharepoint extension is there with VS.
2. Code of ShowNews.cs file below:

using System;
using System.Runtime.InteropServices;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Serialization;
using System.Drawing;
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
using Microsoft.SharePoint.WebPartPages;

namespace MyWebParts
{
[Guid("6e1a7cf2-bf98-4926-81c9-0c0184ba6a60")]
public class ShowNews : System.Web.UI.WebControls.WebParts.WebPart
{

//Controls
private Label lblTitle;
private Label lblNews;

// A table that is used to layout the controls
private Table tbMain;
private TableRow tRow;
private TableCell tCell;

#region "Web Part Properties"

private const string defaultSiteCollection = "NewTeamSite";
private string _siteName = defaultSiteCollection;
[Personalizable(PersonalizationScope.Shared), WebBrowsable(true),
WebDisplayName("Site Name"),
WebDescription("Site from where to fetch News")]

public string SiteName
{
get { return this._siteName; }
set { this._siteName = value; }
}

private const string defaultList = "News";
private string _listName = defaultList;
[Personalizable(PersonalizationScope.Shared), WebBrowsable(true),
WebDisplayName("List Name"),
WebDescription("List from where to fetch News")]

public string ListName
{
get { return this._listName; }
set { this._listName = value; }
}
#endregion

public ShowNews()
{
}

protected override void CreateChildControls()
{
base.CreateChildControls();

// TODO: add custom rendering code here.
tbMain = new Table();
tbMain.BorderStyle = BorderStyle.Double;
tbMain.BorderColor = Color.Silver;
tbMain.BackColor = Color.WhiteSmoke;

lblTitle = new Label();
lblTitle.Text = "News";
lblTitle.Font.Bold = true;

tRow = new TableRow();
tCell = new TableCell();
tCell.VerticalAlign = VerticalAlign.Top;
tCell.HorizontalAlign = HorizontalAlign.Center;
tCell.Controls.Add(lblTitle);
tRow.Controls.Add(tCell);
tbMain.Controls.Add(tRow);

lblNews = new Label();
lblNews.Text = "Blank";

tRow = new TableRow();
tCell = new TableCell();
tCell.VerticalAlign = VerticalAlign.Top;
tCell.HorizontalAlign = HorizontalAlign.Left;
tCell.Controls.Add(lblNews);
tRow.Controls.Add(tCell);
tbMain.Controls.Add(tRow);

this.Controls.Add(tbMain);

CreateNewsHtml();
}

private void CreateNewsHtml()
{
SPList newsList;
SPListItemCollection listitemcoll;

try
{
using (SPSite site = new SPSite(this.Context.Request.Url.ToString()))
{
using (SPWeb web = site.AllWebs[this._siteName])
{
newsList =web.Lists[this._listName];
listitemcoll = newsList.Items;
if (newsList.ItemCount > 0)
foreach(SPListItem item in listitemcoll)
{
lblTitle.Text = item["Title"].ToString();
lblNews.Text = item["News"].ToString();
}

}
}
}
catch (Exception ex)
{

}
}
}
}

3. Create ShowNews.webpart file (get created itself with Sharepoint extension)

<?xml version="1.0" encoding="utf-8"?>
<webParts>
<webPart xmlns="http://schemas.microsoft.com/WebPart/v3">
<metaData>
<type name="MyWebparts.ShowNews, ShowNews, Version=1.0.0.0, Culture=neutral, PublicKeyToken=XXXXXXXXXXXXXXXXX" />
<importErrorMessage>Cannot import ShowNews Web Part.</importErrorMessage>
</metaData>
<data>
<properties>
<property name="Title" type="string">ShowNews Web Part</property>
<property name="Description" type="string">Show News from List on Page</property>
<property name="AllowZoneChange" type="bool">True</property>
<property name="AllowHide" type="bool">True</property>
</properties>
</data>
</webPart>
</webParts>

4. Now, your webpart is ready, deploy it either [1] manually; GAC the DLL, upload webpart file to webpart gallery and made safecontrol entry for webpart in web.config file. or [2] create a deployment package to deploy the webpart.

Happy Coding!!!

User Control for Tab Navigation

2011-04-08T04:21:00.000-07:00

While developing a portal we came across a requirement where a tab navigation to be created and added in master page of the site. Here are the simple steps of how to create a tab navigation using ASP MENU control.

1. Go to your site/project and add a user control as new item.
2. There will be added one .ASCX file and one code file .ASCX.CS
3. We are not using code file here so delete code file (.ascx.cs)
4. Also delete code file reference from <%@ Control ... directive line (first line in file).

write the code to add asp menu and SiteMapDataSource
code below:

<%@ Control Language="C#" AutoEventWireup="true" %>
<div id="TabDiv" runat="server">
<table cellpadding="0" cellspacing="0" border="0" width="100%" class="TabMenuContainer">
<tr>
<td>
<asp:Menu CssClass="TabMenu" DataSourceID="CampaignPortalSiteMap" HideSelectElements="True"
ID="Menu2" Orientation="Horizontal" runat="server">
<StaticSelectedStyle CssClass="TabMenuItemSelected" />
<StaticMenuItemStyle CssClass="TabMenuItem" />
<StaticMenuStyle CssClass="SiteStaticMenu" />
<StaticHoverStyle CssClass="TabMenuItemHover" />
<DataBindings>
<asp:MenuItemBinding DataMember="SiteMapNode" Depth="0" NavigateUrlField="Url" TextField="Title"
ToolTipField="Description" />
</DataBindings>
</asp:Menu>
</td>
<td class="TabMenuSpacer" width="100%">
</td>
</tr>
</table>
</div>
<asp:SiteMapDataSource ID="CampaignPortalSiteMap" runat="server" ShowStartingNode="false"
SiteMapProvider="PortalSiteMap" />

In the code above:
ASP Menu control create navigation, it takes either a sitemap source as data source that can be bind to it, or menu items (statically or through code).

SiteMapDataSource is the sitemap provider reference, sitemap provider will be specified in web.config file of application.

There are many CSS classes for styling of tabs, that will be there in application's CSS file.

5. Now add the CSS file to define style classes, style sheet below:

body
{
font-family: Tahoma;
}

#MasterContainer
{
border: solid 1px black;
}

#BannerContainer
{
padding: 5px 5px 5px 5px;
font-weight: bold;
font-size: large;
}

.TabMenuContainer
{
border-top: solid 1px black;
}

.TabMenuItem
{
background-color: #FFFFBC;
text-align:center;
font-size: xx-small;
border: solid 1px black;
border-left: none;
padding: 3px 3px 3px 3px;
}
.TabMenuItemSelected
{
background-color: White;
text-align:center;
font-size: xx-small;
border-right: solid 1px black;
border-bottom: none;
border-top: none;
border-left: none;
padding: 5px 3px 5px 3px;
}
.TabMenuItemHover
{
color:Black;
font-weight: bold;
}
.SiteStaticMenu
{
margin: -1px 0px 0px 0px;
background-color: Black;
}
.TabMenuSpacer
{
background-color: #222222;
padding: 5px 5px 5px 5px;
}

#SiteContent
{
padding: 5px 5px 5px 5px;
margin: 10px 10px 10px 10px;
width: 100%;
}

.SiteContentSpacer
{
height: 200px;
visibility: hidden;
}#FooterContainer
{
font-size: xx-small;
border-top: solid 1px black;
}

Till now we are done with menu control and its look and feel, now we need to define the data source for that menu control.

6. Open web.config file of web application, go to section and add a provider that we had specified in used control.

<providers>
<add name="PortalSiteMap" type="System.Web.XmlSiteMapProvider" siteMapFile="portal.sitemap" />
</providers>

The last thing left now is to define sitemap file "portal.sitemap" from where asp menu would pick it's menu items.

7. Add a new sitemap item in project, naming portal.sitemap and put links, titles... of pages in specified xml format, sitemap xml below:

<?xml version="1.0" encoding="utf-8" ?>
<siteMap xmlns="http://schemas.microsoft.com/ AspNet/SiteMap-File-1.0" >
<siteMapNode url="" title="" description="" roles="*">
<siteMapNode url="~/Home.aspx" title="Home" description="The home page" roles="*" />
<siteMapNode url="~/default2.aspx" title="Tab 1" description="The first tab" roles="*" />
<siteMapNode url="~/default.aspx" title="Google" description="Google search" roles="*" />
<siteMapNode url="http://www.yahoo.com" title="Yahoo" description="Yahoo search" roles="*" />
</siteMapNode>
</siteMap>

All set now, put this user control on your master page or page, wherever required and navigate...Cheers :-)

Happy Coding!!!

Receive repeated logon windows - loopback check in Windows Server 2003

2011-02-16T23:05:00.000-08:00

It was something which took lots of time and I couldn't find a valid reason or solution for the problem, finally it turned out as a security feature with Windows Server 2003, that is Loopback check.

One of my old .NET web applications was hosted on Windows Server 2000, since Microsoft doesn't support 2000 servers anymore, I had to move my application to 2003 servers. It was a simple web site with windows integrated security. After creating site on new 2003 server, IIS 6, mapping home directory, putting DLLs, components etc in place, tried to browse site from IIS and received repeated logon window, finally ended up with "You are not authorized....". Tried opening the site in browser (IE) on web server, again same problem. Then on other machine in same network, tried opening the site; no problem, site opened successfully with my windows credentials, it was a great relief. :)

So, the problem was- i was not able to open the site from host machine but it was opening perfectly on any other machine. Tried many tricks; adding to trusted site, intranet zone..etc.. but nothing worked. Finally, after searching lots of article, reading many MSDN pages, found the MS KB for this.

There is a security feature with Windows Server 2003 SP1, named loopback check functionality. By default, loopback check functionality is turned on in Windows Server. This cause repeated Login Windows receive. The solution is simple, go in system registry and disable it.

The loopback check functionality is stored in the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\DisableLoopbackCheck

Here is the KB link for details on reason and solution:
http://support.microsoft.com/kb/926642

Hope it works for you..
Cheers!!!!

Enable Sharing & Security Tab - Windows

2011-01-22T03:28:00.000-08:00

Sometimes you want to share a folder or to implement\change some security settings or access rights but you wonder, in folder properties, where the Security tab is? It could happen to you even if you have administrator rights. Here are few simple steps to solve the problem.

So to see and unhide the Security tab, just use the following steps:
1. Launch Windows Explorer or My Computer.
2. Click on the Tools at the menu bar, and then click on Folder Options.
3. Click on View tab.
4. In the Advanced Settings section at the bottom of the list, uncheck and unselect (clear the tick) on the “Use simple file sharing (Recommended)” check box.
5. Click OK.

Security tab is available only to Administrator or users with administrative rights. So make sure you login as one. And security can only be set in an NTFS partition. If you’re still having problem to reveal or display the Security tab on files or folder properties, check out the following registry hack and set the value to 0 or simply delete the key:
Hive: HKEY_CURRENT_USER
Key: Software\Microsoft\windows\CurrentVersion\Policies\Explorer
Name: Nosecuritytab
Type: REG_DWORD
Value: 1

I hope it works for you..

To take ownership of a file or folder

2011-01-22T03:26:00.000-08:00

Take Ownership:
Are you not able to access or delete a file\folder from your computer even you are administrator?
Don’t worry; take ownership of that file or folder.

How to take ownership of a file
You must have ownership of a protected file in order to access it. If another user has restricted access and you are the computer administrator, you can access the file by taking ownership.

To take ownership of a file, follow these steps:
1. Right-click the file that you want to take ownership of, and then click Properties.
2. Click the Security tab, and then click OK on the Security message (if one appears).
3. Click Advanced, and then click the Owner tab.
4. In the Name list, click Administrator, or click the Administrators group, and then click OK.

The administrator or the administrators group now owns the file.
To take ownership of a folder, follow these steps:
1. Right-click the folder that you want to take ownership of, and then click Properties.
2. Click the Security tab, and then click OK on the Security message (if one appears).
3. Click Advanced, and then click the Owner tab.
4. In the Name list, click your user name, or click Administrator if you are logged in as Administrator, or click the Administrators group. If you want to take ownership of the contents of the folder, select the Replace owner on subcontainers and objects check box.
5. Click OK, and then click Yes when you receive the following message:
You do not have permission to read the contents of directory folder name. Do you want to replace the directory permissions with permissions granting you Full Control?
All permissions will be replaced if you click Yes.

Note folder name is the name of the folder that you want to take ownership of.
Click OK, and then reapply the permissions and security settings that you want for the folder and its contents.

Error - Attempted to perform an unauthorized operation

2010-02-08T21:31:00.000-08:00

I’ve faced a problem while trying to deploy a webpart created in Visual Studio 2008 with Sharepoint webparts template. I did the coding and build the project without any problem, but when tried to deploy it using visual studio, Build -> Deploy Solution, it had thrown an error “Attempted to perform an unauthorized operation।”

Reason: The possible problem is that you are trying to deploy solution on a site to which you don't have authorization to deployment.

Solution: Check the URL to which you are deploying the solution, by default it is http://localhost/ , change it to your site where you actually want to deploy the webpart.
Go to the project properties and inside the debug tab select the start action as 'start browser with url' and enter the valid site collection URL।

Though, there may be different reasons of this error because of any other authorization failure, this is also a main reason. Hope this fix might help.

Play Media in ASP.NET Site

2010-02-02T23:13:00.000-08:00

This is one of the basic requirements of a site; you may want to play a media file or a play list (group of media files). Here are few simple steps to create a web page with media player on it.

1. Open Visual Studio 2005\2008
2. File -> New ->Website, Give this site a name, like MySite
3. Create a new folder under your site, Right Click on site -> New Folder, name it Videos.
4. Copy all the media files you want to play on site.
5. Create a playlist, Right click on Videos folder -> Add New Item -> Text File -> Name it Playlist.m3u
6. Open the Playlist.m3u file and provide list of files with relative location in this, each file in new line. I.e. -
/MySite/Videos/Evian.wmv
/MySite/Videos/Too_Good.mpeg
7. Now, open the Default.aspx page, and add following code in <div> or <table> as per you site layout:
<object id="MediaPlayer1" width="360" height="400" classid="CLSID:22D6F312-B0F6-11D0-94AB-0080C74C7E95"
codebase="http://activex.microsoft.com/activex/controls/mplayer/en/nsmp2inf.cab#Version=5,1,52,701"
standby="Loading Microsoft® Windows® Media Player components..." type="application/x-oleobject"
style="text-align: center;">
<param name="FileName" value="Videos/Playlist.m3u" />
<param name="loop" value="True" />
<param name="ShowStatusBar" value="True" />
<param name="DefaultFrame" value="mainFrame" />
<param name="autostart" value="true" />
</object>
8. Save the file and Run this site. It will play the playlist provided.

Note- if you want to play just a single file in Media Player, just replace the line
<param name="FileName" value="Videos/Playlist.m3u" />
With line
<param name="src" value="Videos/Too_Good.mpeg" />

Happy Coding!!!

MOSS - Configure E-mail

2010-02-01T05:31:00.000-08:00

In MOSS site there is built-in functionality for sending\receiving mails for alerts, workflows, events etc. Here are simple steps to configure e-mail on Sharepoint server through Sharepoint Central Administrator.

Configure incoming e-mail
You can configure incoming e-mail settings so that SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-mail settings so that SharePoint sites can archive e-mail discussions as they happen, save e-mailed documents, and show e-mailed meetings on site calendars. In addition, you can configure the SharePoint Directory Management Service to provide support for e-mail distribution list creation and management.
To enable incoming e-mail by using automatic mode, you must install the Internet Information Services (IIS) Simple Mail Transfer Protocol (SMTP) server.
By specifying a drop folder, you can enable incoming e-mail by not using an SMTP server.
1. On the top navigation bar, click Operations.
2. On the Operations page, in the Topology and Services section, click Incoming e-mail settings.
3. If you want to enable sites on this server to receive e-mail, on the Incoming E-mail Settings page, in the Enable Incoming E-Mail section, select Yes.
4. Select either the Automatic or the Advanced settings mode.
If you select Advanced, you can specify a drop folder instead of using an SMTP server.
1. If you want to connect to the SharePoint Directory Management Service, in the Directory Management Service section, select Yes.
You can connect to the SharePoint Directory Management Service for SharePoint sites to manage e-mail addresses in SharePoint lists.
1. In the Directory Management Service URL box, type the URL of the SharePoint Directory Management Service.
2. In the E-mail server display address box, type the e-mail server name (for example, mail.sharepoint.fabrikam.com).
3. Answer the following two questions by selecting Yes or No:
· Does the Directory Management Service manage distribution lists?
· Should distribution lists accept mail only from authenticated senders?
4. In the Incoming E-Mail Server Display Address section, type a display name for the e-mail server (for example, mail.fabrikam.com) in the E-mail server display address box.
Tip You can specify the e-mail server address that is displayed when users create an incoming e-mail address for a list or group. Use this setting in conjunction with the SharePoint Directory Management Service to provide an e-mail server address that is more user-friendly.
1. In the Safe E-Mail Servers section, select one of the following options:
· Accept mail from all e-mail servers
· Accept mail from these safe e-mail servers. If you select this option, type the IP addresses (one per line) of the e-mail servers that you want to specify as safe in the corresponding box.
2. In the E-mail Drop Folder section, in the E-mail drop folder box, type the name of the folder in which Microsoft Windows SharePoint Services polls for incoming e-mail from the Windows SMTP Service.
This option is available only if you selected advanced mode.
Click OK.

Configure outgoing e-mail settings

You can configure outgoing e-mail settings so that your Simple Mail Transfer Protocol (SMTP) server sends e-mail alerts to site users and notifications to site administrators. You can configure both the "From" e-mail address and the "Reply" e-mail address that appear in outgoing alerts.
Configure outgoing e-mail
Configure default outgoing e-mail settings
Configuring the default outgoing e-mail settings configures the default outgoing e-mail settings for all Web applications.
1. On the top navigation bar, click Operations.
2. On the Operations page, click Outgoing e-mail settings in the Topology and Services section.
3. On the Outgoing E-Mail Settings page, in the Mail Settings section, type the Simple Mail Transfer Protocol (SMTP) server name for outbound e-mail (for example, mail.example.com) in the Outbound SMTP server box.
4. In the From address text box, type the from address as you want it to appear to e-mail recipients.
5. In the Reply-to address box, type the e-mail address to which you want e-mail recipients to reply.
6. In the Character set menu, select the character set appropriate for your language.
7. Click OK.

Configure outgoing e-mail settings for a Web application
You can override a Web application's default settings for outgoing e-mail.
1. On the top navigation bar, click Application Management.
2. On the Application Management page, click Web application outgoing e-mail settings in the SharePoint Web Application Management section.
3. On the Web Application E-Mail Settings page, select a Web application by using the Web Application menu in the Web Application section.
4. In the Mail Settings section, type the SMTP server name for outbound e-mail (for example, type mail.fabrikam.com) in the Outbound SMTP server box.
5. In the From address box, type the e-mail address as you want it to appear to e-mail recipients.
6. In the Reply-to address box, type the e-mail address to which you want e-mail recipients to reply.
7. On the Character set menu, click the character set that's appropriate for your language.
8. Click OK.

Cute Editor - Customize Toolbar

2010-02-01T01:13:00.000-08:00

Cute Editor comes with some default set of toolbar configurations like - Simple, Full, Compact Minimal etc, which may full fill your requirements. But in case the entire vendor provided toolbars do not meet your needs and you want to have a certain set of tools\buttons on your editor, you can do it by simply creating your own configuration XML.

Tools are maintained in simple XML config files, loacted at ~\CuteSoft_Client\CuteEditor\Configuration\AutoConfigure folder.
To create a new configuration file, copy an existing config file, i.e. Simple.config and re-name it "MyTools.config". Save it to ~\CuteSoft_Client\CuteEditor\Configuration folder.
Code of the configuration file would be as per our tools requirements as below:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<codeviewToolbars>
<item type="g_start" />
<item type="image" name="Save" postback="True" />
<item type="image" name="Print" />
<item type="image" name="Find" />
<item type="image" name="ToFullPage" command="FullPage" imagename="fit" hotkey="F12" />
<item type="image" name="FromFullPage" command="FullPage" imagename="restore" hotkey="F12" />
<item type="image" name="Cut" />
<item type="image" name="Copy" />
<item type="image" name="Paste" />
<item type="image" name="SelectAll" hotkey="CTRL+A" />
<item type="image" name="SelectNone" />
<item type="g_end" />
</codeviewToolbars>

<toolbars>
<item type="g_start" />
<item type="image" name="ToFullPage" command="FullPage" imagename="fit" hotkey="F12" />
<item type="image" name="FromFullPage" command="FullPage" imagename="restore" hotkey="F12" />
<item type="image" name="CleanCode" imagename="cleanup" />
<item type="image" name="NetSpell" imagename="spell" />
<item type="image" name="Cut" />
<item type="image" name="Copy" />
<item type="dropmenu" name="Paste" group="PasteGroup"/>
<item type="separator" />
<item type="image" name="Undo" />
<item type="image" name="Redo" />
<item type="image" name="Find" />

<item type="image" name="Break" />
<item type="image" name="InsertParagraph" imagename="Paragraph" />
<item type="image" name="InsertOrderedList" imagename="numlist" />
<item type="image" name="InsertUnorderedList" imagename="bullist" />
<item type="image" name="Indent" />
<item type="image" name="Outdent" />
<item type="forecolor" />
<item type="backcolor" />
<item type="g_end" />

<item type="g_start" />
<item type="image" name="Bold" />
<item type="image" name="Italic" />
<item type="image" name="Underline" imagename="under" />
<item type="image" name="StrikeThrough" imagename="strike" />
<item type="image" name="Superscript" />
<item type="image" name="Subscript" />
<item type="image" name="JustifyLeft" imagename="left" />
<item type="image" name="JustifyCenter" imagename="center" />
<item type="image" name="JustifyRight" imagename="right" />
<item type="image" name="RemoveFormat" imagename="unformat" />

<item type="table" />
<item type="image" name="InsertHorizontalRule" imagename="rule" />
<item type="image" name="InsertLink" imagename="link" />
<item type="image" name="Unlink" />
<item type="image" name="InsertAnchor" imagename="anchor" />
<item type="image" name="SelectAll" hotkey="CTRL+A" />
<item type="image" name="SelectNone" />
<item type="image" name="Help" />
<item type="g_end" />


</toolbars>
</configuration>

Now you have created your own toolbar for Cute Editor, you can simply use it on .aspx page by changing following code line in cute editor definition on page:

<CE:Editor ConfigurationPath="~/CuteSoft_Client/CuteEditor/Configuration/mytools.config"
id="Editor1"
runat="server" >
</CE:Editor>
Your Editor will render on your page like below :

Cute Editor Version Upgrade problem - HTTPMODULE

2009-09-15T06:42:00.000-07:00

Hi,

Sometimes a small thing can break down a big application. It happened to me once.
One of my big and critical applications running on .NET version 1.1 is using Cute Editor as users interface editor in its different pages. Once the next version came of the cute editor I tried to upgrade the version I am using with the latest one and all my pages which were using CE are distorted and editor was not working at all.

After digging a lot into this and contacting to CE customer care also, I went nowhere. But it was quite visible that CE files are trying to render on page, but it could not succeed. I felt it may be a security or authorization problem that prevents few files to be uploaded on page, and finally found that the problem is because we were using HTTPMODULE for handling authorization. When I checked the authorization DLL code, there is a credential check for all the files, I just bypassed that check for CE client file and it workedJ.
So next time you upgrade your Cute Editor, follow these steps.

1. Download CE client file from vendor’s site http://cutesoft.net/.
2. Get your .NET version client files.
3. Upload new version Cute Editor client files in application:
a) Need to delete all the client files from "(project)/CuteSoft_Client".
b) Upload all new client files (Downloaded from CE site) to project)/CuteSoft_Client".
4. Add the Component reference (new version DLL of cute editor) to all the projects which are using Cute Editor.
5. Make sure that license file cuteeditor.lic is added in bin folder of projects.
6. Modify all the .aspx files which are using Cute Editor accordingly to support new version.
7. Update the assembly reference with new version in all the .aspx files:

For more details on deployment and implement of Cute editor, please visit:
http://cutesoft.net/developer+guide/index.html
Installation and Deployment -> Deployment of CuteEditor for .NET

Few Common problems:
1. Version difference of cute editor in .ASPX page and DLL added in project references.
2. Client file path not found, if you are sharing client files from a common location, please add entry in web.config file of all the applications using CE.
3. Tool bar customized Configuration file is missing (If toolbar is customized).
4. HTTPMODULE is used for security and CE client files are not bypassed from authentication.

Sharepoint - STSADM commands for FEATURE

2009-09-09T05:47:00.000-07:00

Features:
stsadm -o installfeature
-filename
-name
[-force]
stsadm -o activatefeature
-filename
-name
-id
[-url]
[-force]
stsadm -o deactivatefeature
-filename
-name
-id
[-url]
[-force]
stsadm -o uninstallfeature
-filename
-name
-id
[-force]

STSADM Commands - Sharepoint

2009-09-09T05:11:00.000-07:00

Microsoft Office SharePoint Server 2007 includes the Stsadm tool for command-line administration of Office SharePoint Server 2007 servers and sites. Stsadm is located at the following path on the drive where SharePoint Products and Technologies is installed: %COMMONPROGRAMFILES%\microsoft shared\web server extensions\12\bin. You must be an administrator on the local computer to use Stsadm.Stsadm provides a method for performing the Office SharePoint Server 2007 administration tasks at the command line or by using batch files or scripts.
Content database Operations:
Add content db:
stsadm.exe -o addcontentdb -url -databasename [-databaseserver ] [-databaseuser ] [-databasepassword ] [-sitewarning ] [-sitemax ]

Database repair:
stsadm.exe -o databaserepair -url -databasename [-deletecorruption]

Delete content db:
stsadm.exe -o deletecontentdb -url -databasename [-databaseserver ]

Set config db:
stsadm.exe -o setconfigdb [-connect] -databaseserver [-databaseuser ] [-databasepassword ] [-databasename ] [-exclusivelyusentlm] [-farmuser] [-farmpassword] [-adcreation] [-addomain ] [-adou ]

Delete config db:
stsadm.exe -o deleteconfigdb

Merge content dbs:
stsadm.exe -o mergecontentdbs -url -sourcedatabase destinationdatabasename [-operation <1,>] [-filename ] Where operation is: 1. Analyze (default) 2. Full database merge 3. Read from file
Trim audit log:stsadm -o trimauditlog -url -enddate -databasename [-databaseserver]

Stsadm operations for Webparts:
We creat customized web parts in .NET (sharepoint) for our pecific needs where out of box web parts do not meet our requirements. Microsoft Office SharePoint Server 2007 includes the Stsadm tool for command-line administration of Office SharePoint Server 2007 servers and sites. Once the web part is ready, we need to add and deploy this before use, here are the stsadm command line operations for Web Parts.
Add Web part : addwppack
stsadm.exe -o addwppack -filename [-lcid ] [-url ] [-globalinstall] [-force] [-nodeploy]
stsadm.exe -o addwppack -name [-lcid ] [-url ] [-globalinstall] [-force]

Delete Web part : deletewppack
stsadm.exe -o deletewppack -name [-lcid ] [-url ]

Deploy Web part : deploywppack:
stsadm.exe -o deploywppack -name [-url ] [-time ] [-immediate] [-local] [-lcid ] [-globalinstall] [-force]

enumwppacks:
stsadm.exe -o enumwppacks [-name ] [-url ] [-farm]

retractwppack:
stsadm.exe -o retractwppack -name [-url ] [-time ] [-immediate] [-local] [-lcid ]