Anyway, I figured someone would need something like this at some point so here it is. Enjoy!

Works with both 2007 and 2010

#===================================================================================
function Find-WebParts([String]$webUrl=$(throw ‘Parameter -Url is missing’))
{
write-host “Starting Analysis…”
write-host “”
$site = New-Object -TypeName “Microsoft.SharePoint.SPSite” -ArgumentList $webUrl
$web = $site.OpenWeb()
#Start with the root site
Get-WebPartDetails($webUrl)
#Start looking at all subsites and the subsites of those sites
Get-Subsites($webUrl)
write-host “”
write-host “Done.”
}

#===================================================================================
# Get the subsites and the subsites of those sites
#===================================================================================
function Get-Subsites($Url)
{
$WebCollection = Get-WebCollection($Url)
foreach($site in $WebCollection)
{
if($site.url -like “http*”)
{
Get-WebPartDetails($site.url)
}
if($site.url -like “http*”)
{
Get-Subsites($site.url)
}
}
}

#===================================================================================
# Return all webs within a site
#===================================================================================
function Get-WebCollection($Url)
{
$site = New-Object -TypeName “Microsoft.SharePoint.SPSite” -ArgumentList $Url
$web = $site.OpenWeb()
$WebCollection = $web.webs
return $WebCollection
}

