Tag Info

Hot answers tagged

23

For Features SharePoint Features can be scoped to the Farm, Web Application, Site Collection, and Web Site level depending on the purpose of the feature. The Feature scope is determined by the setting of the Scope attribute in the Feature element defined in the feature.xml file. A sample Feature element tag is given below: <Feature ...


12

Welcome to SharePoint Stack Exchange! In your Visual Studio 2012 SP Solution: Enable Always Force Install to True in for your feature. See example below: By default, it is set to False. You can configure that to be set to True.


8

There is a stsadm -o canceldeployment -id <id> To get the ID you have to use stsadm -o enumdeployments Just be sure that your Timer Job is running.


6

I strongly recommend that each dev has it's own installation. It could be a Virtual machine (single machine with AD, SQL and SharePoint). It looks like your company is not shy on resources so it might be possible for you. 2 people (or more!) on the same box will lead to frequent delays as you deploy/recycle, hook the debugger, or if you want to test a ...


6

Elements by Scope helps you understand what elements are allowed for each scope. That also means that solutions can be developed and SharePoint architecture allows them to be deployed at any of the scope documented. Most solutions use FEATURES that are targeted at web or site collection level and when an element is allowed at both web and site level, it ...


5

I would use a SPWebConfigModification: http://msdn.microsoft.com/en-us/library/bb861909.aspx Something similar to this: SPWebConfigModification handlerMod = new SPWebConfigModification(); handlerMod.Path = "configuration/system.webServer/handlers"; handlerMod.Name = "add[@name='SomeHandler'][@type='SomeHandler']"; handlerMod.Type = ...


5

It seems as if Install-SPSolution and Uninstall-SPSolution has been written by two different developers (or at least at different times) Both commands have the potential of accepting either no, a single or all WebApplications how they deal with these option are quiet different. Install-SPSolution This is the well coded one, where the decision is base on: ...


5

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 ...


4

Have you tried Update-SPSolution?


4

The chosen language cannot be the reason why your job doesn't work. Regardless of language it compiles in the same MSIL. Did you check ULS for any errors related to your job? Did you check ULS settings - maybe it configured not to log some messages? Did you check job status in Central Administration?


4

Have you had a chance to look over the following link? http://blogs.msdn.com/b/vesku/archive/2010/10/14/sharepoint-2010-and-web-templates.aspx#sitetemplate "One of the consideration with the site templates is also the fact that unless you import them to Visual Studio and modify its settings, they are only available on site collection level (site collection ...


4

While it is possible to upgrade features while upgrading solution, it is a very bad practice, so only consider this as a warning of how not to do it: Using -force parameter on Install-SPSolution will force solution to be installed and underlying features to be enabled even if they were already enabled. Forcing a feature to be enabled will also trigger ...


4

Before you can deploy a SharePoint hosted app to your SharePoint Preview development environment you have to configure an isolated app domain. like this : http://sharepointchick.com/archive/2012/07/29/setting-up-your-app-domain-for-sharepoint-2013.aspx http://msdn.microsoft.com/en-us/library/fp179923%28v=office.15%29 Hops it helps!!


4

Here is the PowerShell code to create a webpart page: Add-PsSnapin Microsoft.SharePoint.PowerShell $pageTitle = "Page Name" $layoutTemplate = 4 # Template code $web = Get-SPWeb http://server/site $list = $web.GetList("http://server/site/LibraryName/") $xml = "<?xml version=""1.0"" encoding=""UTF-8""?><Method ID=""0,NewWebPage""><SetList ...


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: ...


3

There are two key points to the Timer Job. The class which represents the timer job, and then the code that actually registers the job. This is typically done within a feature receiver on the feature that contains the timer job. Here is some code on MSDN: http://msdn.microsoft.com/en-us/library/cc406686.aspx#WSSCustomTimerJobs_DeployingCustomTimerJobs ...


3

Also it seems that to deploy a solution, I can simply upload a wsp to the solution gallery within a site collection and activate the feature? Yes this is right. So if I develop say a basic webpart on a dev laptop with installation of SP, VS, etc, and I reference my local sharepoint implementation in the project do I need to somehow change ...


3

None-sandboxed solutions must be deployed by Farm Administrators. You will need to package the solution and send it to the relevant people who can deploy it via STSADM or PowerShell as taste dictates.


3

I would say that developers normally have access to at least test. I am a SharePoint Consultant-Developer and at most of my clients we have some access to a test server. Of course it matters the importance of test and the size of the org. Our big clients it is hard to get on test, or we have to make new test servers for each project. At smaller clients ...


3

Do developers normally have access? It depends on the company and it depends on the project. I've worked on projects where I deploy all the way up to production, and I've worked on projects where my involvement ends when an admin deploys to test. Do developers want access? Naturally. Do admins want developers to have access? Not typically. Is your ...


3

That's typical. Admins are normally responsible for keeping the servers and applications running up and available. If they aren't the ones deploying the solutions, you cut them out of the loop and they then have difficulty supporting their servers and applications. They are the ones getting called initially when applications and servers aren't beahving ...


3

You need to populate the gallery if web part is not appearing in the web part gallery. For that go to site setting(I use 2013) site gallery, click on web parts link There clicking on new documents, you will get all the web parts installed. Check the box along the web part name and click on populate button on the top. That should work, I hope.


3

SharePoint's solution deployment is a bit of a black box. I would try two things: 1) Use -Force on the Install-SPSolution cmdlet to instruct SharePoint to override files, etc., and hopefully result in "Deployed". 2) If #1 doesn't work, I would retract and remove the solution. Then restart the SPAdminV4 and SPTimerV4 Windows Services. Then re-add the ...


3

within your solution click on feature.feature and goto its properties, you should now see somthing on the lines of Always Force Install just set that to true and you dont need to do the force attribute anymore! looks like a feature wasnt retracted properly and has become a phantom! ybs has a similar issue here! Visual studio Both site collections ...


3

I can't find a resource on this atm, but the main differences are: if your solutions contains dll's it will ask to deploy them to the gac. I've personally not deployed them to a specific web app's bin folder yet. if your solution contains webparts or other resources that require modifying the web app's web.config file, it will ask you what web application ...


3

No, the solution dictates if it's global or per web application. WebApp Scope If the solution contains resources that's web application specific like: - Dll deployed to bin - Dll with SafeControls - files to the other hostdir folders then the solution must be installed to specific web application(s) by either specifying web applications like: ...


2

Process of changing feature scope from old one (e.g. Web) to a different one (e.g. Site) involves several steps Deactivate feature with old scope wherever it's been used throughout the whole farm Uninstall feature with old scope Install feature with new scope Activate feature with new scope Without aforementioned procedure, installing feature with ...


2

There is a more fail-safe approach than what @lwbecker2 suggests Get-SPSolution | ? { $_.JobExists } | % { Write-Host "Deployment job is currently running" } This has the benefit of not having a race condition. If you only look for the timer job, it may be that a deployment has already been initiated, but a timer job was not yet created when you check for ...


2

You can only do this via stsadm -o enumdeployments because enumdeployments will list all the active deployments. Moreover, enumdeployments doesn't have PowerShell equivalent (at least that I can find so far). I got 98% of this information from Technet and a little from SharePoint forums


2

Upgrading won't recreate your content types, since they're already created. You need to handle the version of the deployed content types in your code, and modify the content type accordingly based on what version is currently deployed. Jeremy Thake has a great blog post on using versioning with feature development. Additionally, STSADM is deprecated--you ...



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