Tag Info

Hot answers tagged

3

I would suggest you move your code into a Timer Job that executes at regular intervals, in the background. Running stuff when the application starts will only slow down it further (we all know that SharePoint is a bit tired in the morning). Timer Jobs can be set to execute at specific intervals or times and can be run on specific or all servers. Check out ...


3

Do you want the results in memory? or do you want to store them somewhere afterwards? wouldnt mess with the Global handler approach as this is pretty complex to get right & is really hooking into the stack at the wrong level. You want to hook in at the SharePoint Service App level by the sounds of it. This way you dont have to muck about with ...


2

A jr. administrator had used stsadm -o setsiteuseraccountdirectorypath -url https://portal.domain.com -path <LDAP Path> to change the value of the SiteUserAccountDirectoryPath property. He did this in an effort to restrict the people picker from displaying people not currently in the site collection from being displayed. When he made his changes it ...


2

A similar post already answered this: SharePoint equivalent of Application Start in Global.asax SharePoint implements its own compiled assembly to handle events in the Global.asax and the class is sealed so you can't inherit it and override. You need to write a custom HTTP module to tap into the ASP.NET pipeline.


1

where are you putting the code? i presume the createchildcontrols? also the values before postback need to be stored into session state and the values to put back into session state after postback is onPreRender: more info can be found here: How to save variables per user session per page have you tried encapsulating the code with: if (!Page.IsPostBack) ...


1

Instead of passing those arguments using the "args" object, you can append them in the QueryString in the Url of the page. Something like this: var options = SP.UI.$create_DialogOptions(); options.title = "My Dialog Title"; options.url = "/_layouts/DialogPage.aspx?Arg1=value&Arg2=value&Arg3=value"; SP.UI.ModalDialog.showModalDialog(options); And ...


1

This will depend on what you want to achieve. One way would be to hook up a custom module. Example http://www.sharepoint4arabs.com/AymanElHattab/Lists/Posts/Post.aspx?List=0b2c413e%2De6fb%2D4c60%2Da12f%2D9ae9bdbd48c8&ID=62



Only top voted, non community-wiki answers of a minimum length are eligible