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:
I had the same problem today. I compared the project files with an older version. In my case the Package directory (with the files Package.package and Package.Template.xml) was missing.
After copying this directory back from the older version of the project and modifying the csproj file to include the references to the package directory, the error solved ...
We can either manually do it through central admin or by using powershell commands.
I would prefer doing this through powershell
To uninstall and remove Farm solutions use the Uninstall-SPSolution and Remove-SPSolution cmdlets (Use -WebApplication attribute if the solution has webapplication-scoped resources):
Uninstall-SPSolution –Identity ...
You need to move the list Url to your module definition:
<Module Name="Style Library" Url="Style Library" RootWebOnly="true">
for GhostableInLibrary to work properly. You should of course then remove it from the File Url, since it is now defined on module level.
If you have no Url in the Module tag you can only use type="Ghostable" on your File ...
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 ...
Visual Studio deploys to the server it's installed on, and as a best practice it shouldn't be installed on any production server. During the deployment process, the applicable bits for the solution will automatically be "deployed" to any server in the environment with the Foundation Web Application role. For deployment to production, the correct process ...
At the beginning of your FeatureActivated method, put this line of code :
Then, try to activate the feature. This will popup an "exception" window that let you to attach the debugger of your choice.
After attaching, your code will be pause at this line, and you will be able to walk into your code to find the issue.
Follow the below steps to move workflow into production environment site,
In the Development environment open the SharePoint Designer and export the workflow you want using “Export to Visio”.
Rename the vwi files by adding ".zip" extension, now open the zip file and remove the "workflow.xoml.wfconfig.xml" because it contains the details about the ...
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 the ...
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 ...
Last year, Microsoft launched a dedicated site for SharePoint user adoption which can be a good place for you to start with.
With addition to the above, I believe your prime concern should be planning a collaboration roadmap on SharePoint.
This will essentially include high level areas like
Current use of Office 2010 products within your organization and ...
When you install the SharePoint 2013 it installs the service by default and assigns the Distributed Cache service 10 percent of the total physical memory on the server (see more details)
It might be you'r having less memory on your SP Installation. So you might need to update the distributed Cache Service to specify the amount of RAM or increase the RAM for ...
You need CAS policies when you are not allowed to deploy to the GAC and use other system assemblies.
Imagine you have a webpart that reads a log file from disk - you need System.IO from this and thats not allowed in wss_medium (your SharePoint trust level) - in order to say this webpart is allowed to load System.IO you need a CAS policy.
If you deploy a ...
The workaround is as follows:
Open up your SharePoint 2012 solution in Visual Studio 2012/2013
In the Solution Explorer (use View -> Solution Explorer if you don't see it) expand your solution and browse to the Package within your project
Double click on the Package.package entry to open up the package editor
Click on the Advanced Tab
The Additional ...
Please see SharePoint Framework development with SharePoint 2016 Feature Pack 2
In particular, see the section on deployment.
Here are the steps I used to deploy a SharePoint Framework web part named Hello ...
You can install CKSDev extension using VS.NET extension Manager, if you have not already done so. It provides a project configuration called Upgrade Solution. You can switch to it by going to project properties as shown below:
By going to Project’s property pages (SharePoint tab), you can also inspect what actions it takes.
SharePoint is complex but the average user never even has to know what a web part is, so focus on the biggest bang for your buck. If 95% of the user base is just looking for a place to create lists or store documents, you can explain that in under 10 minutes. There are countless videos on the web that show this and there are even third party solutions that ...
There is a fine line of difference between IIS Reset and Web Application Pool recycle when it comes to SharePoint Deployments.
IIS Reset does 2 important things concerning SharePoint -
It recycles all your application pools at one go and clears the memory objects.
It reloads all dlls from the GAC(global assembly cache) in the farm servers.
I suggest you to try the GACUtil tool to try to deploy your assembly, just to test if it is deployable to the GAC at all. If the deployment still fails, this tool might provide you additional information about the reason of the error, that you can use to resolve the issue itself.
Note the Model URL and the File path of the File. Those should point to the same place, for example
<Module Name="Pages" Url="Pages">
<File Path="Pages\myPage.aspx" Url="myPage.aspx" Type="GhostableInLibrary" />
Oh, the content-type minefield, how I love thee...
When a list is provisioned it makes a copy of the schemas of each
content type. These copies are no longer dynamically connected to
the source content type. As a result, when the underlying content
type changes, all lists currently provisioned do not change.
If you delete a content type yet there ...
If you wanted to do it the "right" way then you should have used Feature Upgrading.
It's unfortunately not simple but gives you a lot of control of what happens when you deploy a new version of a feature.
In your case it would have involved:
Add the elements.xml files for the new web parts inside <ApplyElementManifests> inside <UpgradeActions> ...