http://bit.ly/KLN5Ma

Get all Site Columns for a SharePoint 2010 site collection: http://www.sharepointfix.com/2011/03/powershell-script-get-all-site-columns.html

How to: Add a Content Type to a Site: http://msdn.microsoft.com/en-us/library/aa543878.aspx

Export Content Types: http://blog.falchionconsulting.com/index.php/2008/02/export-content-types/

private int Logger(Exception exObj)
{
using (Stream myFile = File.Exists(“TestFile.txt”) ? File.Open(“TestFile.txt”, FileMode.Append) : File.Create(“TestFile.txt”))
{
/* Create a new text writer using the output stream, and add it to * the trace listeners. */
TextWriterTraceListener myTextListener = new TextWriterTraceListener(myFile);
Trace.Listeners.Add(myTextListener);
// Write output to the file.
Trace.Write(“\r\n Test output \r\n”);
Trace.Write(exObj);
Trace.Write(“\r\n Test output \r\n”);

// Flush the output.
Trace.Flush();
myFile.Close();

Trace.Listeners.Remove(myTextListener); // this is very important else you may encounter error wrt file/stream/trace object
myFile.Dispose();
}
return 0;
}

The answer is create an XmlNodeReader object and get the required element (node) into it either by traversing the xml document or by firing a simple (yet powerful) XPath Query on to the document.  The below sample explains the same by making use of Xpath Query.

private void btnGetData_Click(object sender, EventArgs e)
{
//Create xmlnode and xmlElement for xpath
XmlNode xmlNode;
XmlElement root = doc.DocumentElement;

// xpath expression //List[@Name='Lotus Machines']
xmlNode = root.SelectSingleNode(txtExpression.Text);

DataSet dataSet = new DataSet();
if (xmlNode.HasChildNodes)
{
for (int indexNode = 0; indexNode < xmlNode.ChildNodes[0].ChildNodes.Count; indexNode++)
{
XmlNode innerNode = xmlNode.ChildNodes[0].ChildNodes[indexNode];
using (XmlNodeReader reader = new XmlNodeReader(innerNode))
{// fill dataset from reader object as below
dataSet.ReadXml(reader);
}
}
}
}

I would definitely like to hear from ur side if there is any other better way for so… till the bye bye 

Here’s an excerpt:

A New York City subway train holds 1,200 people. This blog was viewed about 5,300 times in 2011. If it were a NYC subway train, it would take about 4 trips to carry that many people.

Click here to see the complete report.

So starting with shelling

what is powershell:
* windows powershell is microsofts task automation framework [as per wikipedia] built primarily for the windows administrators.
* It basically consist of command-line shell which is build on top of .net common language runtime and .net framework that accepts and returns .NET framework objects unlike to its counterparts which accept and return text.
* An administrator can perform administrative tasks on local but also on remote windows system through the virtue of powershell support to COM and WMI

As per microsoft its: http://msdn.microsoft.com/en-us/library/aa973757%28VS.85%29.aspx

I came across some handy tool / editor for playing with the powershell at http://powergui.org  do check it.

Regards,
Manish Patil

