The Web application at https://servername:portnumber/sitename/ could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.

You are using a very simple code and the exception occurs at the very first line while opening new instance of an SPSite :

using (SPSite osite = new SPSite("https://blrs2r11-1c/"))
        {
            using (SPWeb oweb = osite.OpenWeb())
            {
               // Response.Write(oweb.Title);
                Label1.Text = oweb.Title;
            }
        }

Well, if it was a console application, then setting Output type as Any CPU\x64 and target build as .Net 3.5 will work :

https://blogs.msdn.com/b/sowmyancs/archive/2010/04/01/filenotfoundexception-the-web-application-at-http-url-could-not-be-found.aspx

However, this is an ASP.NET web application\website type of project.

Please note that the issue is not specific to any specific version of SharePoint or Visual Studio as such, because it’s more to do with the fact that this behavior is

only when SharePoint is on a 64 bit server.Here' are some observations that I would like to enlist regarding this error :

Are you trying F5 debugging of your asp.net webapplication? If yes, you would always get the error because the built in ASP.Net Development server (WebDev.WebServer.exe) a.k.a Cassini is a 32 bit process while SharePoint is 64 bit.

If you however host the website\webapplication under IIS,then you should be able to use the code , if you take care of the following :

1. App Pool identity of the asp.net webapplication has rights over SharePoint - preferably make them identical

2.And IIS Website is using windows authentication (failing which, You would get 401 unauthorized exception while accessing SPWeb's instance variable's properties. Surprisingly, not at OpenWeb()).

Now in my custom application page, I needed to present a list of such User Solutions(templates, sandbox solutions etc) and be able to activate , deactivate, remove them from this page.

The fact that it’s a Catalog , or in simpler terms a Library, the items need to be treated as SPListItem and WSPs as SPListItem.File

I am sharing the code snippets which I tested successfully in a console application below:

using (SPSite oSite = new SPSite("https://mss2010"))
            {
                using (SPWeb web = oSite.OpenWeb())
                {

                    SPWeb rootweb = web.Site.RootWeb;

                    // Code to ACtivate solution
                    SPList solGallery  = rootweb.Site.GetCatalog(SPListTemplateType.SolutionCatalog);
                    foreach (SPListItem item in solGallery.Items)
                    {
                        if (item.File.Name.Equals("site1.wsp"))
                        {
                            rootweb.Site.Solutions.Add(item.ID);
                            break;
                        }
                    }
                    // Code to DeACtivate solution
                    foreach (SPUserSolution solution in rootweb.Site.Solutions)
                    {
                        if (solution.Name.Equals("site1.wsp"))
                        {
                            rootweb.Site.Solutions.Remove(solution);
                        }
                    }
                    // Code to Delete solution
                    SPList solGallery1 = rootweb.Site.GetCatalog(SPListTemplateType.SolutionCatalog);
                    foreach (SPListItem item in solGallery1.Items)
                    {
                        if (item.File.Name.Equals("site1.wsp"))
                        {
                            solGallery1.Items.DeleteItemById(item.ID);
                            break;
                        }
                    }

                }
            }

Let me start off with this one.

Well.. this one is not exactly about SharePoint 2010, except the error message and that sites can now be saved as .wsp packages (which you already must be aware of if you are getting this error), which is :

[System.InvalidOperationException] = {"Error copying temporary solution file to solutions gallery: _catalogs/solutions/site16.wsp"}

….at Microsoft.SharePoint.SPSolutionExporter.ExportWebToGallery(SPWeb web, String solutionFileName, String title, String description, ExportMode exportMode, Boolean includeContent, String workflowTemplateName, String destinationListUrl)

at Microsoft.SharePoint.SPWeb.SaveAsTemplate(String strTemplateName, String strTemplateTitle, String strTemplateDescription, Boolean fSaveData) at….

All I am trying is SPWeb.SaveAsTemplate method to save a site as template (.wsp) from code that runs in a custom Application page.The same code runs fine from a console application though.I checked the ULS logs and found that the actual exception is :

SPSolutionExporter: Microsoft.SharePoint.SPException: The security validation for this page is invalid. Click Back in your Web browser, refresh the page, and try your operation again

