Skip to main content

SharePoint 2010 Replaceable Parameters, Dynamic Tokens, Dynamic Folder Path

Image
By
Replaceable Parameters :

Replace the tokens values at the run time or compile time.Information not known at design time.Replaceable parameters used in custom actions, assembly name defined at the top of the custom web part control.

 

 

Following are the list of Replaceable Parameters.
Working following files that use  Replaceable  Parameters by default.
  1. Xml 
  2. ASCX 
  3. ASPX 
  4. WebPart 
  5. DWP
Dynamic Token (Microsoft Definition)
This token references a master page from a content page by using the MasterPageFile attribute with the value of the CustomMasterUrl property. The token "~masterurl/custom.master" is replaced at run time by the value in the CustomMasterUrl property, which contains the server-relative full path to the master page, including file name.

Static Tokens (Microsoft Definition)
You can use these tokens to link to a site-relative or site collection-relative master page. For example, if your content page is located at http://siteColl/subsite1/subsite2/default.aspx and you use the token "~sitecollection/mypage.master", your content page would use the master page at http://siteColl/mypage.master. If you use the token "~site/mypage.master", the content page would use the master page located at http://siteColl/subsite1/subsite2/mypage.master. 

Folder Path virtual Path


“ SharePoint Site"

/_controltemplates : Local drive: \Program Files\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\CONTROLTEMPLATES

/_layouts : Local drive:\Program Files\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\layouts

/_vti_bin : Local drive:\Program Files\Common Files\Microsoft Shared\web server extensions\14\ISAPI

/_wpresources : Local drive:\Program Files\Common Files\Microsoft Shared\web server extensions\wpresources

“ SharePoint Central Administration v3”

/_admin : Local drive: \Program Files\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\ADMIN

/_vti_adm : Local drive:\Program Files\Common Files\Microsoft Shared\web server extensions\14\ADMISAPI

Replaceable Prameters: http://blah.winsmarts.com/2013-2-SharePoint_2013_apps_replacement_tokens.aspx

Labels:

Comments

Post a Comment

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

By
What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...
1 comment
Read more

SharePoint 2013 Search Database Part 1

By
SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...
Post a Comment
Read more

STS CryptographicException Error : Key set does not exist

By
Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis
Post a Comment
Read more