#===================================================================================
# This function goes through all the lists for the given url and looks for
# documentlibraries that contain files with an .aspx extension
#===================================================================================
function Get-WebPartDetails ([String]$webUrl)
{
$site = New-Object -TypeName “Microsoft.SharePoint.SPSite” -ArgumentList $webUrl
$web = $site.OpenWeb()
$lists = $web.Lists
ForEach($list in $lists)
{
#Check if document library
if($list.BaseType -eq “DocumentLibrary”)
{
$items = $list.Items

foreach($item in $items)
{
if($item.Name -like “*.aspx”)
{
$pageurl = $web.Url + “/” + $item.Url
[Microsoft.SharePoint.SPFile]$file = $item.File
$mgr = $file.GetLimitedWebPartManager([System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared)
foreach($wp in $mgr.WebParts)
{
$match = “*” + $WebPartName + “*”
if($wp.GetType().BaseType -like $match)
{
write-host $wp.GetType().BaseType”,” $wp.GetType().Name”,” $pageurl
}
}
}
}
}

}

}

Is it really that bad?

1. Create a solution in Visual Studio
2. Add a feature
3. Add an Empty Element to the project
4. In the Elements.xml file add the following XML:

<?xml version=”1.0″ encoding=”utf-8″?>

<Elements xmlns=”http://schemas.microsoft.com/sharepoint/”>

<CustomAction

Id=”F1E874CF-D433-445C-A62A-C0D8BF8D2AAA”

Location=”Microsoft.SharePoint.Administration.Applications”

Title=[PUT LINK TITLE HERE]

GroupId=”ServiceApplications”

Sequence=”15″

RequiredAdmin=”Delegated”

Description=[PUT DESCRIPTION HERE] >

<UrlAction Url=”[PATH TO YOUR FILE “  />

</CustomAction>

</Elements>

Then is it a simple matter of deploying your solution. The above highlighted items can be changed to set the location of where the link appears. Below is are tables that you can use a reference.

The location and group ID values identify a specific place where the custom action must be created (or hidden). See below the possible combinations for both attributes.

2007

2010

Here are the steps I took:

• Added Picture content type to a Shared Documents library on a team site
• Modified the view to include the thumbnail column
• Uploaded a GIF and a JPG to the library

The thumbnail column is unable to find the picture as you can see below.

I did notice that the thumbnail is looking for MMS_gif.jpg and the actual filename is MMS.gif so SharePoint must be doing something to it.

One more thing I noticed is that it works fine if the library is a picture library from the start.

Time to research…

UPDATE:

I have come across this blog entry that details the differences between the picture and image content types. Maybe the answer lies in there. Will keep posting as I find out more.

I must admit that I have not used this feature extensively so if in fact I am missing something please point it out. Or perhaps suggest a way of extending the feature.

UPDATE:

Spoke too soon. Through the use of workflows or “Send to connections”  you can route documents to a repository (content organizer web service) and leave a link in the previous location. It just takes some creative thinking!

If you set AllowPaging=”true” or AllowSorting=”true” on a GridView control without using a DataSourceControl DataSource (i.e. SqlDataSource, ObjectDataSource), you will run into the following errors:

When changing the page on the GridView control:

The GridView ‘GridViewID’ fired event PageIndexChanging which wasn’t handled.

When clicking a column name to sort the column on the GridView control:

The GridView ‘GridViewID’ fired event Sorting which wasn’t handled.

As a result of not setting the DataSourceID property of the GridView to a DataSourceControl DataSource, you have to add event handlers for sorting and paging.

<asp:GridView ID=”gridView” OnPageIndexChanging=”gridView_PageIndexChanging” OnSorting=”gridView_Sorting” runat=”server” />

private string ConvertSortDirectionToSql(SortDirection sortDirection)
{
   string newSortDirection = String.Empty;

   switch (sortDirection)
   {
      case SortDirection.Ascending:
         newSortDirection = “ASC”;
         break;

      case SortDirection.Descending:
         newSortDirection = “DESC”;
         break;
   }

   return newSortDirection;
}

protected void gridView_PageIndexChanging(object sender, GridViewPageEventArgs e)
{
   gridView.PageIndex = e.NewPageIndex;
   gridView.DataBind();
}

protected void gridView_Sorting(object sender, GridViewSortEventArgs e)
{
   DataTable dataTable = gridView.DataSource as DataTable;

   if (dataTable != null)
   {
      DataView dataView = new DataView(dataTable);
      dataView.Sort = e.SortExpression + ” “ + ConvertSortDirectionToSql(e.SortDirection);

      gridView.DataSource = dataView;
      gridView.DataBind();
   }
}

• uninstalling the new version.
• Installing the old version.
• Running stsadm -o copyappbincontent
• Upgrade to the new version.

http://www.allaboutmoss.com/index.php/2010/04/05/webpart-development-part-4-creating-custom-web-part-properties/

In recent blog posts we learnt webPart development, deployment  and adding controls etc..

In this blog post we will see how to add custom properties for SharePoint web part. There are several properties available in SharePoint web part for setting its look and feel like Title, Height and Width etc.. In this example we will see how to add Dropdown, Check box and a Text box in webPart tool pane.

1. Open Visual studio and create a new web part project
2. Open the .cs file
3. import the name space System.ComponentModel;
4. To define the XML namespace to be used for the Custom WebPart, add the below code just above the class declaration. (These values can be whatever you choose and aren’t related to the class name.)
   view sourceprint?

   1.  [DefaultProperty("Text"), ToolboxData("<{0}:WPwithBGcolr runat=server></{0}:DisplayLatestPosts"), XmlRoot(Namespace = "WPwithBGcolr")]
5. Change the base class from System.Web.UI.WebControls.WebParts.WebParttoMicrosoft.SharePoint.WebPartPages.WebPart
6. For adding a text box in tool part pane, add the below property in the class
   view sourceprint?

   01.public string text;

   02.[Category("Advanced Settings"),

   03.Personalizable(PersonalizationScope.Shared),

   04.WebBrowsable, WebDisplayName("Text"),

   05.WebDescription("Enter your text")]

   06.public string Text

   07.{

   08.get { return text; }

   09.set { text = value; }

   10.}
7. For adding a checkbox in tool part pane you need to add the blow code
   view sourceprint?

   01.public Boolean border;

   02.[Category("Advanced Settings"),

   03.Personalizable(PersonalizationScope.User),

   04.WebBrowsable, WebDisplayName("Border"),

   05.WebDescription("Do you want border")]

   06.public Boolean Border

   07.{

   08.get { return border; }

   09.set { border = value; }

   10.}
8. For adding a dropdown in tool part pane , first declare an enum variable and create the property using this new variable as shown in the below code.
   view sourceprint?

   01.public enum ColorByEnum { Red, Blue, Green };

   02.protected ColorByEnum colorBy;

   03.[Category("Advanced Settings"),

   04.Personalizable(PersonalizationScope.User),

   05.WebBrowsable,

   06.WebDisplayName("Background Color"),

   07.WebDescription("Choose a background color for your webpart")]

   08.public ColorByEnum ColorBy

   09.{

   10.get { return colorBy; }

   11.set { colorBy = value; }

   12.}
9. You can retrieve the value, entered by the user, using the below code.
   view sourceprint?

   1.protected override void RenderWebPart(HtmlTextWriter output)        {        output.Write(this.text  );         }
10. For expanding the custom category default we need to override the  function ‘GetToolParts’.�
    view sourceprint?

    01.public override ToolPart[] GetToolParts()

    02.{

    03.ToolPart[] toolpart = new ToolPart[3];

    04.CustomPropertyToolPart custom = new CustomPropertyToolPart();

    05.custom.Expand("Advanced Settings");

    06.WebPartToolPart Wptp = new WebPartToolPart();

    07.Wptp.FrameState = FrameState.Normal;

    08.Wptp.FrameType = FrameType.Default;

    09.toolpart[0] = Wptp;

    10.toolpart[1] = custom;

    11.return toolpart;

    12.}

The following properties can be added to costom controls in the tool part pane.

The custom property will be displayed automatically in the default property pane based on the property type string, bool, int or enum. The following table describes how each of these property types is displayed in the property pane.

In the coming articles we will see how to validate custom controls in tool part pane.

Download the sample source code here.

I am by no means a VMWare expert, in fact this is the first time I am actually using it. Which is pretty sad.

Anyway, I had some issues getting all the separate VM’s to talk to each other consistently. After some fiddling I determined that the network adapter’s on the VM’s work well when set to NAT.  Another important setting was to set the DNS server to the AD server’s IP. Once this was all done the servers could talk properly without any issue.

Ollie