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:
This can occur when an installed feature is renamed. Either reverse the rename or uninstall the feature.
PowerShell's Uninstall-SPFeature <Guid> -force will not work. You should use stsadm -o uninstallfeature -id <Guid> -force instead.
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 ...
SharePoint solution packages consist of a .WSP file that you can create using Visual Studio (or manually if you so wish).
Before deploying to a production environment, I recommend you take a look through Deploy solution packages (SharePoint Server 2010).
Basically you need to add your solution to the solution database of a SharePoint Server farm using the ...
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.
I suggest you should deal with the problem after going through httphandler development and its deployment in IIS 7 and ASP.NET 3.5. Here is a good link : http://msdn.microsoft.com/en-us/library/bb398986(v=VS.90).aspx
(See various walk-through and consider asynchronous handlers as you deal in asynchronous way)
If you think you know it all, Please ensure :
To deploy a .wsp farm solution you need to be a local administrator on the server:
Adding a solution package
Before you can deploy a solution package, you must add it to the solution database of a SharePoint Server farm.
Important: You must be a member of the Administrators group on any computer on which you run Windows PowerShell.
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 ...
Our way around this is to use ILMerge.
The common assembly is merged into the other assemblies post-build, avoiding problems with different assembly versions (less of a problem in your case) and inadvertent retraction.
When you deploy a file to a gallery using the File CAML element, SharePoint does not automatically remove the file when you deactivate the feature (or retract the solution). Presumably this is to prevent parts of the site that rely on the presence of that file from breaking if you were to accidentally deactivate the feature.
To get around it, you should ...
Yes, it is possible to keep the same name in the new environment. You need only to redirect your DNS entry to the new servers. As for the old servers, you can rename the url to -OLD or set up host file entries on the servers and then you can get to them from within the servers only for reference or to retrieve information. My recommendation is to rename the ...
I used the following techniques a few times (with SP2007 and SP2010) :
Create a SharePoint project "YourLibrary", that contains all the shared code.
Package the code in a separate WSP
The most important part : create a Farm Feature, empty, auto-activated at the install
The 3rd point is important, because your projects that depends on this ...
Sandbox Solutions can be deployed by Site Collection Administrators. These can be considered 'users'.
Farm Solutions require to use the SharePoint Farm Account on a web front end to deploy. These should never be done by 'users' and only by system administrators.