Using Aspx page insted of default portal page

Hi,
Is there a way to add aspx page in a portal.
After login I want aspx page to display hosted on different domain instead of portal default page.
Thanks in advance.

Oh, I see the misunderstanding. The EXE you talk about is your LV built application - not related to ASP.NET. Okay...
What you want to look up in your LV docs is "remote front panels". This allows you to either embed a dynamically generated image of the VI into the HTML or actually the front panel itself (requires the RTE on the client machine). The second form means the display is interactive. Unfortunately, the only web server supported for this right now is the LV web server. However, you could do some tricks to get the image (option #1 of RFP) from a LV server and then post it up on the IIS server.
For example, you could create a little LV application that uses the IE control in LV to hit the LV web server, grab the page and then save it in the IIS virtual directory.
You other questions...
5. Manage to get your C# code to VB.NET.
I'm not a VB.NET programmer so I can only tell you what you need to do...The PumpMessages dll is C++ so that isn't going to change. To call it from VB.NET, you need to create a DllImport statement. Trying to convert what is in the MSDN sample, it should be something like
<DllImport("C:\Inetpub\wwwroot\MyWebApp\bin\MyLVApp.dll", EntryPoint := "LVDLLStatus", _
   ExactSpelling := True, _
   CallingConvention := CallingConvention.Cdecl)> _
Public Shared Function MoveFile(errStr As IntPtr, errStrLen As Integer, module As IntPtr) As Integer
    ' Leave function empty -
End Function
The other code just calls it. You need to create a VB.NET class with a static constructor (the static Global() in my example), static member (Thread) and static method (ThreadProc).
6. Even though there were few explanations on this area from you this summer , I was not quite clear or to follow  .
Was there any workaround in this area from you on this.
I am not sure what you are asking here..I said of lot of stuff over the summer *grin*, just reply with the specific question
Brian Tyler
http://detritus.blogs.com/lycangeek

Similar Messages

How to use custom aspx page as template for custom content type

Hi,
I have created custom content type and custom aspx page. I want to use aspx page as template for custom content type.
Can anybody please let me know how to accomplish this?
Any help would be appreciated.
Thank you,
AA.

Check if you are looking for the below
http://www.sharepointpals.com/post/How-to-Create-a-Page-Layout-(PageLayout)-with-ContentType-in-SharePoint-2013
Please remember to click 'Mark as Answer' on the answer if it helps you

Using powershell to deploy provider-hosted app and specify remote Url instead of using appinv.aspx page

Hello all,
Could you possibly help me with provider-hosted app development/deployment process.
We developed SharePoint provider-hosted app that works just fine in development environment. Now we need to automate it's installation in test environment via powershell.
In AppManifest.xml that we are deploying we have key instead of explicit URL:
<App xmlns="http://schemas.microsoft.com/sharepoint/2012/app/manifest" Name="ShowAllRoomsApp" ProductID="{922a18aa-5592-b59a-4da9-4791baef02e7}" Version="1.0.0.0"
SharePointMinVersion="15.0.0.0">
<Properties>
<Title>SomeTitle</Title>
<StartPage>~remoteAppUrl/Pages/Default.aspx?{StandardTokens}</StartPage>
If we use as
https://technet.microsoft.com/en-us/library/jj655398.aspx recommends, we cannot specify Redirect Url as we can do this on
/_layouts/appinv.aspx
So now it seems like the only way to deploy this kind of solution is using appinv.aspx page.Or must we apply this URL in AppManifest on developing stage in Visual Studio?
What did I miss?
P. S. Even if I use /_layouts/appinv.aspx after powershell commandlets, I get error.

hi,
to deploy provider hosted app you need 2 things
1. Client ID
2. Redirect URL.
What you can do you can generate app from visual studio using clientID and URL from developer enviornment.
Now a app file is just a simple compressed zip file if you rename it as .zip and extract you will find AppManifest
inside it. So to create an app for Testing enviornment what you have to to Get the CLient ID (from AppRegNew.aspx) in testing enviornment. Unzip .App file change the AppManifest with testing client ID and URL than again zip file and rename as .app.
Now if you upload this file it will work.
To automate this scenerio i have created a simple windows Application in which i Pass the Client ID and StartURl and an App File it unzips the app file make changes to app and again zip it.
public static class AppPackageHelper
public const string StartUrlExpression = "{0}?{1}";
public const string StandardToken = "{StandardTokens}";
public static string Publish(string appPath, string ClientId,string StartUrl)
string tempDir = string.Empty;
string outPutFile = string.Empty;
try
string parentDir = System.IO.Path.GetDirectoryName(appPath);
outPutFile = System.IO.Path.Combine(parentDir, ClientId + "-Winshuttle.app");
tempDir = System.IO.Path.Combine(parentDir, ClientId.ToString());
Directory.CreateDirectory(tempDir);
int lastInd = appPath.LastIndexOf('.');
string tempPath = string.Empty;
string targetFilePath = string.Empty;
string cabPath = System.IO.Path.Combine(tempDir, System.IO.Path.GetFileNameWithoutExtension(appPath) + ".cab");
FileInfo fInfo = new FileInfo(appPath) { IsReadOnly = false };
File.Copy(appPath, cabPath);
XDocument doc = null;
string appManifest = string.Empty;
using (ZipArchive zipArch = ZipFile.Open(cabPath, ZipArchiveMode.Update))
appManifest = string.Format(@"{0}\AppManifest.xml", Directory.GetParent(cabPath).FullName);
ZipArchiveEntry manifestEntry = zipArch.Entries.LastOrDefault(e => e.Name.ToLower() == "appmanifest.xml");
manifestEntry.ExtractToFile(appManifest);
doc = XDocument.Load(appManifest);
XNamespace ns = doc.Root.GetDefaultNamespace();
string defaultUrl = string.Format(StartUrlExpression, StartUrl.TrimEnd('/'), StandardToken);
doc.Descendants(XName.Get("StartPage", ns.NamespaceName)).First().Value = defaultUrl;
doc.Descendants(XName.Get("RemoteWebApplication", ns.NamespaceName)).First().Attribute(XName.Get("ClientId")).Value = setupInfo.ClientId.ToString();
doc.Save(appManifest);
if (manifestEntry != null)
manifestEntry.Delete();
zipArch.CreateEntryFromFile(appManifest, "AppManifest.xml");
int totEnt = zipArch.Entries.Count;
for (int e = 0; e < totEnt; e++)
if (zipArch.Entries[e].Open().Length == 0)
//if (zipArch.Entries.Count > totEnt && e >= totEnt) break;
//zipArch.CreateEntry(zipArch.Entries[e].FullName);
File.Delete(appManifest);
if (File.Exists(outPutFile))
File.Delete(outPutFile);
File.Move(cabPath, outPutFile);
return outPutFile;
catch
throw;
finally
if (System.IO.Directory.Exists(tempDir))
System.IO.Directory.Delete(tempDir, true);
return outPutFile;
using System.IO.Compression.FileSystem.dll.
Also if you want to do it using powershell You need to do the same thing unzip-> changes values-> zip
So basic thing is You need to ahve only valid AppManifest file which contains 2 valid values Client Id and StartUrl
if you changes it inside appmanifest manuall than it will also work. Using above code you can create a console Application to do it. You can use powershell it just that i dont know how to zip unzip in powershell but i am pretty sure you can easily find it
on searching.
Whenever you see a reply and if you think is helpful,Vote As Helpful! And whenever you see a reply being an answer to the question of the thread, click Mark As Answer

How to create a new aspx page in Pages library using Elements.xml without including any aspx page layout in my feature?

Is it possible to have the elements.xml file create a page in the Pages (or SitePages) library without actually including any sort of page layout or aspx artifact in the feature?
I see no reason to add a mywebpartlayout.aspx to my feature just so I can deploy a Home.aspx based on the BlankWebPart.aspx page layout.
I'm sure there is something obvious I am missing with regards to the Elements schema (which is why I've almost given up on using it completely and just gone to pure C#) but
I would really like to do this kind of simple stuff with declarations if at all possible. Must less code to write, debug, test and maintain.

I don't see how my question keeps getting misunderstood. This seems to be very clear and clearly not answered: "Is it possible to have the Elements.xml file
create a page in the Pages (or SitePages) library without actually including any sort of page layout or aspx artifact in the feature?"
I can't be more clear than "without including ANY sort of page layout or aspx artifact (meaning anything ending in aspx) IN THE FEATURE". I am not capitalizing to yell,
only to emphasize. Your disagreement is based on a link that shows ADDING AN ARTIFACT (the dummy MyPage.aspx) to a feature. I am asking if it
is possible (again, I cannot be more clear) to just use an Elements.xml file to instruct SharePoint to make a new item in a Pages or SitePages library.
Your definition of page includes Page Layouts and what you call Web Part Pages (again, a type of page layout + data in a site pages list that says what webparts
to display). Page Layouts are clearly NOT items stored inside of a SitePages or Publishing Pages library. Those libraries are just lists whose records
define the parts to show inside a specific layout.
When I refer to a Page I mean an entry into a pages (site pages/publishing pages) list. If I wanted to deploy a page layout then, quite obviously, I would need
to include it into my solution. I think maybe you are assuming that I do not know the difference. I do. The question is, can an Elements file alone be enough to instruct SharePoint to make a new entry into a Pages or SitePages library.
Now, your second link does show how to reference an existing Page Layout. Thank you for that. It is excellent. But this still leaves the problem of having to
add some sort of aspx page into the solution. Let me try to explain why I feel this SHOULD BE unnecessary: The aspx file will not have anything on it if I am referring to the ~sitecollections/.../BlankWebPartPage.aspx layout.
All web parts and content that should appear on the new page can be described IN the Elements.xml file. Any sort of aspx file is unnecessary, it seems to me.
So, if I am referencing a ~sitecollections/.../BlankWebPartPage.aspx page layout and specifying the web parts to add to the page, why should there be a
requirement to have some aspx file within the feature? That's what I am trying to figure out.
I am not asking for source code as proof. I am asking for an Elements file that does NOT reference anything AT ALL inside the Visual Studio solution for reasons I just described.
If you do not know how to do it then perhaps it cannot be done but I would like the question to stay unanswered for a little while until someone can demonstrate either a) it CAN
be done or b) a link to some Microsoft document stating that it is MANDATORY to have a physical element within the feature that gets copied to the environment.
I think it is important to understand what is being asked before insisting you have answered. It is clear from your posts that you have not fully understood the question yet but
I am hoping this posts makes it clear. I really appreciate you taking the time to respond, though. You seem to be the only one up for the challenge! :)

