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 ...
a- Add reference to "Microsoft.SharePoint.Taxonomy" assembly
b- You need to register following Assembly in your Web Part
<%@ Register TagPrefix="Taxonomy" Namespace="Microsoft.SharePoint.Taxonomy" Assembly="Microsoft.SharePoint.Taxonomy, Version=220.127.116.11, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
c- You can use the control as following
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.
I think if you have no limitation on using the server object model, that would be the best option.
In my opinion, these are the advantages:
Code more "ordered"
Simpler to use
Of course it is an opinion and depends a lot on each case. But in general terms, if I have no limitations, I would ...
Here is a way to do it in sharepoint 2013 in visual studio 2012
1)Create a empty sharepoint 13 solution Farm solution .
2) Add a sharepoin 13 project into it .
3)Add a mapped foder "Resources" to the project .
4)Now you gonna add three resources one for english "testMutliLing.en-US.resx" and one for german
"testMutliLing.de-DE.resx" and one default ...
Do you know how to build a basic web part? If not I suggest you learn this first. Here's a sample tutorial: http://msdn.microsoft.com/en-GB/library/ms415817(v=office.14).aspx
Next you want to learn how to develop against web services. Helpfully, Yahoo have a tutorial on how to deal with responses to web services as XML within C# applications: http://...
I think the problem is src attribute of tag. Try <script src="/StyleLibrary/js/jquery-1.9.1.min.js" /> and take a look at this article
Edit If you decide to store js in _layouts folder, use <SharePoint:ScriptLink runat="server" ID="ScriptLinkJQuery" name="/Js/jquery-1.9.1.min.js" Localizable="false" />
If you don't want other people to be able to Reverse Engineer the source code to DLLs you're giving them, then you should obfuscate the DLL. See .Net Obfuscation for some suggestions.
But before going in that direction I have a couple of comments:
The only people who can get the DLL is the people with access to WSP (or the farm where it's installed). Not ...
When working with URLs in SharePoint, there are two very helpful utility classes: SPUtility and SPUrlUtility
There are three different kinds of url used in different properties of various SharePoint objects: absolute, server-relative and site-relative. One need to be careful with them, especially when site collection is not located directly at web ...
your code is fine appart from one part, you looping on the validation! you need to set date type at the end:
so you have:
i got that from the error you shown:
Unable to find control id
You'd need to enable Session State in your web application.
Execute the following powershell script Enable-SPSessionStateService –DefaultProvision
Apply the following web.config change:
More information is available at: Using Session State in SharePoint 2010
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 ...
Using JSOM in the past I have experienced this trouble when I have a lack of system resources, specifically when my systems RAM has less than 5% available.
The fact that you are getting a Service Activation Exception leads me to believe this may very well be the case, and can be verified in Windows event viewer.
Close some applications or disable some ...
That is simple. Do not have two references to jQuery in your webparts. Load jQuery only once. What happens is that a new jQuery overrides all the extensions...
Consider this. Every js code declared as <script> is loaded synchronously.
Web Part 1 loads jQuery and fancybox. Fancybox is an extension of
Web Part 2 loads jQuery again, and ...
Here is a link to all possible values: http://msdn.microsoft.com/EN-US/library/ms412690
In your case you should use EditListItem or AddAndCustomizePages depending on type of page and more exact scenario.
The MSDN above has the full definitions for the two options.
If not one specific is doing it for you, you can combine multiple ones by separating them ...
This may be unrelated, but did you put a proper URL in your project's Site URL field, and can you properly deploy and activate an empty solution from VS?
I find that the designer files are not generated properly if my site URL is faulty (VS can't connect to it) or if I lack the permissions to deploy and activate a solution from within Visual Studio.
You can create a single global resources file and deploy it to:
This post shows you more on how to do it: http://blogbaris.blogspot.co.uk/2012/07/localization-with-sharepoint-2010-and.html
The post is based on SP2010 but works just as well for SP2013
I finally found one solution. It has all to do with the url of the site. It should be a valid url. It is a bit strange though because the url that I was providing was valid. To test it I created a new webapp with a site collection eg.: http://mysomething:5040 and visual web part was created successfully with the design file "....g.cs".
You should always select your list based on the URL, as the Title is more likely to change. And don't do SPWeb.Lists as this will enumerate all lists on the web site. Use this similar snippet instead:
public Guid? GetListId(string siteUrl, string listUrl)
using (var currentSite = new SPSite(siteUrl))
using (var currentWeb = currentSite....
You need to load webpart properties before you can read them. That is,
var properties = webPart.get_properties();
Then read the properties in success method.
Set Always Force Install to True in for your feature. (Assuming you are using Visual Studio)...Check the feature property window and you should see this option!
If you are using PowerShell, you can also use :
$sln = Add-SPSolution mySolution.wsp
Install-SPSolution -Identity mySolution.wsp -GACDeployment -Force
Its common that SharePoint Sites stops working for a while till the deployment completes as it includes IIS Application Pool Recycle retracting/adding solutions and its assemblies into layouts folder.
Similarly for debugging, Visual Studio will attach an IIS worker process(w3wp.exe) to the specific application pool to debug the solution. So the sites will ...
Arun's solution would work, but another is to give each developer their own dev environment. So, each dev would have their own server to work on. If you haven't thought about this before, then it may seem extreme, but this is the common strategy people use. Create an image that's a single server farm, and let each dev have a copy of it to run on their ...
SPFX web is not supported yet in SP2016 on-primise. It will be available via Feature Pack.
Currently SharePoint Framework is available in SharePoint Online only.
In the future it will be also available for SharePoint 2016
on-premises. At this moment there are ...
The original (Farm Solution) Visual Web Part uses a User Control for the UI. The User Control gets deployed up into the SharePoint System Folders and the Web Part just dynamically loads the User Control into the page at run time.
In a Sandbox Solution we can't deploy files into the SharePoint System Folders so we can't use the same technique. To address ...
change your code to:
<Taxonomy:TaxonomyWebTaggingControl runat="server" ID="taxProjectOwnerDepartment" Visible="true" IsMulti="false" IsDisplayPickerButton="true">
<asp:CustomValidator ID="rfvProjectOwnerDepartment" runat="server" OnServerValidate="validator_ServerValidate" />
now in your codebehind ...
AFAIK, the "SharePoint 2010 - visual web part" solution template will create a web part targeted at SharePoint 2010, while the other will create a web part to be deployed to a SP 2013 farm. If anything else, the referenced assemblies would be different so I strongly advise against mixing the two (that is - assuming that VS actually allows you to do that).