Wednesday, December 25, 2013

JQuery hints

Set a field value: $('input[title=Email]').attr({value:'test email'});

Hide a row: $('h3:contains("Title")').closest('tr').hide();

Change event on choice field: $('select[title=Display]').change(function(){alert($('select[title=Display]').val())});

Condition: if($('select[title=Display]').val()=="Yes") {alert($('input[title=Email]').val());}

Tuesday, August 13, 2013

Add Custom Attachment Control & Disable Attachment button on Ribbon

<!-- Add Attachment File control -->

<table width="100%">
<tbody><tr>
<td width="190" class="ms-formlabel" valign="top" style="font-family: verdana; color: #525252; font-size: 1em; font-weight: normal">Add Attachments: </td>
<td class="ms-formbody" id="attachmentsOnClient" valign="bottom">
<span dir="ltr">
<input name="fileupload0" title="Name  " class="ms-fileinput" id="onetidIOFile" type="file" style="width: 386px"/> </span>
</td></tr>
<tr><td>&#160;</td>
<td class="ms-attachUploadButtons">
<input id="attachOKbutton" onclick="OkAttach()" type="button" value="OK  " style="width: 5.8em; height: 1.8em"/> <span id="idSpace"></span></td>

</tr></tbody></table>
 

<!-- Hide File Attachment Button on Ribbon-->

<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.10.1/jquery.min.js">
</script><script type="text/javascript">
$("span.ms-cui-ctl-largelabel:contains('Attach')").parent("a").hide();

$("span.ms-cui-groupTitle:contains('Actions')").hide();
 </script><!-- Hide File Attachment Button -->

Use in list forms & Enjoy :) 

Saturday, July 20, 2013

Save Site as template using Object Model

public void savesiteastemplate(string webname)
{
 string templatename;
string templatetitle;
string templatedesc;
try
{
SPSecurity.RunWithElevatedPrivileges(delegate()
{
using (SPSite _site = new SPSite(SPContext.Current.Site.ID))
{
_site.AllowUnsafeUpdates =true;
using (SPWeb oweb = _site.RootWeb)
{
SPWebCollection _webcol = _site.AllWebs;
oweb.AllowUnsafeUpdates = true;
foreach (SPWeb _web in _webcol)
{
if (string.IsNullOrEmpty(txtwebname.Text))
{
msg = "Enter the name of a web";
}
else if (_web.Name.ToLower() == txtwebname.Text.ToLower())
{
templatetitle = _web.Name + "Template";
templatename = _web.Name + "Template";
_web.SaveAsTemplate(templatename, templatetitle, templatedesc,false);
msg = "Template Saved Successfully";
txtwebname.Text = "";
break;
}
else
{
msg = "web is not available";
}
}
oweb.AllowUnsafeUpdates= false;
PnlMain.Controls.Add(new LiteralControl(msg));
_site.AllowUnsafeUpdates =false;
}
}
});
}
catch (Exception ex )
{
lblmsg.Text = ex.Message;
}
}


Where
strTemplateName
Type: System.String
The name to use for the template on the Create form and also for the file name of the solution package (.wsp) that contains the template. If a solution package with the same file name already exists, a numeric suffix is added to the name when the solution file name is formed. For example, if you pass "Test", the method tries to create a template file named "Test.wsp". If that name is taken, it tries "Test2.wsp". If that name is in use, it tries "Test3.wsp" and so on.
strTemplateTitle
Type: System.String
A string that contains the display name of the site template.
strTemplateDescription
Type: System.String
A string that contains the description of the site template.
fSaveData
Type: System.Boolean
true if data on the website is saved as part of the site template; otherwise, false.

Thursday, April 11, 2013

Difference Between SharePoint Application Pages Vs Site Pages


Difference Between SharePoint Application Pages Vs Site Pages

Application Pages:
  • Application pages are stored in the server’s file system. 
  • SharePoint Designer tool cannot be used with application pages. 
  • Application pages cannot be used within sandboxed solutions. 
  • An Application page cannot be customized and modified by end user, instead a developer is required. 
  • These are the normal .aspx pages deployed within SharePoint. Most common of them are the admin pages found in _layouts folder.
  • These are deployed either at the farm level or at application level. If they are deployed within _layouts folder or global SharePoint Virtual Directory, then they can be used by any SharePoint application (available at farm level), otherwise they can be deployed at application level only by creating a virtual directory.
  • These are typical ASP.Net aspx pages and can utilize all of the functionalities available within ASP.Net including code-behind, code-beside, inline coding etc.
  • These are compiled by .Net runtime like normal pages.
  • If you deploy your custom ASPX pages within _layouts folder or within SharePoint application using a virtual directory, you will not be able to use SharePoint master pages and have to deploy your master page within the virtual directory or _layouts folder.
  • Application Pages cannot use contents as this concept is associated with SharePoint Page Layouts not with ASP.Net.
  • Since application pages are compiled once, they are much faster
  • Normally application pages are not web part pages, hence can only contain server controls or user controls and cannot be personalized by users.
  • Easiest way to deploy your existing ASP.Net web site within SharePoint is to deploy its pages as Application Pages within SharePoint. In this way you can convert any ASP.Net web solution as SharePoint application with minimal efforts.
  • SharePoint specific features like Information Management Policies, Workflows, auditing, security roles can only be defined against site pages not against application pages.
  • Application pages can be globalized using Resource files only. 
