If you double-click on the feature (NameofFeature.feature), in your solution. You'll see a properties window come up - as a window that details the title, description, scope, items in solutions, and items in the feature. In the properties window, you'll see an option titled 'Always Force Install'. By default, it is set to False. You can configure that to be ...
Short explanation: As far as usage is concerned, in many common cases there are almost no actual differences - anything you can do with a webpart you could do with a visual web part. For many points of view the visual web part is only a tool that enables the developer to work with a user control instead of creating all controls in codebehind.
Visual web ...
You can do it via the XML editor as well!
Go to your Features in your project.
Open the feature.template.xml file
add AlwaysForceInstall="TRUE" to the below tag
<Feature xmlns="http://schemas.microsoft.com/sharepoint/" AlwaysForceInstall="TRUE">
Now try to deploy the code.
When you deploy a solution with a WebPart it deploys three things:
The dll with the web part
A SafeControl entry to be inserted into web.config
A .webpart (or .dwp) file with configuration settings to be inserted into the Web Part Gallery (this part actually happend at feature activation not at solution deploy, but..)
When you're adding a web part to a ...
I discovered that the problem comes from the program Microsoft Visual Studio 2010 Shell (Isolated) - ENU that gets installed with SQL Server 2012. After uninstalling that program and then running the SharePoint 2013 installer I am able to see the splash screen.
Warning - This will prevent Sql Server Management Studio 2012 from working on that machine.
SharePoint only shows Incoming Email settings link for OOTB lists of type Announcements, Event, Document Library, Picture Library, XML Form, Discussion Board, Posts.
So, if you create a custom list, you need to create a custom email event handler and attach to your list and then Incoming Email settings link will be available.
More info: http://social....
You can create a Visual Web Part for SharePoint 2013 Online.
Your web part will be contained in a Sandbox Solution which you will develop locally. Once development is complete you will upload the Solution Package created by Visual Studio to SharePoint Online. Once this is done your web part will be available for use.
As mentioned, development will be done ...
In order to develop SharePoint Solutions (as opposed to Add-ins/Apps) you have to run SharePoint on the machine running Visual Studio and the Site you you debug on must be one hosted by that SharePoint Farm.
Before you continue down this road make sure you really want to create a SharePoint Solution.
First, The above code is Server-side object model, not Client Side object model so you should use Microsoft.SharePoint not Microsoft.SharePoint.Client namespace
Second, the CamlQuery is used with Client Side object model at Microsoft.SharePoint.Client namespace.
Third, in Server-side object model you should use SPQuery with Microsoft.SharePoint
Actually, retraction of a WSP solution is part of the standard functionality of Visual Studio 2010 and it happens after you stop the debugger. It can be deactivated by un-checking the "Auto-retract after Debugging" checkbox available in the bottom of the SharePoint tab page, of the Project Properties (right-click your project and choose properties).
Remove feature receiver
Close Visual Studio
Delete SharePoint project's obj folder in Windows Explorer
Delete SharePoint project's bin folder in Windows Explorer
Open Visual Studio and re-add feature receiver
You cannot add an event receiver through the "Add new project" dialog. What you do is create an empty sharepoint project first. Then just right click on said sharepoint project, click add new item, go to Office/SharePoint and choose Event Receiver. See my screenshot.
If you add list using ListInstance then you can add items using ListInstance file:
<?xml version="1.0" encoding="utf-8"?>
<ListInstance Title="LinkList" OnQuickLaunch="TRUE" TemplateType="170" FeatureId="Your feature id" Url="Lists/LinkList" Description="Your description">
Answering your 4 questions:
Remote Event Receiver (RER) -
A provider hosted app is must, which means you need additional infra. Apparently, as pointed out by Mihail-Florin Popa, it is no longer true.
Works using web services, you expose web services on your provider hosted app, that are called when an event is fired.
Only Client Object Model ...
Is your production a multi server farm? I think you are facing the following issue:
It turns out that VS 2010 internally implements a call to the method
If the assembly contains any event or feature receivers then the deployment target should be Global Assembly Cache. And if you deploy the solution using a command line then you should start a new instance of that before activating the feature (this is most important when you get to upgrading) as an old version of the dll can't be unloaded.
Actually Visual Studio 2010 Professional, Premium and Ultimate all allow for SharePoint development as the "Office and SharePoint development tools" are available for all (see here http://download.microsoft.com/download/4/6/E/46E8BB6C-108F-467C-9292-50EE94F117B5/download/Visual-Studio-2010-Feature-Comparison-Matrix.pdf)
Same stands still with Visual Studio ...
Package a WSP
Right click your project in the right column. Then click "Publish".
A dialog will open, where you will get to choose where to place the resulting .wsp file. After clicking "Publish" your project will be build and then packaged in the selected location.
Make sure to have the Solution configuration set to Release when building for production.
To fully remove it you have to maunally delete the .webpart or .dwp file from the wp gallery manually.
Go to [site]/_catalogs/wp/Forms/AllItems.aspx and you will see all of the webparts.
You might also like to check this post out
By the way, I normally deploy webparts as solution files and if i want to remove them, I retract them from Central Admin > ...
To add to Hugh's answer, almost anything you can do in VS 2010 for SP10 works in SP13 (event receivers, web parts, etc.), but nothing new, or not much of the new features work in VS2010 because much of them are new templates and data techniques such as the app model, remote event receivers, etc.
The App model requires the ability to do remote development ...
TLDR: You have to re-create the content types using the correct parent content type!
You cannot change the parent content type of a content type:
The Parent property is read-only.
The content type ID is prefixed with the parent content type's ID. See explanation below copied from here. This is for SP 2010 but it works the same for SP 2013 and later ...
If the assembly you reference is really external, you have to include the external DLL in your SharePoint solution package:
In VS open Package > Advanced > Additional Assemblies > Add
Here you must add the assembly and specify the safe controls that will be added to web.config to allow safe parser to execute the assembly
In general, you should avoid directly connecting to PRODUCTION for any sort of development or debugging. Consider bringing the list to your development environment. You can use import/export or consider saving list as template and install the template in Dev environment.
How should you develop, debug and deploy sharepoint solutions?
The serious ...
How to customize SharePoint Blogs using client-side rendering (CSR)
Since the client side rendering (CSR) is the default rendering mode in SharePoint 2013, below is demonstrated how to override Body field in such a way that the link for the post will be displayed via CSR.
And the resulting page could look like this
Example: how to override ...