Tag Info

New answers tagged

0

The web.config for application pages is located in the {SharePointRoot} folder. However, I recommended that you move your service to the ISAPI folder (mapped to _vti_bin) or to a separate IIS website.


0

This answer may not fully apply as I was using a ListViewWebPart (not XsltListViewWebPart) but they are similar so it might help. The following code allowed me to use a ListViewWebPart from one site (with the embedded GUIDs in the source code) on a different site collection entirely: listViewWebPart.ListId = theList.ID; listViewWebPart.ViewGuid = ...


0

Solution: I was using CKSDev to deploy my code, the problem was there. I tried the Visual Studio deploy, did an iisreset and it worked.


1

it took me 2 days, but I figured it out. It turned out quite simple: Everything with the code was ok. The problem is that the feature had to be activated by default in the Administrative Web site(the feature was scoped as Web). If you have a problem like this, you just add the following code to the Feature Manifest as a Feature attribute: ...


1

Remove master page reference from your site first, than place this sample code to try it out <html> <head> </head> <body> <form runat="server"> this the the policy page <br /><br /> <input onclick="close_window()" type="button" value="Close" /> <asp:Button ID="Button1" ...


2

Remember that Application pages are just normal .aspx pages, nothing SharePoint specific. So you can just remove the DynamicMasterPageFile property from the <%@ Page %> tag. Just remember to add html, head, body now that a masterpage is no longer dictating the html structure.


2

You should have a line similar like this in your .aspx <%@ Page Language="C#" AutoEventWireup="true" CodeBehind="CreateCollabWeb.aspx.cs" Inherits="Something.Layouts.CreateCollabWeb" DynamicMasterPageFile="~masterurl/default.master" %> Here you can point to a different master page: <%@ Page Language="C#" AutoEventWireup="true" ...



Top 50 recent answers are included