Does anyone know of a way to "publish" (Perform all the action of publish) a masterpage in "Sharepoint 2010 Foundation"
I can do this really easy in "Sharepoint 2010 Standard"
However the publishing features aren't available in Foundation
Situation
I have 5+ sites each with 5 sub-sites
I would like to change one master page and then publish it to all the rest.
Rather than have to copy it to each site and then set as default for each.
as this is rather repetitive.
You may have already sorted this one but if not then this is a handy little feature to install on to SharePoint 2010 Foundation.
http://spfmasterpageselect.codeplex.com/
It allows you to select a masterpage for a site collection/site and then push it down to all the sub sites.
Hope this helps.
Cheers
Related
New project in Visual Basic using Visual Studio 2013.
Want to add the "Microsoft Internet Controls" component but I can't find it.
What am I missing?
This is the second link on Google:
http://answers.microsoft.com/en-us/office/forum/office_2010-customize/cant-find-reference-to-microsoft-internet-controls/e138ff0c-8046-47b1-9c0c-ac28cebe3c7a
Apparently it may have been renamed "Microsoft Browser Helpers" and you may need to add a reference to "ieframe.dll".
If you need FTP, it is fully supported in the .NET framework. You could start with the examples on MSDN: https://msdn.microsoft.com/en-us/library/ms229718%28v=vs.110%29.aspx
The inet1 Internet Transfer Control is installed with MS Office. Install it and you should have no problem having it become available to use in Visual Studio etc.
It's old but still completely useful in apps. It did all the FTP and HTTP calls for a web crawler I wrote years ago and was fast and completely error-free when crawling 100s of 1000s of web pages at a time while I slept. I'd use inet1 today if I was writing an app that did huge amounts of internet calls as quickly as possible.
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
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)
LS,
I'm trying to open an sharepoint 2010 list with InfoPath 2010 but when I try this I get the following errormessage: "this feature requires sharepoint server 2010 or greater with infopath forms services enabled". Strangely everything works if I create an empty form with InfoPath, it even publishes to SP2010. My current license is "SharePoint Server with Enterprise Client Access License" so it should work.
Thanx in advance
Can you enable the "SharePoint Server Enterprise Site Collection features" in the Site Collection features.
Did you happen to upgrade the farm from Sharepoint Standard to Enterprise?
Make sure that the InfoPath Forms Services are enabled, as the following post suggests:
Infopath 2010 Beta Sharepoint List
I had this same problem. Enterprise features were enabled, InfoPath Forms Services was setup correctly, etc...
What fixed my problem was navigating to the site collection, selecting "Site Settings" from the Site Actions dropdown, Navigating to "Manage site features" under the Site Actions section, then disabling and then re-enabling "SharePoint Server Enterprise Site features".
Tons information about this error, but all the fixes were already done on my setup, just needed to remind the collection it really did have these features enabled...
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!