I couldn't use Crystal Report Viewer Control in my ASPX page.

Please I'm having a problem with crystal report viewer control which I couldn't resolve. I'm using VS 2008 and Framework 3.5.
I building an ASP web application and when I add a CrystalReportViewer to my ASPX page I'm getting the following
error.
"Error 20 Type 'CrystalDecisions.Web.CrystalReportViewer' is not defined."
I think maybe because I'm not having the right reference file. I'm using Crystal Reports 2008 and also I installed the following
Service Packs:
cr121_redist_install
CR2008-SP1
CR2008SP1-Fixes 1 and 2
cr121_clickonce
I check all the reference files in my project and they are as follow:
CrystalDecisions.CrystalReports.Engine (12.0.2000.0)
C:\Program Files\Business Objects\Common\4.0\managed\dotnet2\CrystalDecisions.CrystalReports.Engine.dll
CrystalDecisions.Enterprise.Framework (12.0.1100.0)
C:\Program Files\Business Objects\Common\4.0\managed\CrystalDecisions.Enterprise.Framework.dll
C:\Program Files\Business Objects\Common\4.0\managed\CrystalDecisions.Enterprise.InfoStore.dll (12.0.1100.0)
C:\Program Files\Business Objects\Common\4.0\managed\dotnet2\CrystalDecisions.ReportSource.dll (12.0.2000.0)
C:\Program Files\Business Objects\Common\4.0\managed\dotnet2\CrystalDecisions.Shared.dll (12.0.2000.0)
Please Why I'm getting this problem? How I can resolve it?
Thanks.