Through reflector, I was able to track that SPWeb.SaveAsTemplate internally calls Microsoft.SharePoint.SPSolutionExporter.ExportWebToGallery

From here, I analyzed that the code fails while adding the .wsp file (which has already been generated by now in the code of ExportWebToGalleryMethod and stored as a .TMP file in %temp% directory) to the User Solutions Gallery (_catalogs/solutions). The InvalidOperationException, though is raised in this method with the custom message string  - SPResource.GetString("SitePackaging_ErrorCopyingTemporarySolutionFileToSolutionsGallery"…

So good for analysis and exploring new APIs, but as it turns out that the actual exception is the good old “The security validation for this page is invalid” SPException and I probably missed some basic stuff ….like AllowUnsafeUpdates. Huh, but I did make sure I set it correctly. But not for the correct objects.Since I was running the custom application page from a subsite, while the solutions gallery is on the RootSite, I added the statement web.Site.RootWeb.AllowUnsafeUpdates = false and the error was gone.

    protected void Page_Load(object sender, EventArgs e)
        {
            SPWeb web = SPContext.Current.Web;
            try
            {
                //SPUtility.ValidateFormDigest();
                web.AllowUnsafeUpdates = true;
                web.Site.RootWeb.AllowUnsafeUpdates = true;

               //Error here: “Error copying temporary solution file to solutions gallery: _catalogs/solutions/site16.wsp” 
                web.SaveAsTemplate(web.Title, web.Title, "", false);

                //SPSolutionExporter.ExportWebToGallery(web, "solutionFileName", "templateTitle", "templateDescription", SPSolutionExporter.ExportMode.FullReuse, false);

                web.AllowUnsafeUpdates = false;
                web.Site.RootWeb.AllowUnsafeUpdates = false;
                result = "Success";
            }
            catch (Exception Ex)
            {
                result = Ex.StackTrace;
            }
            finally
            {
                Label1.Text = result;
            }
            
        }

Other way would be to use SPUtility.ValidateFormDigest() as the first thing on the custom application page. For a comprehensive understanding on all things 

AllowUnsafeUpdates, two part series by Hristo Pavlov is a great place :

https://hristopavlov.wordpress.com/2008/05/16/what-you-need-to-know-about-allowunsafeupdates/

Happy Investigating SharePoint !!

https://sharepoint.microsoft.com/blogs/GetThePoint/Lists/Posts/Post.aspx?ID=122

https://www.heathersolomon.com/blog/articles/brandsppart2.aspx

For the purpose of an example , consider this style element (in my case , it references an image from a custom theme ) :

#siteLogo a {

      background: #94b7d7 url('_themes/FB/FBLogo.gif') no-repeat top left;

      width:200px;

      height:60px;

      }

Create a custom master page based on any OOB master page (make a copy of OOB Blueband.master)
- remove the DOCTYPE declaration on top
- Add an anchor tag in Placeholder Main, such as :

<tr>

            <td id="GlobalTitleAreaImage" class="ms-titleimagearea" width="50%" align="left">

            <!-- changed logo for FB Sharepoint Template -->

                  <div id="siteLogo">

                        <a href=https://www.microsoft.com target="_blank"></a>

                  </div>

            </td>

      </tr>

You will notice that when such a custom theme is applied to the site, it will display fine in IE (background images will come up fine), but in non-IE browsers, (I tested in FireFox) , images will not come up.

CAUSE :
The root cause of the issue is that CustomSite.master doesn’t have a <!DOCTYPE tag.
Per the W3 visual formatting model - <https://www.w3.org/TR/CSS2/visuren.html>
Anchors are inline elements and shouldn’t have an explicit height\width. However, since IE ignores even if the master page has no doctype declaration , IE (without a doctype) displays images while FireFox does not.

SOLUTION :
So, the solution could be to follow either of below approaches :

Approach1 :

Include display and float elements along with anchor style elements. For e.g. I induced below highlighted change in my custom CSS file ,and was able to get the image displayed in FireFox :

#siteLogo a {

      background: #94b7d7 url('_themes/FB/FBLogo.gif') no-repeat top left;

      width:200px;

      height:60px;

      display:block;

      float:left;

      }

Approach2:

