Tag Info

Hot answers tagged

2

Go to the visual studio feature file and check whether you have all the webparts you needed in the feature. Else add them by selecting and send from left to right.


2

Make sure that your feature (in the VS solution) has all the web parts in it.


1

In a sandboxed solution cannot deploy files within the SharePoint root directory or any other location on the file system of the web server. That means you cannot deploy branding files to familiar locations that are commonly used in farm solutions, such as the IMAGES directory or the LAYOUTS directory. You must instead provision branding files, such as ...


1

In Sharepoint online you can not deploy files to the _layouts folder as there is no _layouts folder there. For Sandbox solutions, the Style Library is the correct location. If you are going to keep them in the Style Library can try referencing the scripts using the ~sitecollection replacement token (generally Style Library is only provisioned at the root ...


1

Custom developed web parts get the safe control entry automatically added, when it is created in Visual Studio 2010 and deployed . Only Refactoring the name or namespace of the web part class will break that safe control entry. OR This is common error if you eg. changed WebPart name after creation and/or changed its namespace. If you are working on ...


1

You should structure your features in a way that makes sense to your project. The key aspect of features is that they can be turned on and off on a site. The simplest thing to do is to put all your stuff in one feature, but that may or may not be the best solution in your case. Whether a feature is automatically activated on deployment depends on a few ...


1

There is nothing call Install Feature. When you deploy a new solution this is what happens. It first add the solution to farm. Then deploy the solution. If you have set the features to activate on the deployment in the Feature settings, it activates. You do not need to have one feature per webpart. It depends on the requirement. You can even handle with ...


1

I am not sure about the script why it is throwing the error, I would rather recommend you to post his Blog may be he will give you answer why it is failing. Did you check these commands from Gary. http://www.falchionconsulting.com/PowerShellViewer/Default.aspx I would also recommend you to use the 3rd party tools which have the atleaset 14 days trail. If ...


1

My advice is do not use xml list templates. It will give you many headaches when you are upgrading the solutions, creating lookups and etc... I would suggest create a feature receiver and create the list in the feature activated event. With the C# code you get much flexibility and opportunities to change the things around without affecting the existing ...



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