Close Module Dialog SharePoint from server side Code and javascript

Javascript



C#


//current Context
HttpContext Currentcontext = HttpContext.Current;
//Checking  dialog is  open on this page or not
if (HttpContext.Current.Request.QueryString["IsDlg"] != null)
{
//executing javascript for closing pop on runtime;
Currentcontext.Response.Write("");
Currentcontext.Response.Flush();
Currentcontext.Response.End();

}


from update panel

///

/// Call Runtime Javascript Functions
///
/// type Complete Function and js Code
private void CallJavaScriptMethods(string Script)
{
ScriptManager.RegisterClientScriptBlock(this.Page, this.GetType(), Guid.NewGuid().ToString(), Script, true);
}


ScriptManager.RegisterClientScriptBlock(this.Page, this.GetType(), Guid.NewGuid().ToString(), "window.frameElement.commitPopup();", true);

public static void GetAllListItemsInFolder()
{
            ClientContext clientContext = new ClientContext("http://xxxxxx:000");
            List list = clientContext.Web.Lists.GetByTitle("MainLib");
            CamlQuery camlQuery = new CamlQuery();
            camlQuery.ViewXml = @"
                                   
                                   
                               
";            camlQuery.FolderServerRelativeUrl = "/MainLib/HR";
            ListItemCollection listItems = list.GetItems(camlQuery);
            clientContext.Load(listItems);
            clientContext.ExecuteQuery();
            ListItem itemOfInterest = listItems[0];
            string Itemcreator = itemOfInterest.FieldValues["Created_x0020_By"].ToString();
            string Itemtitle = itemOfInterest.FieldValues["Title"].ToString();
        }

if you trying to upload Large file to you AutoHosted App some thing like 1.5 Gb which more time to execute then you will receive and error especially if you're using MVC.

Add in app web.config :)
 


       
         
           
         
       
   

WebPart Vs App Part

Web Part	App Part
Run on SharePoint Server	Run on external servers or Browser
Run  with User Permissions or will full Permissions (elevated Privilege)	Run with App Identity that is granted specific Permission.
Runs in the Same Domain and environment of the page and its content.	Runs on Different domain providing complete client -side isolation
Could take up a significant amount of CPU cycles for complex operations	Executed outside SharePoint hence SharePoint performance is  not impacted
Not easy to publish globally / locally. It requires installations and activations.	Can be published internally and or to the Microsoft public SharePoint Store

Migrate WebPart to App Part

Migrating Web part to App Part are not 1 : 1 Mapping for code because might be Web Part is Server Side API which not available in App Part. 

To migrate your web part to App Part you have determined hosting Option. Is App Part run in client or its external server? If your web Part contains any kind of intellectual property that you need to secure you should have to use external server. Because client side code is not very secure and easy to reverse engineered. 

Choosing right API which is very important if you're creating SharePoint Hosted App than you have three Option for CSOM flavours : 

• JavaScript

• Silverlight

• Rest.

And if you're doing SharePoint Cloud Hosted App Part you have two flavours.

• . Net 

• Rest

Which you pick it depends on allot of App Requirement and developer skill that you feel more comfortable with it. .net by using .Net you have a much better developer environment and Rapid Application development and with Rest you can take leverage of the new modern style of development.

Evolution of customizations in SharePoint

    Microsoft office SharePoint 2007

• Required IT to Deploying Custom Solution by Console and GAC manually. 

    Microsoft SharePoint 2010

• SharePoint 2010 Sandbox Solution AKA partially trusted and user code solution. 

• Sandbox deployed by Site Collection Administrators.

• Only subsets of Server site API available and external database and web service call is not allowed.    

• Can deploy on SharePoint online. 

        Microsoft SharePoint 2013

•         Cloud App Module which runs Outside the SharePoint server 
•         Better life cycle installs > update > install. 
•          App Store to Manage Apps.

Advantages Cloud App Module.

If your organization is really looking for a Cloud Scalable Solution. This is the Right Architecture for you. The Cloud App Module is running totally outSide the SharePoint. Which allow developers to manage their app isolated with effecting other Solutions or farm itself  You can update your Apps without re installing and activating them. In case of error or bug your app will not effect on whole farm which helps SharePoint Administrators allot.  By using Cloud hosted App Module you take lavage of new web standards like MVC, MVVM, Html 5, Jquery. At the same time you take all advantages of SharePoint with chrome control cross domain library. SharePoint list is not recommended for highly transactional or Relationship data Module. In App Module You can access Data outside the SharePoint and external resources. Like Web services and SQL and take lavage with your app module. 

 SharePoint 2013 app module much better development life cycle than SharePoint 2010. Which meet the fashion of modern App development and publishing life cycles.

SP App Design - A Choice of Three Approaches

 

 

 

It was Great Fun to meet Sharepointers in UAE. Salman Ahmed and All Other Community members done great effort and hope so in  near feature we will do some more SharePoint Community events very soon. 

I was try to Add Item in  Custom list which in hosted Site from SharePoint hosted App.  then try to open same Add Form in Dialogbox and Get this Error. then I Find one very helpful Post  By Humberto Lezama.

xxxxxxxx-------------a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.

This is because SharePoint 2013 adds the x-frame-options header set to same origin.

to Solve this Problem.

Add this Control on Top of the App Page.

The following tells SharePoint to allow this page to be hosted in an IFrame -

<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

Hope So it will help others