function getField(fieldType,fieldTitle)
{
var docTags = document.getElementsByTagName(fieldType);
for (var i=0; i < docTags.length; i++)
{
if (docTags[i].title == fieldTitle)
{
docTags[i].readOnly = true;
docTags[i].setAttribute(“choices”,”Comment 1|20″);
}
}
return false;
}
getField(‘input’,'Comment Type’);

here in today I would like to share a small but required thing while packaging sharepoint solutions. We usually require to bundle-up .net assemblies within a sharepoint solution(s). Microsoft Visual studio 2010 has made this thing very easy for packaging sharepoint 2010 solutions.

Please check the screen shots for the sameIn the solution explorer you can see an .net assembly( underlined red in color), I wanted to refer/add this assembly into the sharepoint solution (highlighted in dark black).

So I opened the package.package (double click it ) as shown in screen shot.

Here on the wizard click on Advance tab (highlighted in red box below)

On opening of the tab gives option (inform of buttons) to add, edit, delete “Additional Assemblies”. The added assemblies are listed in the grid.

When we try to add new assembly it will give 2 options viz; Add existing assembly & Add assembly from project output

Now if you want to add assembly from your current project/solution then use second option & if you to refer to external assembly which is not part of your project then use first option.

In either cases if you want to register these assemblies into the web.config safe controls then there is provision for same

One most important thing to remember is: any assembly that you want to refer/add should be strong named (public token key) in order to add it to the GAC / assembly cache.

Additional Resource can be found at: Add & Remove Additional Assemblies

This post is helpful for those who are trying to extract information from the SPContentDatabase class. This is usually required when one is creating custom timer job, base level features etc.

The following code is written for Custom timer job:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint.Administration; (must)
using Microsoft.SharePoint;

namespace TTKTimerJob
{

class TTKIssueTimerJob: SPJobDefinition
{

public TTKIssueTimerJob()
: base()
{ }

public TTKIssueTimerJob(string jobName, SPService service, SPServer server, SPJobLockType targetType)
: base(jobName, service, server, targetType)
{ }

public TTKIssueTimerJob(string jobName, SPWebApplication webApplication)
: base(jobName, webApplication, null, SPJobLockType.ContentDatabase)
{
this.Title = “TTK Issue Timer Job”;
}

public override void Execute(Guid targetInstanceId)
{

// get a reference to the current site collection’s content database
SPWebApplication webApplication = this.Parent as SPWebApplication;
SPContentDatabase contentDb = webApplication.ContentDatabases[targetInstanceId];
// Get the TimerJobList Name from the webApplication collection
SPSiteCollection timerSiteCollection = webApplication.ContentDatabases[targetInstanceId].Sites;
SPList timerJobList = null;
foreach (SPSite siteItem in timerSiteCollection)
{
#region code here: finds the List in rootweb
//assumes the existence of a site collection with an absolute URL of
//http://localhost/sites/sitecollection/subsite/Lists/abc and that this site collection has a Web site named subsite
//SPList xyz = siteItem.RootWeb.GetList(“list url here”);

//SPList xyz = siteItem.RootWeb.Lists.TryGetList(“list Title here”);
timerJobList = siteItem.RootWeb.Lists.TryGetList(“ListTimerJob”);
if (timerJobList != null)
{
// create a new list Item, set the Title to the current day/time, and update the item
SPListItem newList = timerJobList.Items.Add();
newList["Title"] = DateTime.Now.ToString();
newList.Update();
break;
}
#endregion}

}

}

}

This post is outcome of love & relationship with excel automation and recent hit back with the same. I would like to praise the courage & efforts of colleagues who restlessly kept on working so that I can write this post

So starting with the post we’ll go to history from where this all started

As a aspiring software developer in mid-of  2006 I first came across this notorious requirement where I was required to read excelsheets from one location on the server process the data and then dump it into database. Believe me this requirement put into nodus situation. I had never that this kind of situation could ever arise and if then should not possible at all.

But when I did bit of goggle (I’m god follower from start of my carrier) then I came to know this is very common requirement and there are fair enough solutions (which actually work for all:) ). And that point when I had my first hate and love relationship with excel automation(hate=bcz I never thought of this, love = bcz many handy solutions are around).

Following are the possible approaches by which I had read and wrote to excel file:

READ:

1. Microsoft OleDB driver:
   1. Jet OleDB for 32 bit applications
   2. ACE.OleDB for 64 bit applications
2. Microsoft Office COM/ Excel Objects
3. Stream objects
4. Excel Services (applicable only for MOSS)

Write:

1. CSV or delimiter while exporting data to client through HTTPHeaders of ASP.NET
2. XML and XSLT while exporting data to client through HTTPHeaders of ASP.NET
3. Microsoft Office COM/ Excel Objects
4. Open Office SDK (applicable for MSOffice 2007 and above [.xlsx extensions])
5. Microsoft OleDB driver with SQL queries that pushes data into excel