we currently have the need to display Webparts of a Sharepoint 2007 instance in another Portal (Liferay). I'm not familiar with Sharepoint. After some searching, I wasn't able to find a satisfiing answer. For Sharepoint 2007 there was announced the WSRP Toolkit (Webservices For Remote Portlets). http://archive.msdn.microsoft.com/WSRPToolkit
Does anyone know if the Toolkit still works somehow the 2010 Version of Sharepoint (I failed when I tried)
Is there maybe a way to access a single Webpart by URL (-parameters)
Does anyone know another way to solve the Problem of displaying webparts in other Portals?
Thanks for you attention,
Andreas
Related
Using MS Access desktop and trying to create a new sub-folder in Sharepoint (office 365 version) for each record created. Have scoured the web for ideas, tried MkDir, json, and scripting but cannot figure it out. I am sure it must be fairly simple. It works locally to my computer so the issue is me not understanding how to connect to Sharepoint on the cloud.
Lots of brilliant people out there, any ideas?
I need your help on a generic question. I am using Visual Studio 2012 to develop my Windows Forms Application that is running only on my machine locally to support my work. I have Windows10 and Office2016 installed. My Application interacts with MS Access (via System.Data.OleDb) and Outlook+Excel via Office.InterOp. Fine.
Today I received the information that our Company is rolling out Office365 and I started researching how this could impact my development work. I am not a programmer (more business) but always try to teach myself. But in this case I have no clew what all that means. I read about registering my Application before I connect to Outlook, Outlook REST API and many other things.
So my questions are:
Will my Application work the same way after migrating to Office365 (InterOps) ?
Is there a good tutorial out there that helps me getting started?
I really appreciate any help and guidance on this. Have a great weekend. Thanks
First what is yoy current version of Office you use ? Then do you know if your compagnie will move to office pro plus ? (I suppose yes)
Even if you pass to Office ProPlus the interop will still work, you should after starting to move you app using Graph API, but this API is to interact with the Office 365 data, not the Office App, it's in this case you register your app o the Azure Active Directory to have the right to use Office data
It is working on the web but not on the desktop. I have read all the available threads already but I am still not able to figure out the reason
Please guide, any help would be appreciated
My Manifest is compatible with outlook 2013 or later, what can be the reason?
Do you get any errors?
The Troubleshoot user errors with Office Add-ins page describes the information to help resolve common issues that your users or you encounter with an Office Add-in.
You can also use Fiddler to identify and debug issues with your add-ins.
Does a custom (i.e. one I've developed for SharePoint 2010) visual webpart have to operate within a sandbox solution in SharePoint office 365, or can it be a farm solution?
Thanks, Confused
Web parts have to be sandboxed for SharePoint 365. Visual web parts can't be sandboxed since the ascx control that comes with the web part is copied to the file system. if you need to create a visual web part in SharePoint 365 you can use the SharePoint Power Tools extension.
http://visualstudiogallery.msdn.microsoft.com/8e602a8c-6714-4549-9e95-f3700344b0d9
There you have the option to create a visual web part that can be deployed as a sandboxed solution.
Independent from the type of SP-I (SharePoint Item) you're creating, Office 365 only supports sandboxed solutions.
Microsoft is going to migrate Office 365 to SharePoint 2013 within the next weeks/months. When migration is done, you can also create Apps using the new SharePoint 2013 App model.
But for now, it's only possible to deploy Sandboxed solutions, because it's not allowed to do any changes to the filesystem or elements, that are available across the boundaries of your SiteCollection.
When it comes to WebPart development, you've to remember that it's not possible to impersonate using SPSecurity. (There are more limitations for Sandboxed Solutions, you should revisit the MSDN in order to get a common understanding of what you can do within the Sandbox)
I have made a site in SharePoint Foundation 2010. I used team site as a starting template. I have saved it as my own custom template.
Next, I have added that solution to SharePoint Server 2010. When I tried to create a new site in SharePoint Server 2010 based on it, I got an error that a feature is missing. Missing feature guid is e8389ec7-70fd-4179-a1c4-6fcb4342d7a0. Looking at the solution's ONet file, it appears to be a 'ReportServer Feature'.
Now, my question is: Is it really possible that SharePoint Foundation 2010 may contain features that do not exist in SharePoint Server 2010? Isn't SharePoint Server supposed to be wider set of SharePoint Foundation?
Please help. Thanks.
Same topic here: http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/db59de6e-e13a-47e8-9fc7-5f1fe461be86
Paul, an MVP has answered this topic on MSDN forum. You may find the link to the thread in the question above.
In short, any feature that exists in default SP Foundation instance must exist in SP Server as well. In my case, I have had installed Sql Reporting to the server machine running SP Foundation, which has subsequently added 'Reporting Server' feature. That's where all the commotion came from. Cheers everyone!