If you have a viewer on one of your forms, delete it off the form and re-add it, ensuring that the crystalreports.web assembly referenced in your project is version 12.
Ludek

Default.aspx page reverting

I am the administrator for a custom SharePoint application. The application is developed in-house. There appears to be an issue with one of our current solutions. The solution should be updating the default.aspx page under the STS template.
It appears that when I deploy this solution, it works fine for a short time - however, at some point in time, the default.aspx page under "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\SiteTemplates\sts" reverts,
and the default page that came shipped with sharepoint returns.
The shipped custom default.aspx adds a custom zone to the page layout, and the result is that any user who has placed a web part in the zone has their web part shifted to another zone, messing up the page layout.
At the suggestion of the development team, I copied in the default.aspx from the solution file. This corrected the issue - but again, it was only for a short time. I go back and look now and it has reverted back to the same date/filesize, etc.
as a backup I took of the default.aspx before deploying the one from the solution.
Is there a way that I can update the SharePoint content DB with the appropriate default.aspx, after deploying it manually? I think what is happening is that the SharePoint content DB is deploying it's copy from the database - so i would like to update
the database so that the solution deployed default.aspx becomes the authoritative copy.
Thank you

Because Microsoft may at any time override your changes with any patch (e.g. security hotfix, Cumulative Update, Service Pack) and you're back to where you've started.
It is just bad development practice, as well.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Hidden Report Viewer Confiugration Error on aspx pages that use report viewer web control

