New answers tagged application-pages
Since SharePoint Content database connection string is stored in Windows Registry, the following example demonstrates how to read Data Sourcefrom a SharePoint Content Db connection string: /// <summary> /// Get SharePoint Content Db DataSource (SharePoint 2010) /// </summary> /// <returns></returns> private ...
Public connectMe = new System.Data.SqlClient.SqlConnection("Integrated Security=SSPI;Initial Catalog=TestDatabase;Data Source=(local);") This connection string's options can be dissected as: Integrated Security=SSPI; – This means we want to connect using Windows authentication Initial Catalog=TestDatabase; – This means the database we want to ...
Try changing the options.Url to: options.url = _spPageContextInfo.webServerRelativeUrl+'/_layouts/MyProject/AppPage.aspx'; Edit: Didn't notice 2010 first, updated with webServerRelativeUrl
Would this not work? Using the fact that Layouts is shared through the fram targetUrl = '/_layouts/MyProject/AppPage.aspx' + "?Location=" + window.location.href; or you could try: targetUrl = SP.Utilities.Utility.getLayoutsPageUrl('MyProject/AppPage.aspx' + "?Location=" + window.location.href)
If you mean the Getting started with your site look, then you can't unless you're building a new site collection. But all of the features (and many, many more) are still available if you hit the gear Icon in the upper right corner and select Site Settings.
You would essentially have 2 ways to my knowledge, after launching a modal window: using the SPLongOperation which in result would show the actual progress bar and a message at the start, tasks executing or the end, example http://sharepointzen.wordpress.com/2012/09/30/using-splongoperation-for-synchronous-long-running-tasks-in-sharepoint/ or client side ...
There is an out-of-the-box way how to prevent users who have the Edit Items permission to start a workflow. According to Start a workflow instance Permissions needed to start a workflow By default, users who have the Edit Items permission can start a workflow. If you specify that Manage List permissions are required to start the workflow, only list ...
you need to put the workflow to not start manually, you dont need to do custom actions for that.
Finally I added a custom action to inject my css to every file, in my css file I hide the div which I don't need. <CustomAction Id="ReferCssSiteCol" Location="ScriptLink" ScriptBlock="document.write('<link rel="stylesheet" After="Corev15.css" type="text/css" ...
Top 50 recent answers are included