16

Yes, your trouble is quite understandable! First, you should read that "controversial" discussion we had here a few days ago: SharePoint development past and "future": how to keep calm?. This will give you a history/backgroung about the different dev approaches for SharePoint. And here's another (more technical) overlook: Farm solutions (aka ...


9

I read that sandbox solution is not preferred in SharePoint 2013 and we should use the app model. So is creating artifacts an available approach to do inside SharePoint apps? Yes there are multiple available approaches. The one I use the most is (for provider hosted add-ins) to use a remote event receiver on AppInstalledevent. In the event receiver you can ...


6

DON'T There is no way this is going to turn out well. Changing the name of the WSP isn't going to change anything. You'll still have the same: Solution Id Feature Folders and Ids Dlls (including the codebehind for your application pages) SharePoint Root files (including your application pages) So in order for the new solution not to overwrite the old you ...


6

You could use the "PostRender" event to execute your javascript method after the form is completely loaded, something like: (function () { // Initialize the variable that stores the objects. var overrideCtx = {}; overrideCtx.Templates = {}; // Assign a function to handle the // PostRender events overrideCtx.OnPostRender = ...


6

Add the Microsoft.Office.Server.Search.Query reference to your solution Then in your code behind, use this reference as the following using Microsoft.SharePoint; using Microsoft.Office.Server.Search.Query;


6

Can you check if the user's are still enabled in AD? This error can be occurred as if the user is not enabled in AD, though it will still show as an SP User. Please let me know what happens.


5

The Get-SPFeature command will list the features with flags to filter them down to specific areas. Reference: http://technet.microsoft.com/en-us/library/ff607945.aspx There is also the Get-SPSolution command to show all the solutions on the farm and whether they are deployed and online. Reference: http://technet.microsoft.com/en-us/library/ff607754.aspx ...


5

Have you tried Update-SPSolution?


5

If you only want to hide the list from "All Site Content", the SPList class has a "Hidden" attribute. If you set this attribute to true, nobody will see the list via "All Site Content", but you can still access the list with the direct link. You could set the "Hidden" attribute with Powershell or a console application, for example (or do it at feature ...


5

You would need to Create a new Web Application in farm 2 Export solutions* from farm 1 Install solutions in farm 2 Backup content databases belonging to the web application in farm 1 Restore all content databases in farm 2 Enable all features on farm 2 Web App | Site | Web that are enabled in farm 1 web app Test From an abstract level, this works. To make ...


5

Farm solutions are fully supported, although the Visual Studio tooling isn't quite yet available.


4

The Update-SPSolution call is asynchronous. More precisely, this command only create a timer job that will be run eventually. You can use this function to wait for the end of the execution of the job : function Wait-SPSolutionDeploymentJobToFinish { param ( [Parameter(Mandatory=$true)] [string]$SolutionFileName ) process { ...


4

Just provide the path of the folder where WSP is located and the function will add all the WSPs in Solution store. Remove-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue function WaitForInsallation([string] $Name) { Write-Host -NoNewline "Waiting for ...


4

Just right-click PowerShell and click "Run as Administrator". If that does not work you then just run Get-SPShellAdmin and see if your account you are using is listed as a ShellAdmin. Initially, only the "Farm Admin" service account is a ShellAdmin (not the "Setup Admin" service account). If your account is not listed, then use the Add-SPhellAdmin to add ...


4

Retract Solution fires off the Uninstall process of the WSP package from the farm. It's equivalent to the Uninstall-SPSolution PowerShell command and the opposite of the Install-SPSolution command. Remove Solution is the equivalent of the Remove-SPSolution PowerShell command and is the opposite of the Add-SPSolution command. It can be seen as deleting the ...


4

Are there only 2 kinds of SharePoint Solutions? yes, but since SP 2013 we could count the APPs as a separate solution type as well Does the SharePoint Foundation Sandboxed Code Service" (SPUserCodeV4) have to be active ... yes On what server(s) should...Code Service" (SPUserCodeV4) be active? I would suggest on the front end "Save Site as ...


4

try it as below: public override void ItemAdded(SPItemEventProperties properties) { base.ItemAdded(properties); SPUserToken systemAccountUserToken = SPContext.Current.Site.SystemAccount.UserToken; using (SPSite elevatedSite =new SPSite(properties.SiteId,systemAccountUserToken)) { SPWeb newSite = elevatedSite.AllWebs.Add(...


4

You can't do this easily. Farm solutions and sandbox solutions with custom code aren't supported in SharePoint Online. Generally you must rewrite your application as SharePoint Add-in (SharePoint-hosted or Provider-hosted). You should read this guide about transformation process.


4

As far as I have information, I doubt anything will change with respect to farm solutions. They exist since the first version of SharePoint and are the most powerful way to develop solutions in SharePoint. Among other things: Better performance Code more "ordered" Compiled code Simpler to use Elevated privileges More classes It does not seem that this ...


3

how long is a pice of string? ;) only joking, its a vauge question so im going to try to answer without being so vauge! Your talking about user/group policy: •User-only policy—This user-only policy is the authorization policy that was always applied in SharePoint 2010. When the user-only policy is used, the authorization checks take into account ...


3

If you are simply creating web applications, site collections, etc., I would use a PowerShell script. I would only create a custom solution if you are adding custom content, such as web parts, master pages, etc.


3

You can use feature stapling to achieve this. You just deploy a simple element file in a feature and activate it at the web application level. <?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <FeatureSiteTemplateAssociation Id="the guid of the feature to staple to new sites" TemplateName="...


3

Use powershell commands: Uninstall-SPSolution Remove-SPSolution Uninstall-SPSolution uses some sort of timer job to actually, so it can take 15-45 seconds for the Uninstall to finish. This guy has a reasonable complicated script for automating this: http://jmkristiansen.wordpress.com/2012/02/17/automatically-retract-remove-add-and-deploy-sharepoint-...


3

Steps to Upgrade from SP 2010 to SP 2013: Make the site in SP 2010 readonly. Using SQL Management Studio, perform the backup of Content database and service database in SP 2010. Restore the databases in SP 2013 SQL server. Attach the content database to a site collection in SP 2013. Similarly, attach the service databse to the corresponding service in SP ...


3

Since you need to use the Client Object Model for apps, you will have to rewrite large parts (if not all) of your back-end code.


3

Go to Package.package in your project and double-click it. Click the "Advanced" tab Click "Add" and "Add Existing Assembly.." Click the "triple-dots (...)" Navigate to your project folder and then to the .dll in the bin-folder and click "Open" That should be it


3

Due to customization, most of stuff is manually and required extra steps. Build New Farm( make Sure it should be same version level) Create and Configure the Service Applications Create a New Web application and configure the Authentication. make sure same authentication Now you have the Apply the customization( i.e any web .config change, hive folder ...


3

The SharePoint terminology is vert confusing. Officially, you have the "site collections", and each site collection contains "site"s (the root site and all its sub-sites are sites). There's no "web". That's for the admin/user point of view. However, from the developer point of view, things are a little different: a site collection is an SPSite while a ...


3

Please try this once. private static TermSet RetrunTermSetIfExists(ClientContext clientContext, TermGroup termGroup, string termSetName) { clientContext.Load(termGroup.TermSets); clientContext.ExecuteQuery(); TermSet termset = termGroup.TermSets.FirstOrDefault(x => x.Name.ToLower() == termSetName.ToLower()); if (...


3

There are few caveats you need to check when working with EnsureUser EnsureUser will work only if the user is available in that particular Site collection. Check if user is available in any site group If you have that user in your site collection, probably you need to get the encoded claim value to be passed to that method. SPClaimProviderManager cpm = ...


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