I try to fix the problem. The error below is embedded on aspx pages that use report viewer web control. Please note that the div element is hidden, and the reportviewer is displaying correct contents.
Div element hidden on aspx page
<div id="ReportViewer1_HttpHandlerMissingErrorMessage" style="border-color:Red;border-width:2px;border-style:Solid;padding:10px;display:none;font-size:.85em;">
<h2>
Report Viewer Configuration Error
</h2><p>The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file. Add <add verb="*" path="Reserved.ReportViewerWebControl.axd" type = "Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> to the system.web/httpHandlers section of the web.config file, or add <add name="ReportViewerWebControlHandler" preCondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> to the system.webServer/handlers section for Internet Information Services 7 or later.</p>
</div>
I tried adding the two elements to web.config, but to no avail.
Add below to system.web/httpHandlers
<add verb="*" path="Reserved.ReportViewerWebControl.axd" type = "Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
or add below to system.webServer/handlers for Internet Information Services 7 or later.
<add name="ReportViewerWebControlHandler" preCondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
The required assemblies below are installed under C:\Windows\assembly folder. I have installed both Microsoft ReportViewer 2010 Redistributable, and 2008 SP1.
Microsoft.ReportViewer.WebForms, version 10
Microsoft.ReportViewer.Common, version 10
Below is the whole web.config:
<?xml version="1.0" encoding="utf-8"?>

<configuration>
<connectionStrings>
<add name="ApplicationServices" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<add key="car" value="myCar" />

</appSettings>
<system.web>
<httpHandlers>
<add verb = "*" path = "Reserved.ReportViewerWebControl.axd" type = "Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

</httpHandlers>
<compilation debug="true" targetFramework="4.0">
<assemblies>
<add assembly="Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="Microsoft.ReportViewer.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="Microsoft.Build.Framework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="System.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
</assemblies>
<buildProviders>
<add extension=".rdlc" type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</buildProviders>
</compilation>
<authentication mode="Forms">
<forms loginUrl="~/Account/Login.aspx" timeout="2880" />
</authentication>
<membership>
<providers>
<clear />
<add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="ApplicationServices" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" applicationName="/" />
</providers>
</membership>
<profile>
<providers>
<clear />
<add name="AspNetSqlProfileProvider" type="System.Web.Profile.SqlProfileProvider" connectionStringName="ApplicationServices" applicationName="/" />
</providers>
</profile>
<roleManager enabled="false">
<providers>
<clear />
<add name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider" connectionStringName="ApplicationServices" applicationName="/" />
<add name="AspNetWindowsTokenRoleProvider" type="System.Web.Security.WindowsTokenRoleProvider" applicationName="/" />
</providers>
</roleManager>
<pages>
<controls>
<add tagPrefix="ajaxToolkit" assembly="AjaxControlToolkit" namespace="AjaxControlToolkit" />
</controls>
</pages>
</system.web>
<system.webServer>
<modules runAllManagedModulesForAllRequests="true" />
<validation validateIntegratedModeConfiguration="false" />
<handlers>
<add name="ReportViewerWebControlHandler" preCondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</handlers>
<httpProtocol>
<customHeaders>
<remove name="X-Powered-By" />
</customHeaders>
</httpProtocol>
</system.webServer>
<system.serviceModel>
<bindings>
<basicHttpBinding>
<binding name="WebService1Soap" />
</basicHttpBinding>
</bindings>
<client>
<endpoint address="http://localhost:58269/WebService1.asmx" binding="basicHttpBinding"
bindingConfiguration="WebService1Soap" contract="ServiceReference1.WebService1Soap"
name="WebService1Soap" />
</client>
</system.serviceModel>
</configuration>
Any idea?
Update:
IIS is7.5, AppPool is Integrated.
I have tried below, none of them works:
1) Add it only to system.web\httpHanders. Changed AppPool to classic, still got hidden error.
2) Add it only to system.webServer\handlers. Integrated mode,still got hidden error.
3) Add both to both element. Integrated mode, still got hidden error.

