Hot answers tagged sharepoint-foundation
The rest interface is not available to anon users by default. It can be enabled, but MS recommends against it. The preferred solution is to enable the search rest api for anonymous access, and retrieve all data that you need via that. A good article that explains the above in detail. Waldek's post that is a good explanation of how to enable the search api ...
Yes, You can One Sql Server with two Different SharePoint Farm. Currently i have two Dev farm(2013) sharing the Same Database server. As long as you have unique Names for yoru Config & content DBs. Having Enough hardware to support both farm I am positive you will not do this in production, big risk. IF DB server goes down...both farm will go down.
It should be noted that there are no synchronous calls available in the JS Object Model, and this is on purpose. The proposal to use promises is just a different async pattern, but that's okay… It is possible to artificially 'force' the scripts to work in a synchronous manner using various techniques, but there's really no reason to. Async patterns (direct ...
You can't, this is an all or nothing setting. It is either content approval for everyone, or no one.
By default, a lookup field contains just one value. In this case, the field value is an object of type String, and the string has the following format: Id;#Value Use int value = new SPFieldLookupValue(item["Project_x002f_Task_x0020_Status_"] as String).LookupValue to read the lookup value and int id = new ...
At the very least, I would separate the server in two different instances on the same SQL Server, but I don't see it being completely impossible. Make sure that you create your config database as something else, and make sure all the databases are different than what is on the first farm. Use GUIDs wisely. I don't recommend this approach though.
All services Applications are farm level but you can manage them which Web App want to use it or not. When you create a visio graphics Services, it will added into Default Application Proxy Group. By default all Web Apps will consume this service. Now you have to change the Service Application Associations for Default Group and remove this Services ...
Maybe use a blog instead and they can publish the content to the blog directly from Word and retain the look they have with no customizations necessary.
should be the same as: server side: SPGroupCollection groups = SPContext.Current.Web.SiteGroups; and client side: clientContext = new SP.ClientContext(); var groupCollection = clientContext.get_web().get_siteGroups(); its grabbing a collection of the current web groups.
Only top voted, non community-wiki answers of a minimum length are eligible