Use DocType declaration in custom master page. So far, I tested by adding doctype element in my custom master page (all out-of-the-box masterpages have doctype elements) :

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "https://www.w3.org/TR/html4/loose.dtd">

There is some good information on DOCTYPE tag and SharePoint master pages available at below links:

https://www.heathersolomon.com/blog/archive/2007/02/21/6213.aspx

https://www.sharepointkings.com/2009/10/moss-2007-master-page-doctype-issue.html

function CreateCopyControl()
{
      try
      {
            copyctl = new ActiveXObject("STSUpld.CopyCtl");
      }
      catch(e)
      {
            return null;
      }
      return copyctl;
}

Now I was getting a Blank Dialog Box on Clicking Ok button on Copy.aspx. Since it’s an ActiveX, it could be a client side issue(IE-Office Integration) – and you might want to check accessing the site on another environment.
Also check following registry key, if it is there - "HKCR\STSUpld.CopyCtl"

One of possible conditions leading to this problem could be Multiple versions of Office installed (in the client environment..).

In this scenario, customer had SharePoint Designer also installed on the client machine where the issue occurs. The resolution for this case was - Open “Microsoft Office SharePoint Designer” IDE and Click on the “Help” menu to open up the list. Click on the “Office Diagnostics” help menu and wait till this operation completes.

Error in the Site Data Web Service. (*** 'Type' is an unexpected token. The expected token is '='. Line 246, position 344.) Local Office SharePoint Server sites

Above is the error which one of my customers reported in crawl logs when crawling a List created from a custom list definition which is using a custom content type.I would like to share the resolution to this error hoping it might be useful for someone.

Firstly, we had deployed custom site columns and content type via Features, which in turn were being used in list definition.Some of the custom Fields used spaces and special characters in the “Name” and “StaticName” in the fields.xml (used in the ContentType Feature) and schema.xml of List Definition Feature.

For e.g :

 <Field
    ID="{9FB8728C-5F3C-4e29-965A-A7B26E0ECE35}"
    Name="Document Type #"
    DisplayName="Document Type"
    SourceID="https://schemas.microsoft.com/sharepoint/v3/fields"
    StaticName="Document Type #"
    Type="Choice"
    Required="FALSE"
    Group="Custom">

As highlighted above, in this case the issue was because of spaces in “Document Type #” in the Name column above.As you know Xml Name translates to

SPField.InternalName while StaticName translates to SPField.StaticName and DisplayName is the SPField.Title.

Because of special characters in InternalName, the crawl fails with Error in the Site Data Web Service. Infact, once I tested after removing spaces, I got another similar error, this time for the # character in the name. Which shows that not only space, but special characters also aren’t allowed for field internal names.

