Tag Info

Hot answers tagged

2

The issue is that SharePoint 2010 is on .NET 3.5 (the .NET 2.0 stack). Which means the SharePoint web application does not in anyway support .NET 4. You would need to run that .NET page in a different web application with a different application pool. (You can create the application under the same IIS site, however you MUST use a different application ...


2

The obvious answer is "with JavaScript", e.g. jQuery. You may also be able to override the page viewer web part class with code. However why would you need to do this? This error will only show, as the message states, for browsers prior to Internet Explorer 5. The minimum requirements for SharePoint are above that.


1

The page viewer loads into an iFrame. I would think you would need some fancy javascript on both the parent page and the iframe content. You could then call into the parent and activate the functions. If the content is not hosted on SharePoint you might some XSS issues. Parent: functon next(){ Do something } In the iFrame: <a ...


1

This webpart is provided with the feature "BasicWebParts" (ID: 00BFEA71-1C5E-4A24-B310-BA51C3EB7A57). It's a hidden feature, activated by the out-of-the-box site template. See C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\SiteTemplates\MPS\XML\onet.xml for example. In your case, are use using a custom site ...


1

Developing web parts is not SharePoint specific, but standard ASP.NET webforms, even though most only use it for SharePoint. And nothing prevent you from embedding the web part into a bare page which can be used in Iframes from other systems. The main thing is who do you want to empower? The end user or the developer? In SharePoint development you goal ...


1

You could just pass the url as a query string parameter to the page in the subsite. Wouldn't something like this work? http://myportal/mysite/mysubsite/default.aspx?refurl=http://myportal/mysite In your code on the subsite page, you can read the querystring and create your site object using that. The query strings should be retained on postback. UPDATE: ...


1

Please try the following piece of code and see if it works. SPLimitedWebPartManager wpManger = site.OpenWeb().GetLimitedWebPartManager(your page url, System.Web.UI.WebControls.WebParts.PersonalizationScope.Shared); PageViewerWebPart pageViewerWP = new PageViewerWebPart(); pageViewerWP.Title = "My Page Viewer"; pageViewerWP.ContentLink = ...


1

It sounds like you don't have permission to view those Site Pages. I find half the problems I run into with SharePoint are permissions issues. If you have access to an Site Owner or Administrator Account, login to that account and try the code. If not, as always, contact your system administrator.


1

You cannot access the current SharePoint user information from an external web site. The page viewer web part will only include your ASP.Net page in an iFrame. The SharePoint Authentication will not be passed through. To get the URL you should be able to parse the http-referrer. That should be the surrounding SharePoint page's url. To receive the user ...



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