Hi Kingofwebguru,
According to your description, when you use reportviewer control, you got the error message: The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file.
To troubleshoot the problem, please refer to the following steps:
Click Start, click Run, then type InetMgr.exe and click OK.
Click plus sign next to server name to expand it.
Click Application Pools in left pane.
In Application Pools list, click DefaultAppPool.
In the Actions pane, in Edit Application Pool section, click Edit Settings to check the Pipeline mode.
Configuration settings for the HTTP handlers are specified in the system.web/httpHandlers element and the system.webServer/handlers element. of your application Web.config file. The handler specified in system.web/httpHandler is used by Internet Information
Services (IIS) 6.0 or IIS 7.0 in Classic mode, whereas the handler specified in system.webServer/handlers is used by IIS 7.0 in Integrated mode. To use IIS 7.0 in Integrated mode, you must remove the HTTP handler in system.web/httpHandlers. Otherwise, IIS
will not run the application, but will display an error message instead.
For more information about Web.config Settings for ReportViewer, please refer to the following document:
http://msdn.microsoft.com/en-us/library/ms251661.aspx
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
If you have any feedback on our support, please click
here.
Wendy Fu
TechNet Community Support

How to create a aspx page that expires after first use

I want to create an ".aspx" page in VB that will expire after the first use or 30 minutes
This is to add a password reset page onto our one of our apps.
Thanks

I want to create an ".aspx" page in VB that will expire after the first use or 30 minutes
This is to add a password reset page onto our one of our apps.
Thanks
Hi,
Based on your replay in another thread about sharepoint, maybe you are asking the way used in sharepoint, then I would suggest you consider posting this issue in
sharepoint forum to get supports.
If not, then you could post this issue in the forums Mr. Monkeyboy suggested.
Thanks for your understanding.
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

"Open In Excel" button inside the Xlviewer.aspx page return Error and I can not open excel using local office

Inside the xlviewer.aspx page when I click on "Open In Excel" at first I receive this Error:
Some files contain viruses that can be harmful to your computer. it is important to be certain that this file is from a trustworthy sourceDo you want to open this file?
Then, When I click on Yes, the second error message(below) shows and I can not open Excel using my local Excel Application.
This action couldn't be performed because office doesn't recognize the command it was given.
I should notice that the application is published under the HTTPS protocol.
It is just working with IE 9.0. Neither Chrome nor IE after 9.0.

Sure. I posted here since I suspect that the lastest upgrade may have a bearing on it.
What do I need to move it over to Number and Lion?

We encountered a problem with some client machines that use Firefox version 24ESR and IE8. Ajax requests of aspx pages from Firefox are getting the following er

I encountered a problem with some client machines that use Firefox version 24ESR and IE8.
Ajax requests of aspx pages from Firefox are getting the following error from the iis server (iis version 7.5):
Bad Request - Request Too Long
HTTP Error 400. The size of the request headers is too long.
From analyzing the request that was sent to the server, I saw that the request consist of only the viewstate of the aspx page.
I tried to disable the viewstate for one page and the server got the request correctly.
I do not encounter any issues on these laptops with postback requests from Firefox or when running the same application with IE8.

Sometimes that means that the page address sent is loo long.
Check the link address you are using.
I can't help you further and will send for more help.

SharePoint Foundation 2010 - StoreMan.aspx page not reporting proper metrics

The configuration of my farm:
Sharepoint 2010 Foundation - up to date on all service packs.
SharePoint Offers an Application Page (_layouts/storman.aspx) which enables the user to view the Size usage of files throughout a Site collection.
Currently this page is only referred from within the Site settings. Only those with owner rights can get to the link. We are planning to set up the link on an "Admin Dashboard page" so all users can see and use the information to delete
versions or uneeded documents. It's very handy for this type of reporting.
The problem is that the numbers shown in the .aspx page do not properly reflect the values shown in the libraries. I'm sure the timer job that runs this report is looking at all versions throughout the portal (even in the recycle bin). This is where I see
the innacuracy I'm experiencing. Is there a way to get Storageman.aspx to only run on the files in libraries and ignore the recycle bin? Does anyone have any ideas of how to give users more accurate data on file sizes? Our storage is locally hosted and
we adhere to a strict data usage policy, yet I'm finding it difficult to enforce without the ability to show users where the "problem children" live.