Crawl uses GetContent method of SiteData.asmx webservice (https://msdn.microsoft.com/en-us/library/ms772581.aspx), and I was able to reproduce the issue by programmatically calling this webservice for the particular list item which contains data in field with Internalname - “Document Type #”

Ultimately, issue was resolved once I made sure to update the “Name” of the field In all three places, that is : fields.xml (where site columns are defined), contenttypes.xml (where fieldrefs for the content type are defined) and schema.xml (of list definition feature).

Just in case you are new to customizing CQWP following posts are great places to start:

https://msdn.microsoft.com/en-us/library/bb850574%28office.12%29.aspx

https://msdn.microsoft.com/en-us/library/aa981241.aspx

https://www.heathersolomon.com/blog/articles/customitemstyle.aspx

· The ULS logs exhibit these entries when the issue occurs :

Potentially excessive number of SPRequest objects (11) currently unreleased on thread 1

......Microsoft.SharePoint.Publishing.WebControls.ContentByQueryWebPart.getWeb(String webUrl)     at Microsoft.SharePoint.Publishing.CrossListQueryCache.GetSiteData(SPSite site, String webUrl)     at Microsoft.SharePoint.Publishing.CrossListQueryCache.GetSiteData(SPSite site)     at Microsoft.SharePoint.Publishing.WebControls.ContentByQueryWebPart.IssueQuery()     at Microsoft.SharePoint.Publishing.WebControls.ContentByQueryWebPart.GetXPathNavigator(String viewPath)     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.PrepareAndPerformTransform()     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.PerformSelect()     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.DataBind()     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.EnsureDataBound()     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.CreateChildControls()     at System.Web.UI.Control.EnsureChildControls()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.WebControls.WebParts.WebPart.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal() ..............

· While debugging through a custom webpart deriving from CQWP, following exception appears after a few seconds in the ‘ModifyXsltArgumentList’ function of CQWP.

An unhandled exception of type 'System.StackOverflowException' occurred in mscorlib.dll

· On applying any basic XSL template , which doesn’t remove HTML mark-up from the @Body field of the CQWP resultset , such as below :

<xsl:template name="ShowXML" match="Row[@Style='ShowXML']" mode="itemstyle">

    <xsl:for-each select="@*">

      <br />

      Name: <xsl:value-of select="name()" />

      <br />Value:<xsl:value-of select="." />

    </xsl:for-each>

  </xsl:template>

doesn’t result in any loop-back or crash.

Here’s the “item-style” xsl that can be used to trim the blog post’s body content. Here we have to use a “removemarkup” template\function that will remove the html markup as blog post’s body will be stored in its raw form in the content database.

  <xsl:template name="removeMarkup">

    <xsl:param name="string" />

    <xsl:choose>

      <xsl:when test="contains($string, '&lt;')">

        <xsl:variable name="nextString">

          <xsl:call-template name="removeMarkup">

            <xsl:with-param name="string" select="substring-after($string, '&gt;')" />

          </xsl:call-template>

        </xsl:variable>

        <xsl:value-of select="concat(substring-before($string, '&lt;'), $nextString)" />

      </xsl:when>

      <xsl:otherwise>

        <xsl:value-of select="$string" />

      </xsl:otherwise>

    </xsl:choose>

  </xsl:template>

 

  <xsl:template name="CQWP_Blog" match="Row[@Style='CQWP_Blog']" mode="itemstyle">

    <xsl:variable name="SafeLinkUrl">

      <xsl:call-template name="OuterTemplate.GetSafeLink">

        <xsl:with-param name="UrlColumnName" select="'LinkUrl'"/>

      </xsl:call-template>

    </xsl:variable>

    <xsl:variable name="SafeImageUrl">

      <xsl:call-template name="OuterTemplate.GetSafeStaticUrl">

        <xsl:with-param name="UrlColumnName" select="'ImageUrl'"/>

      </xsl:call-template>

    </xsl:variable>

    <xsl:variable name="DisplayTitle">

      <xsl:call-template name="OuterTemplate.GetTitle">

        <xsl:with-param name="Title" select="@Title"/>

        <xsl:with-param name="UrlColumnName" select="'LinkUrl'"/>

      </xsl:call-template>

    </xsl:variable>

    <xsl:variable name="LinkTarget">

      <xsl:if test="@OpenInNewWindow = 'True'" >_blank</xsl:if>

    </xsl:variable>

 

       <xsl:variable name="bodyContent">

      <xsl:call-template name="removeMarkup">

<!--<xsl:with-param name="string" select="$bodyContent" />-->

        <xsl:with-param name="string" select="substring(@Body,1,1000)" />

      </xsl:call-template>

    </xsl:variable>

 

   <div id="linkitem" class="item">

      <xsl:if test="string-length($SafeImageUrl) != 0">

        <div class="image-area-left">

          <a href="{$SafeLinkUrl}" target="{$LinkTarget}">

            <img class="image" src="{$SafeImageUrl}" alt="{@ImageUrlAltText}" />

          </a>

        </div>

      </xsl:if>

      <div class="link-item">

        <xsl:call-template name="OuterTemplate.CallPresenceStatusIconTemplate"/>

        <a href="{$SafeLinkUrl}" target="{$LinkTarget}" title="{@LinkToolTip}">

          <span class="ms-announcementtitle">

            <xsl:value-of select="$DisplayTitle"/>

          </span> (written <xsl:value-of select="@Created" /> by <xsl:value-of select="@Author" />)

        </a>

        <div class="description">

    <!--<xsl:value-of select="substring($bodyContent,1,1000)" disable-output-escaping="yes" />-->

          <xsl:value-of select="$bodyContent" disable-output-escaping="yes" />

          ...(<a href="{$SafeLinkUrl}" mce_href="{$SafeLinkUrl}" target="{$LinkTarget}" title="{@LinkToolTip}">more</a>)

          <br /><br />

        </div>

      </div>

    </div>

  </xsl:template>

Basically, we only want a substring (@Body, 1, 1000) in CQWP (w\o htmlmarkup) and then append "more..." to it, But the issue above is that we were first passing the whole  "@Body" field value to the 'removemarkup' function (via  bodyContent variable) , afterwards calling substring($bodyContent,1,1000) to take a part of it to display. and then appending "more..." to it, as in :

<xsl:value-of select="substring($bodyContent,1,1000)" disable-output-escaping="yes" />

We have to make sure we pass on a substring of body not only while displaying it (which is in div tag towards the end), but also to removemarkup function.

In summary ,if you are facing performance issues while using CQWP, which you have altered to use a custom itemstyle of your own, then check the ItemStyle for such things which are easy to miss but can lead to serious performance issue.

The menu Item “Edit Document” is rendered via AddDocLibMenuItems function in CORE.JS. Possible approaches to achieve this override in a supported way :

Option1 :

a)Create a customCORE.JS