Site Pages:
  • Site Pages is a concept where complete or partial page is stored within content database and then actual page is parsed at runtime and delivered to end-users.
  • Site pages can be edited by using SharePoint Designer tool.
  • Site pages are used within Sandboxed solutions. 
  • A site page can be customized and modified by end user. 
  • Pages stored in Pages libraries or document libraries or at root level within SharePoint (Wiki pages) are Site Pages
  • You must be thinking why we should use such pages? There are many reasons for this. One of the biggest catch of the SharePoint is the page layouts, where you can modify page once for a specific content type and then you can create multiple pages using the same page layout with different contents. In this case, contents are stored within database for better manageability of data with all the advantages of a data driven system like searching, indexing, compression, etc and page layouts are stored on file system and final page is created by merging both of them and then the outcome is pared by SharePoint not compiled.
  • Site Pages can contain web parts as well as contents placeholders, and all of them are stored per page-instance level within database and then retrieved at run time, parsed and rendered.
  • Another advantage is they are at user-level not at web-application or farm level and can be customized per site level.
  • Since their definition is retrieved from database, they can utilize master pages stored within SharePoint masterpages library and merged with them at run time for rendering.
  • They are slower as compared to Application pages as they are parsed everytime they are accessed.
  • SharePoint specific features like Information Management Policies, Workflows, auditing, security roles can only be defined against site pages not against application pages.
  • Since they are rendered not compiled hence it is not easy to add any inline code, code behind or code beside. Best way of adding code to these pages is through web-parts, server controls in master pages, user controls stored in "Control Templates" folder or through smart parts. If you want to add any inline code to master page, first you need to add following configuration within web.config:<PageParserPaths>
            <PageParserPath VirtualPath="/_catalogs/masterpage/*" CompilationMode="Always" AllowServerSideScript="true" IncludeSubFolders="true" />
    </PageParserPaths>
  • To add code behind to SharePoint master pages or page layouts.
  • Since Site pages are content pages, hence all SharePoint specific features like Information Management Policies, Workflows, auditing, security roles can only be defined against site pages.
  • Variations can only be applied against Site pages for creating multilingual sites.
  • "SPVirtualPathProvider" is the virtual path provider responsible for handling all site pages requests. 

Friday, March 29, 2013

IIS, Worker Process, Application Pool


What is IIS?
IIS (Internet Information Server) is one of the most powerful web servers from Microsoft Corporation that is used to host the Asp.Net web application. IIS has its own ASP.NET process engine to handle the ASP.NET request. So, when request comes from client to server, IIS takes the request and process it and send response back to the clients.
IIS means when request comes from client to the server a lot of operation is performed before sending response to the client. This is about how IIS process the request.
What is Worker Process?
Worker process (w3wp.exe) runs the ASP.NET application in IIS. This process is responsible to manage all the request and response that are coming from the client system. All the ASP.NET functionality runs under the scope of worker process. When request comes to the server from a client worker process is responsible to generate the request and response.
In single word, we can say worker process is the heart of ASP.NET web application runs on IIS.
What is Application Pool?
Simply to say about what is application pool is: A group of one or more URLs are served by a particular worker process or set of worker processes.
Application pool is the container of worker process. Application pools are used toseparate sets of worker processes that share same configuration. Application pools enable a better security, reliability, and availability for any web application.
The worker process servers as the process boundary that separates each application pool so that when one worker process or application is having an issue or recycles, other applications or worker processes are not affected. This makes sure that a particular web application doesn’t impact other web application as they are configured into different application pool.
Application pool with multiple worker process is called “Web Garden”.
http://msdn.microsoft.com/en-us/library/gg552610.aspx
Why are application pools important?
They provide a way for multiple sites to run on the same server but still have their own
worker processes and identity.
Note:
• Isolation of Different Web Application.
• Individual worker process for different web application.
• More reliably web application.
• Better Performance.
How to find the application pool account for a web application?
Go to IIS settings (type inetmgr in command mode) and select the web application on left pane and click on the “Basic Settings” on the right pane.

