Tag Info

Hot answers tagged

4

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


3

you can create a separate Project eg. "Common" where you include those classes. You can reference that assembly than from your other Projects. Of course, you have to ensure that this wsp is installed along your other wsps (which use that dll)


3

Why are you using the client side ID. Use the server side ID "abc". It will work. Regards.


2

You could use the something like const string scriptKey = "jQuery"; if( !Page.ClientScript.IsClientScriptIncludeRegistered( Page.GetType(), scriptKey ) ) { Page.ClientScript.RegisterClientScriptInclude( Page.GetType(), scriptKey, ResolveClientUrl("~/js/jquery.min.js" ) ); } The key to making this work is that you need to include the same key ...


2

I suspect this behavior could be related with JavaScript template itself. It seems that when XLV web part is instantiated via Visual web part, custom template is not applied since clienttemplates.js (part of CSR library) library is not yet loaded. In order to make sure the custom template is registered property, try to enclose it using SP.SOD.executeFunc ...


2

There are 3 List Templates for Tasks: Project (Gantt) Tasks (TemplateId: 150) Tasks (2010) (TemplateId:107) Tasks (TemplateId: 171) Did you verify that the requested List is using the Template you ask for?


2

This is the code from my project <asp:DataList ID="dlPaging_Top" runat="server" RepeatDirection="Horizontal" OnItemCommand="dlPaging_ItemCommand" OnItemDataBound="dlPaging_ItemDataBound"> <ItemTemplate> <asp:LinkButton ID="lnkbtnPaging" runat="server" ...


2

You can get (or set) the selected value from code-behind (e.g. when user clicks a button) with myDateTimeControl.SelectedDate. EDIT: See https://karinebosch.wordpress.com/sharepoint-controls/datetimecontrol-control/ for examples (SharePoint 2007, but still relevant in 2013).


1

The user control which you deploy will be saved inside hive folder inside control templates. If your path is folder path in solution is "MyProject/Webparts/Mywebpart.ascx" then the path which you should use will be like this "~/_controltemplates/15/MyProject/Webparts/Mywebpart.ascx". If you are checking whether page is in edit mode or display mode ...


1

You should try as follow. It will work. <SharePoint:SPGridView ID="GridView1" runat="server" AutoGenerateColumns="False" AllowSorting="True"> <Columns> <asp:ImageField DataImageUrlFormatString="~/_layouts/15/MyProject/images/icons/{0}" DataImageUrlField="MyType"></asp:ImageField> </Columns> Hope it will ...


1

You can save User data as below string[] userarray = a.CommaSeparatedAccounts.ToString().Split(',');; SPFieldUserValueCollection usercollection = new SPFieldUserValueCollection(); for (int i = 0; i < userarray.Length; i++) { SPFieldUserValue usertoadd = ConvertLoginAccount(userarray[i]); usercollection.Add(usertoadd); } ...


1

I was able to get my solution upgraded from a 2010 project to 2013 using the following. Note that this will update your solution to use the new 2013 API. It is possible to update just the project file but still run in 2010 mode. First edit your .csproj file (for c#). Modify the target framework to this: ...


1

Not sure but this could be the problem: lvwp.JSLink = "~site/_layouts/15/JS/jquery2.1.1.min.js|~site/_layouts/15/JS/JSLinkFields.js"; I think you should remove the ~site part from the URL:s, like this: lvwp.JSLink = "/_layouts/15/JS/jquery2.1.1.min.js|/_layouts/15/JS/JSLinkFields.js"; Also make sure to set the ClientRender ...


1

When attempting to troubleshoot something like this, remember that F12 is your friend. The CSS tab of most browser debuggers - IE, Chrome, Firefox - will allow you to select an element on the screen and see all CSS affecting it. In the case you describe, the menu element or one of its parent containers is being overridden by a style from one of the following ...


1

You are passing two strings (name and WOGLicensetext) to your AppendData function, yet in the function you are trying to access a result object, which probably doesn't exist in that scope. So you should change $("textarea#idTxtArGenHtml").append(result.WOGLicensetext); to $("textarea#idTxtArGenHtml").append(WOGLicensetext);


1

I wrote this code here so I can't guarantee it will work as is. It should get you pointed in the right direction. private Func<string> _func; protected void Page_Load(object sender, EventArgs e) { _func = new Func<string>(GetCurrentUserData); Page.RegisterAsyncTask( new PageAsyncTask( new ...


1

The CSWP can return any content from the search index. Use it on your SharePoint 2013 sites when you are connecting to a search service and want to return indexed search results in your pages. The CSWP returns content that is as fresh as the latest crawl of your content, so if you crawl often, the content that the CSWP returns is more up-to-date than if you ...


1

Open the list in Shareoint Designer and create a new NewForm.aspx - we need the old one in case of a problem. Then, using UI edit, delete the webpart and add yours webpart


1

Create a feature receiver. On activation event use below snippet to change the Page. SPList lst = web.Lists["ListTitle"]; string newUrl = url; var form = web.GetFile(newUrl); if (form != null && form.Exists) { lst.DefaultEditFormUrl = newUrl; lst.Update(); } Also make sure to create those pages using Module and Elements.xml file.


1

No, there is no way to deploy a solution to a particular site collection. A solution is deployed either Globally to all web applications or a single web application. It is the feature inside the solution which can be deployed to a farm/webapplication/site collection/web.


1

Usually you deploy your farm solution to web application, but you activate solution's feature(s) only on desired site collection.


1

You should get the current site collection rootweb url as below String siteUrl = SPContext.Current.Site.RootWeb.Url;


1

You can loop through the XsltListViewWebPart internal controls and hide the Toolbar control like: //Find the ToolBar control and set visible to False foreach (Control ctrl in webpart.Controls) { if (ctrl.GetType() == typeof(ViewToolBar)) { ctrl.Visible = false; break; } } Or you can use Reflection to set the Toolbar to none for View, ...


1

When you use Visual Studio to build your visual web part. In the Feature Design mode we you gave the scope of feature as Farm by mistake and when we try to deploy the solution you will get the error message. "Error occurred in deployment step 'Activate Features': Feature with Id XXXXXXX' is not installed in this farm, and cannot be added to this scope". ...



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