b)Add extra code, explained in next few lines below in AddDocLibMenuItems function

c)Create a custom masterpage and add a scriptlink for customCORE.js

Option2:

Similar to above option, but instead of creating  customCORE.js, we can override either the  AddDocLibMenuItems or add an implementation of Custom_AddDocLibMenuItems on the masterpage itself in a script tag, after the scriptlink for CORE.js <SharePoint:ScriptLink language="javascript" name="core.js" Defer="true" runat="server" />)

Option3:

If the change is needed only on one page(View Page of one Library), add a CEWP with an implementation of Custom_AddDocLibMenuItems, which is identical to AddDocLibMenuItems from CORE.js + additional check for the file extension talked about below.

We can override the AddDocLibMenuItems function to not to render the “Edit Document” menu, when the file is of a particular file extension.(In below example, I am checking if it’s a .txt file, then skip the part that renders the “Edit Document” menu.)Below highlighted, is the code that I put in the AddDocLibMenuItems in CORE.js

function AddDocLibMenuItems(m, ctx)

{

...

    else

        {

            var strExt  = GetAttributeFromItemTable(itemTable, "Ext", "FileType"); 

            if(strExt != "txt")

                  {                

                        var   objEditor=StsOpenEnsureEx(currentItemOpenControl+".3");

                        if (objEditor !=null ) 

                              strDisplayText=L_EditInApplication_Text;

                }

        }

                  if (strDisplayText !="")

                  {

                        strAction="editDocumentWithProgID2('"+currentItemFileUrl+"', '"+currentItemProgId+"', '"

+currentItemOpenControl+"', '"+bIsCheckout+"', '"+ctx.HttpRoot+"', '"+currentItemCheckedoutToLocal+"')";

                              strImagePath=ctx.imagesPath+currentItemIcon;

                              menuOption=CAMOpt(m, strDisplayText, strAction, strImagePath, null, 240);

                              menuOption.id="ID_EditIn_"+currentItemAppName;

                  }

                        }

                  }

            }

      }

...

}

HTH & Happy Customizing SharePoint !!

-In a List there’s a column called COMMENTS (Multiple Lines of Text w/ Append Changes to Existing Text)  where people put their comments for that list item whenever they edit it. It’s a column with Append Changes property set.

-When we use the option "Export to Spreadsheet" we only see the latest comment and not all the comments in the spreadsheet.

Since Out of the Box , "Export To SpreadSheet" doesn't export values of the previous versions , it only extracts the current Published Version. And therefore no values for Comments made in previous versions are exported.

I though of sharing here, the SharePoint OM code that I used in above scenario and which will do the job of extracting not just the current Version , but all previous versions.In other words -a Code Sample to export Version History of Items in a List :

I will lay out the steps that I followed to use the code. Below is the structure of the list that I used for testing. Default OOB Generic List, with few Columns I added : - Col1(single line of text), Col2(single line of text), Comments (Multiple lines of text, Append Changes to Existing Text).

