Tag Info

Hot answers tagged

4

In order to view the Closed Web Parts, you just need to do: "Add Web Part" in any Web Part Zone Search for the "Closed Web Parts" category in the Web Part selection menu that appears on the Ribbon Your closed web parts should be right there


4

Don't worry. The pure use of CreateChildControls is only due to old habits of SharePoint developers due to the way Web Parts was developed in the past. If you prefer to build your web parts declaratively due to the increased productivity then just use that method. The only reason to prefer CreateChildControls is if you need the extra flexibility of adding ...


3

From a user perspective, there is no difference between web parts and app parts. Both add functionality to a SharePoint page. Technically web parts run inside a SharePoint context, and as a consequence may make an entire page unresponsive if the web part fail to load. An App part run outside SharePoint context and displays its result in an iFrame. If an app ...


2

I think the old trick of the calculated column for emitting HTML could do in this case: create a new calculated column of type Number with the following formula: ="<a href='" & "http://myCompany.com/Lists/Catalogus/AllItems.aspx?" & [Title] & "'>" & "http://myCompany.com/Lists/Catalogus/AllItems.aspx?" & [Title] & "</a>" ...


2

You can create a calculated column in your Customers list with formula =CONCATENATE("http://myCompany.com/Lists/Catalogus/AllItems.aspx?Expertise=",[Title]) and then use a list view web part which shows only this calculated column


2

For this, you'll want to use the ListItemCollectionPosition property of SPQuery. SPListItemCollectionPosition is the class which helps to achieve paging and sorting the results fetched by SPQuery. See here: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.splistitemcollectionposition.aspx and here for a more comprehensive example


2

You can use SPSiteDataQuery for getting List data from multiple sub sites of same site collection. Below is the basic code to start with ,bywhich you can use to get all announcement list items from the different sub sites: using (SPSite oSPsite = new SPSite(SPContext.Current.Web.Url)) { using (SPWeb oSPWeb = oSPsite.OpenWeb()) ...


2

I can think of following differences between app parts and webparts: SharePoint Server Object Model code is not allowed in app parts (only client object model code is allowed) whereas web parts allow both Sever and Client object model code. App parts provide deployment isolation. However, deployment of web parts causes files to get deployed to 15 hive, ...


2

Use the following approach 1.) Create a visual webpart 2.) First add the following on the .ascx page Code for .ascx page <SharePoint:ListViewByQuery runat="server" ID="customlistview" /> 3.)Add the following code to query your list(assuming you have created the site and web objects) Code for .ascx.cs page SPList list = ...


2

It appears that this has to do with IE9, IE10, IE11 document standards for the client's browser. The problem is in the pickerdialog.master. As the People Picker is using the pickerdialog.master file, you need to add the following line in the head element. meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" Find the pickerdialog.master file in ...


2

Because there is no resources file specified in the call to the some resource key in your web part, SharePoint will look in the default places where you can place your resources files in the following order (given that your language is US-English). You must check all resources strings in your web part also ULS should have some string like "Localized ...


1

The feature will also need to be activated in order for web part to show up. The next time you deploy a WSP, the feature will remain activated/deactivated depending on its state. That is, if the feature is activated and you deploy the WSP again, you won't need to activate the feature. However, if it is deactivated, it need to be activated again.


1

This answer may be specific for SharePoint 2010: Using javascript (even better with jQuery) you can accomplish this. On the webpart page, your page viewer part will contain a div element with a unique id (e.g. WebPartWPQ3). Inside this div is an iframe that points to the page to display (i.e. src="your page"). You can use your favorite DOM inspector to find ...


1

Strong Names Strong naming uses a private key to digitally sign an assembly. Strong naming also stamps the assembly with a public key to validate the signature. This technique guards against unauthorized versions of a Web Part. If the public key fails to validate the digital signature, SharePoint Foundation refuses to run the module. When you ...


1

When you create a SharePoint project in VS, look at the dialog that appears: it asks which site you want to use for debugging, and the second question is whether you want it to be a sandbox or a farm solution. (or, for an existing project, you can change this in the properties of the project). There's already been a lot written on both, so read up on them ...


1

Edit the page in Advanced Mode (from Sharepoint Designer). If the button "Advance Mode" is grayed, you need to enable "Enable Detaching Pages from the Site Definition". You can find this setting on the site in the section "SharePoint Designer Settings" (http://site-name/_layouts/15/SharePointDesignerSettings.aspx)


1

You can try to detach and re attach the content DB. you can try the codeplex tool for this SharePoint Feature Administration and Clean Up Tool If features are not deactived before removal they stay as an orphan in the system (contentdb) and can cause issues lateron. You can use the poweshell code from the below Wiki Article to remove the orphan stuff. ...


1

As many of you may know, Microsoft just rolled back SP1 for SharePoint 2013! Besides, SP1 is not a trivial update and will likely require an entire rebuild of your SharePoint farm. The much easier fix is to install the following hotfix: KB 2600088 The issue is that the browser definition files for .NET 4 in conjunction with ASP.NET Forms are not ...


1

Andrew Connell is pretty keen on SharePoint 2013 SPAs. He has several blog posts about his experience with Breeze + Angular such as this one "Getting BreezeJS to Work with the SharePoint 2013 REST API". His PluralSight course on the subject will be published very soon along with a sample. There's a "Breeze.Angular.SharePoint" nuget package that loads your ...


1

Paging using CAML cannot go to a Nth page directly, like you can do in SQL. For using paging, you need to use ListItemCollectionPosition property in the SPQuery. Tips Limit the Columns (ViewFields) of your query Set the RowLimit on the SPQuery Don't forget to explicit the OrderBy in the Query Choose an indexed column (if possible) to OrderBy Every time ...



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