HI Shaun,IE11 is having some know issues with the share point.Make sure the IE (Internet Explorer) Version should be 32-bit and not a 64-bit.
http://expertsharepoint.blogspot.de/2014/08/issues-with-sharepoint-2013-and.html
Anil Avula[MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

Question about including JQuery in a Survey list DispForm.aspx page

In SharePoint 2010, I was able to hide the links for editing, deleting... an existing survey entry in the DispForm.aspx page using the following technique:
1 - Save jquery .js file to the Style Library in the top level site
2 - Save the .js file that has the jquery code to hide the link in the Style Library in the top level site
3 - Reference the .js files in the DispForm.aspx page like this:
<asp:content contentplaceholderid="PlaceHolderAdditionalPageHead" runat="server">
<script type="text/javascript" language="javascript" src='<asp:Literal runat="server" Text="<%$SPUrl:~SiteCollection/Style Library/jquery-1.5.0.min.js%>"'></script>
<script type="text/javascript" language="javascript" src='<asp:Literal runat="server" Text="<%$SPUrl:~SiteCollection/Style Library/hideedit.js%>"'></script>
</asp:content>
The hideedit.js file contains the following:
$(document).ready(function(){
$('#ctl00_m_g_d3bec7ca_bd25_448d_8874_da35856854c5_ctl00_ctl01_ctl00_toolBarTbl').hide();
I am trying to use this same technique in SharePoint 2013 but it is not working.
It appears that neither of the js files are loading properly.
As a test, I put the following in the hideedit.js:
alert('test');
$(document).ready(function(){
alert('from jquery');
Neither of the alerts are displayed when navigating to the DispForm.aspx file.
How do I get JQuery loaded in a survey DispForm.aspx file in SharePoint 2013?

Have you tried this within Designer? Copy the DispForm, edit it and add the JD references below the PlaceHolderMain section and then save. Set this as the default Displat Form and your changes should load.
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

Combine content from selected aspx pages and Consolidate to pdf

Hi All,
I have a new requirement in one of the SharePoint portals :
Contents are placed on ASPX pages using a content editor
A feature to select pages and combine all the content from content editor of these pages into a pdf document
Is there a way to access only
the content stored in content editor and consolidate them in to one data source and then convert that in to a pdf file ?
Thanks in Advance
Pallavi

Hi Pallavi,
According to your description, my understanding is that you want to convert the content in content editor webpart to PDF file.
I suggest you can use read content from content editor web part to a string variable using ContentEditorWebPart class.
Here is a code demo about reading content using ContentEditorWebPart class:
http://sharepoint.stackexchange.com/questions/87499/how-to-get-content-from-content-editor-webpart-cewp-to-a-custom-webpart-on-the
ContentEditorWebPart.Content property:
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.webpartpages.contenteditorwebpart.content(v=office.15).aspx
Then you can generate PDF file with string variable. To create PDF file, you need to download PDFsharp library and reference the dll in your project.
Here is a code demo about creating pdf file using C#:
http://csharp.net-informations.com/file/create-pdf.htm
Best Regards
Zhengyu Guo
TechNet Community Support

Having trouble loading ASPX pages from one website, only in firefox, only on one computer.

I am having an issue where firefox will not load an aspx page, from one computer. It seems to work fine on everything else. I have disabled the virus scanner, firewall and web filter. It works fine on other browsers, on the same computer.
I've tried clearing the cookies, cache and offline storage. I also uninstalled and reinstalled firefox and tried loading the page in firefox safe mode.
Any ideas?
[http://blog.acadianacomputerrepair.info/portals/blog/images/firefoxwontloadaspx/firefoxbrowser.jpg Firefox ScreenShot]

Do you have that problem when running in the Firefox SafeMode? <br />
[http://support.mozilla.com/en-US/kb/Safe+Mode] <br />
''Don't select anything right now, just use "Continue in SafeMode."''
If not, see this: <br />
[http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes]

Error on modifying the SharePoint excel services viewer (xlviewer.aspx) page

I am working on SharePoint 2013 and am following this
article to modify the xlviewer.aspx page in order to pass into it URL parameters. After following the instruction when I reload the new webpage (MyXLViewer.aspx) I am getting the foll. error:-
Sorry, something went wrong An error occurred during the compilation of the requested file, or one of its dependencies. 'Microsoft.Office.Excel.WebUI.ExcelWebRendererInternal' does not contain a definition for 'RowsToDisplay' and no extension method 'RowsToDisplay'
accepting a first argument of type 'Microsoft.Office.Excel.WebUI.ExcelWebRendererInternal' could be found (are you missing a using directive or an assembly reference?) Technical Details
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: db9b709c-966c-80de-156d-15c4b2783b09
Date and Time: 2/3/2014 5:15:03 PM
Go back to site
Can you please try this and replicate and let me know if you are facing the same issue..? Or whether I am doing something wrong here? Foll.
is the procedure I have followed:-
Create a copy of XLViewer.aspx which is located in C:\Program Files\Common Files\Microsoft Shared\web server extensions\15\TEMPLATE\LAYOUTS. I named my copy MyXLViewer.aspx. you can try /14/ incase of SharePoint2010..
Open MyXLViewer.aspx in Notepad and do the following;
<%@ Page language="C#" Codebehind="XlViewer.aspx.cs" AutoEventWireup="false"... --> Change This To --> <%@ Page language="C#" Codebehind="XlViewer.aspx.cs" AutoEventWireup="true"...
Placed foll code before head tag closes </head> on
the page:
<script runat="server">
private void Page_Load(object sender, System.EventArgs e)
if (Request.QueryString["RowsToDisplay"] != null)
m_excelWebRenderer.RowsToDisplay =
Int32.Parse(Request.QueryString["RowsToDisplay"]);
if (Request.QueryString["ColumnsToDisplay"] != null)
m_excelWebRenderer.ColumnsToDisplay =
Int32.Parse(Request.QueryString["ColumnsToDisplay"]);
if (Request.QueryString["ToolbarVisibilityStyle"] != null)
if (Request.QueryString["ToolbarVisibilityStyle"] == "1")
m_excelWebRenderer.ToolbarStyle =
ToolbarVisibilityStyle.FullToolbar;
else
m_excelWebRenderer.ToolbarStyle =
ToolbarVisibilityStyle.None;
</script>

Hi,
The article you referenced might be applied to SharePoint 2007, however, in SharePoint 2013, the
RowsToDisplay property and
ColumnsToDisplay property are no longer supported, so these properties are not guaranteed
to work as they were in SharePoint 2007.
If you want to customize the Excel Web Access Web Part, it is recommended to take a look at the two documentations about Excel Web Access Web Part custom properties:
http://office.microsoft.com/en-001/sharepoint-server-help/excel-web-access-web-part-custom-properties-HA010377893.aspx
http://office.microsoft.com/en-001/sharepoint-server-help/excel-web-access-web-part-summary-HA010105454.aspx
Best regards
Patrick Liang
TechNet Community Support
Hello Patrick,
As I have posted in my question I am interested in customizing the Excel viewer aspx page which opens up when you open an excel book via the document library in SharePoint 2013. The solution you are talking about is to modify the properties of the excel
web part and this does not answer my question.
Again, can you tell me if there is any possible way to customize the XLVIEWER.ASPX page sitting in LAYOUTS folder so that I can access certain properties like AllowInteractivity, etc? Or has this been completely discontinued by Microsoft in SharePoint 2013?
If the RowsToDisplay
property and ColumnsToDisplay
property are no longer supported, are there
any other property that this tag supports?
We have opened the xlviewer.aspx page from layouts folder and can see the foll. control:
<Ewa:ExcelWebRendererInternal id="m_excelWebRenderer" runat="server"
AllowInteractivity="false" AllowPivotSpecificOperations="false"/>
However, there is no documentation available from Microsoft or any other dev sites on this control/tag. This
link mentions that the ExcelWebRendererInternal is a totally useless instance.
I need clarification on this.
We also tried to edit the "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\1033\ewa.strings.moss.js" file. But, any edits corrupts what is rendered on the right click of the pivot chart/table on xlviewer.aspx
page.

Using Aspx page insted of default portal page

Similar Messages

Maybe you are looking for