Close modal dialog when SPLongOperation Complete 

protected override void OnClick(EventArgs e)
{
 try{
    using (SPLongOperation longOp = new SPLongOperation(this.Page))
    {
      longOp.LeadingHTML = "Long Operation Title";
      longOp.TrailingHTML = "This may take few seconds.";
      longOp.Begin();
      //--------------------------
      //here code part
      //---------------------


      HttpContext context = HttpContext.Current;
      if (context.Request.QueryString["IsDlg"] != null)
      {
         context.Response.Write("<script type='text/javascript'>window.frameElement.commitPopup();</script>");
         context.Response.Flush();
         context.Response.End();
      }
      else
      {
         string url = SPContext.Current.Web.Url;
         longOp.End(url, SPRedirectFlags.CheckUrl, context, string.Empty);
      }

}
  }
  catch (ThreadAbortException) { /* Thrown when redirected */}
  catch (Exception ex)
  {
     SPUtility.TransferToErrorPage(ex.ToString());
   }
}



































Comments











Post a Comment



















Popular posts from this blog









This content database has a schema version which is not supported in this farm




















Image







  Today i have faced one issue while mount content database to server.   the issue is " This content database has a schema version which is not supported in this farm."   I was getting this error when i ran Mount-SPContentDatabase using powershell.    I tried checking SP versions and other things finally got solution in below way    Reason:  Once you have taken the backup from SharePoint 2013 content database, usually you will restore the database in the target SQL server.  After restoring the database, you will try to restore content database in any one of Webapplication most probably new one. In this stage, you will get the above error message. Solution:  Your source SQL server schema and the destination SQL server schema might not be matched. So you need to update the "Versions" table values in the "Restored Database".  1. Open " Versions " table from any of the existing "Content database"  from the Target SQL Server machine in ...








Read more










Export all documents/Folders permissions to CSV using SharePoint PowerShell





















   $ver = $host | select version  if($Ver.version.major -gt 1) {$Host.Runspace.ThreadOptions = "ReuseThread"}  if(!(Get-PSSnapin Microsoft.SharePoint.PowerShell -ea 0))  {  Write-Progress -Activity "Loading Modules" -Status "Loading Microsoft.SharePoint.PowerShell"  Add-PSSnapin Microsoft.SharePoint.PowerShell  }   #Get the Site collection  $Site= Get-SPSite http://SiteURL   $outputPath = "c:\Permission.csv"   Function GetMyFiles($Folder)  {       Write-Host "+in : "$Folder.Name      foreach($file in $Folder.Files)      {          Write-Host "'t" $file.Name          Add-Content -Path $outputPath -Value  "                     File Name : $($file.Name)"          # $file.Item.RoleAssignments -fore yellow          Add-Content -Path $outputPath -Value "                       ...








Read more










SPUtility.js




















Image







 http://sputility.codeplex.com/      Installation  To use the library, you can just upload SPUtility.js and prototype.js into a document library and put a Content Editor Web Part with some JavaScript code on whichever page you want to modify! Detailed instructions are on the  Installation  page.  Usage Examples:   Set a Text field's value  SPUtility.GetSPField('Title').SetValue('Hello world!');  Set a Text field's value and make it read only  SPUtility.GetSPField('Title').SetValue('Hello world!').MakeReadOnly();  Make a Choice field read only  Before SPUtility.GetSPField('Status').MakeReadOnly(); After  Set a People field and/or Make it Read Only  SPUtility.GetSPField('Assigned To').SetValue('Menke, Kit'); SPUtility.GetSPField('Assigned To').MakeReadOnly();  Hide a field from view  Before SPUtility.GetSPField('% Complete').Hide(); After   








Read more