Tag Info

Hot answers tagged

17

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


15

With Visual Studio 2010 it is easy to build a WSP. Additional tools are not required, especially for a project as you described. The basic steps are: Create a new SharePoint 2010 project using the Empty SharePoint Project template. For each of your items that you want to add, right click on your project in Solution Explorer and choose Add New Item. Choose ...


9

Not sure why it wasn't working through the Central Admin but I ended up doing it through the Management Console using the following commands: Uninstall-SPSolution -Identity mySolution.wsp -allwebapplications Remove-SPSolution -identity mySolution.wsp -force Hope this helps someone.


9

If the WSP has any assemblies in it - no. The assemblies developed for SharePoint 2010 will be referencing the SharePoint 2010 core assemblies, and will fail when trying to load them in SharePoint 2007. If the WSP only has XML in it, and no server side code in assemblies, it should deploy fine, given it has no Feature code that's new in 2010 (such as ...


9

Ok, for the wsp part follow laurie, or if your lazy add wspbuilder to visual studios to build the wsp for you. now to add the masterpage and css: create an empty project add module as you can see above, remove the sample.txt, right click styles and add your masterpage and add another module for css :) for the css, click on the elements.xml and add ...


8

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.


8

I have to disagree with James. The SPContentType in SharePoint 2010 has a new constructor that lets you specify the content type id. The addition of the Inherits attribute of the ContentType element makes the behavior of content types described in CAML inconsistent. Finally, the Feature upgrade mechanism is great if you are adding fields but it doesn't ...


7

When you have common/shared components, like the helper DLL you talk about, that get used acros multiple solutions within you ogansisation. My recommendation is to package these up as a 'framework solution' that is deployed to the servers indendently of the 'feature based solutions'. This way you 'feature solutions' are developed in the knowledge that ...


7

In the Timer Job project, open the package designer. Click Advanced (bottome of the designer) Click Add, and choose Add Assembly from Project Output. Select Project A Repeat selecting the other project. All your assemblies will be in the Timer Job solution, and is the only one you need to deploy to SharePoint.


7

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


6

As the documentation states, when you add new artifacts to a solution you need to reinstall it. Really nothing new here, except for support for solution dependencies (and this is really only half implemented, since you can delete solutions that other solutions depend upon without getting any warning) Feature upgrade is an entirely different matter. No ...


6

the article you reference at the end of your question really answers it: custom web services should be placed in _vti_bin. i usually start by adding them to _LAYOUTS but thats only to be able to define my discovery files etc (as described in the MSDN specification you mention). _vti_bin is a virtual directory mapped to the 12/ISAPI folder, so you can ...


6

By doing that you are deploying your solutions to the farm and therefor you can find it if you go to Central Administration System Settings Farm Management > Farm Solutions If you want to deploy it to sandbox solution using powershell then your solution will need to be sandbox solution compatible and you can use the following command ...


6

The Visual Studio 'Deploy' command actually invokes all the deployment steps in the current project deployment configuration. If you go and check by default it performs many seperate tasks under the coverall of 'Deploy'. That's under the SharePoint tab of the project properties window. The 'Deploy' function also does conflict resolution such as deleting the ...


6

The most highly praised, probably the most widely used, and personally my favourite SharePoint dev tool ever created is possibly your best solution to this. WSPBuilder: http://wspbuilder.codeplex.com/ You'd need to reorganise your folder structure of the WSP into what WSPbuilder expects, but this is probably your fastest way to do this. We have recreated ...


6

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


5

I think you still need to activate the feature that deploys your webpart. As far as I can see you have installed the solution and thereby installed the feature but not activated the feature that contains your webpart. So add the line enable-spfeature -identity foobarwebpartfeature -url yourwebsite in your script to ensure that the feature is activated.


5

It is by-design that retract doesn't remove actual data. There is no event handler either that you could use to remove content after solution has been retracted. :( I guess you would need to create custom functionality that will clear old content and run it after retracting solution. Would it be possible to use site collections for this, and then just ...


5

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've implemented this method in the past, so I just share my code with you: add: private void AddAuthorizedType(SPWebApplication webApplication, string assembly, string namespace_) { SPSecurity.RunWithElevatedPrivileges(delegate { var modification = new SPWebConfigModification(); modification.Path = ...


5

We've found it's much easier to just add a webconfig.something.xml file to the Config folder. So for your one entry you can create an xml file with these contents: <?xml version="1.0" encoding="utf-8" ?> <actions> <remove ...


5

As far as I know, you can only open the wsp file as a cab and modify the files from there. The downside is that all the code will be compiled into assemblies and there will be no way to extract the code from them. You could create a new Visual Studio web part project and add the assemblies from the wsp file and see if there are any open facing classes or ...


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

Also enable your feature Enable-spfeature -identity <featurename, id or object> -url http://yoursite It is also worth mentioning that something that can be quirky is permissions. To deploy (farm) solutions you need to be farm admin and local administrator. Some commands also require you to have shell admin role (add-spshelladmin). Read more on ...


4

If you are packaging your wsp manually, then you need to include your dll in your DDF file, e.g. bin\Debug\MyFile.dll MyFile.dll and you include the assembly in the solution manifest, e.g. <Assemblies> <Assembly DeploymentTarget="GlobalAssemblyCache" Location="MyFile.dll" /> </Assemblies> Here is an MSDN reference If you do not ...


4

There are some ways to do this with custom content types, possibly even building on the Discussion Boards that are out of the box in SharePoint, but if you are looking for something that might be able to be implemented quickly I would look at the SharePoint Forums from Lightning Tools. http://lightningtools.com/


4

I wouldn't go for WSPBuilder (a third party product) anymore in SharePoint 2010 as all the building is done from within Visual Studio and MSBUILD today. To create a wsp package just like Visual Studio's there are a couple of steps: Use MSBUILD with argument /p:IsPackaging=True Done I guess it was just one step... :-) Read up on Continuous Integration ...


4

Out of the box, no, you can't save it as a template (wsp) that you can then edit in Visual Studion. However, you can still get to the XOML files that create it. By going through All Files>Workflows. With a lot of work, you can take these and pull them into Visual Studio to create a re-usable workflow from VS. This is not easy, though. Paul Schaeflein has a ...



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