Below is the sample code  that can used to extract Items with their Versions, and thus the Comments, who made the Comments  (Modified By),and when (Modified Date), respective Version Number.

   1:  using System;

   2:  using System.Collections.Generic;

   3:  using System.Linq;

   4:  using System.Text;

   5:  using Microsoft.SharePoint;

   6:  using System.IO;

   7:  using System.Data;

   8:  namespace ExportVersionstoCSV

   9:  {

  10:      class Program2

  11:      {

  12:          static void Main(string[] args)

  13:          {

  14:              Console.WriteLine(@"Enter View URL of the List you want Exported. e.g http:\\site\Lists\List1\MyView.aspx");

  15:              Console.WriteLine(@"Where ""MyView"" signifies the View to use, which will determine number of columns to be exported");

  16:   

  17:              string strSite = Console.ReadLine();

  18:              Console.WriteLine("Enter filepath to store the Version content. e.g C:\\ListVReport.csv");

  19:              string strPath = Console.ReadLine();

  20:              SPSite site = new SPSite(strSite);

  21:              SPWeb webmain = site.OpenWeb();

  22:              SPList oList = webmain.GetListFromWebPartPageUrl(strSite);

  23:              SPView oViewObj = webmain.GetViewFromUrl(strSite);

  24:              SPView targetView = oViewObj;

  25:              

  26:              DataTable dtSource = oList.GetItems(targetView).GetDataTable();

  27:              System.Collections.Specialized.StringCollection ostrCollFinal = new System.Collections.Specialized.StringCollection();

  28:              foreach (DataColumn oColumnObj in dtSource.Columns)

  29:              {

  30:                  ostrCollFinal.Add(oList.Fields.GetFieldByInternalName(oColumnObj.ColumnName).Title);

  31:              }

  32:              CreateCSVFile(dtSource, strPath, ostrCollFinal, oList);

  33:          }

  34:          public static void CreateCSVFile(DataTable dt, string strFilePath, System.Collections.Specialized.StringCollection ostrCollparam, SPList oList)

  35:          {

  36:              // Create the CSV file to which grid data will be exported.

  37:              StreamWriter sw = new StreamWriter(strFilePath, false);

  38:              // First we will write the headers.

  39:              int iColCount = ostrCollparam.Count;

  40:              int ColPos = 0;

  41:              for (int i = 0; i < iColCount; i++)

  42:              {

  43:                  sw.Write(ostrCollparam[i]);

  44:                  if (ostrCollparam[i].Equals("Comments"))

  45:                  {

  46:                      ColPos = i;

  47:                  }

  48:                  if (i < iColCount - 1)

  49:                  {

  50:                      sw.Write(",");

  51:                  }

  52:              }

  53:              sw.Write(sw.NewLine);

  54:              // Now write all the rows.

  55:              foreach (DataRow dr in dt.Rows)

  56:              {

  57:              

  58:                  SPListItemVersionCollection oVColl = oList.GetItemById(int.Parse(dr["ID"].ToString())).Versions;

  59:                      foreach (SPListItemVersion oV in oVColl)

  60:                      {

  61:                          for (int i = 0; i < iColCount; i++)

  62:                          {

  63:                              if (oV[ostrCollparam[i]] != null)

  64:                              {

  65:                                  if (ostrCollparam[i].Equals("Modified By"))

  66:                                  {

  67:                                      sw.Write(oV[ostrCollparam[i].ToString()].ToString().Split('#')[1].ToString().Trim(new char[]{','}));

  68:                                  }

  69:                                  else

  70:                                  {

  71:                                      sw.Write(oV[ostrCollparam[i].ToString()].ToString());

  72:                                  }

  73:                              }

  74:                              if (i < iColCount - 1)

  75:                              {

  76:                                  sw.Write(",");

  77:                              }

  78:                          }

  79:                          sw.Write(sw.NewLine);        

  80:                      }

  81:               

  82:              }

  83:              sw.Close();

  84:          }

  85:      }

  86:  }

  87:   

Here's a screenshot of the sample OutPut :

If it was a document Library, then code will need to be modified to pick values from SPfile.Versions instead of SPListItem.Versions.

Hope this helps you save sometime !!