Thursday, March 28, 2013

Send Email using Object Model

We will discuss various methods of Sending an e-mail in SharePoint 2010.
In First we need to configure Out going email on Central Administration.
Method 1 : –Code retrieves the SMTP host’s address from the SharePoint configuration database.

public static bool SendMail(string Subject, string Body,bool IsBodyHtml, string From, string To, string Cc, string Bcc)
{
bool mailSent= false;
try
{
SmtpClient smtpClient = new SmtpClient();
smtpClient.Host = SPContext.Current.Site.WebApplication.
OutboundMailServiceInstance.Server.Address;
MailMessage mailMessage = new MailMessage(From, To, Subject, Body);
if (!String.IsNullOrEmpty(Cc))
{
MailAddress CCAddress = new MailAddress(Cc);
mailMessage.CC.Add(CCAddress);
}
if (!String.IsNullOrEmpty(Bcc))
{
MailAddress BCCAddress = new MailAddress(Bcc);
mailMessage.Bcc.Add(BCCAddress);
}
mailMessage.IsBodyHtml = IsBodyHtml;
smtpClient.Send(mailMessage);
mailSent = true;
}
catch (Exception) { return mailSent; }
return mailSent;
}
This ensures that you get the advantages of.NET-style mail delivery while keeping your configuration in Central Administration.
If however, you are not working in a SharePoint context, you can get the SPWebApplication reference from a new SPSite object like below
public static string GetSharePointMailService(string mysite)
{
string address;
using (SPSite site = new SPSite(mysite))
{
address = site.WebApplication.OutboundMailServiceInstance.Server.Address;
}
return address;
}
Method 2 : – This uses the embedded SharePoint SendEmail which has fewer capabilities, but is as straightforward as possible, and is the preferred approach if you simply want to send e-mail:
SPUtility.SendEmail(web, useHtml, htmlEncode, to, subject, htmlBody)
The Paramets are :
web(SPWeb) – An object that represents the site
headers(StringDictionary) – A collection of additional headers
useHtml(bool) – Used to append an HTML tag to the message (true)
htmlEncode(bool) – Encodes the message and replaces characters in HTML tags with entities
to(string) – The address to which to send the e-mail
subject(string) – Contains the subject for the e-mail message
htmlBody(string) – Contains the body of the e-mail message
addFooter(bool) – Used if there is a footer to be appended to the e-mail
The headers parameter is used instead of the to and subject parameters. It allows you to set all possible mail headers and forces you to add at least the to header that way. An example follows:
StringDictionary headers = new StringDictionary();
headers.add(“to”,”authors@apress.com”);
headers.add(“cc”,”joerg@krause.net”);
headers.add(“bcc”,”checkthis@apress.com”);
headers.add(“from”,sp2010@apress.com);
headers.add(“subject”,”Send an EMail from SPUtility”);
headers.add(“content-type”,”text/html”);
string bodyText =”This is an html formatted message.”;
SPUtility.SendEmail(web, headers, bodyText);
Note that StringDictionary is defined in the System.Collections.Specialized namespace.
Method 3 : - Sending E-Mail from a WCF Service
Sending an e-mail from a service when SPContext is not available could fail. As a workaround, you have to prevent the mail function from reading the current context by using HttpContext.Current = null. If it can’t, it will retrieve the right context and it will then work. The next example shows this.
Sending E-mail Using SendMail from a WCF Service
try
{
using (SPSite site = new SPSite(“http://sharepointserve”))
{
SPWeb thisWeb = site.RootWeb;
{
string to = “someone@apress.com”;
string subject = “Book Message”;
string body = “A message from SharePoint”;
HttpContext curCtx = HttpContext.Current;
HttpContext.Current = null;
bool success = SPUtility.SendEmail(thisWeb, true, true, to, subject, body);
HttpContext.Current = curCtx;
}
}
}
catch (Exception ex)
{// Exception handling skipped for clarity}
In the above code the current context is set to null to force the context to be retrieved again. Saving the current context ensures that the service works properly after the method has been executed.

Tuesday, January 8, 2013

IIS Manager Error: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)

When i was tried to open my 80 Port  i got 404 error and checked on the IIS the web site was stopped and when I try to start it the error message "The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)" appears, and i solved the issues with a simple method.
There is another application(SKYPE) that is using port 80

1. Open the Skype window, then click on Tools menu and select Options.
2. Click on Advanced tab, and go to Connection sub-tab.
3. Uncheck the check box for Use port 80 and 443 as an alternatives for incoming connections option. 
4. Click on Save button 
5. Restart Skype to make the change effective. 

Enjoy :)