I'm fairly new to SP Online, but haven't had much luck finding information regarding moving a SP10 web part to SP Online. It looks like I may have to recreate it using the SharePoint Framework. Does anyone have experience with migrating an existing SP 2010 webpart successfully to SP Online or is the Framework the only way to do that now?
Even I tried with Sandboxed solution deployment but seems this option also removed from Microsoft itself.
Related
I'm trying to get a SharePoint 2010 web portal working for a TFS 2012 team project. Most of the functionality is working, but I'm having a difficult time getting the custom work item controls we've built working in the SharePoint Project Portal site. (They're working fine within Visual Studio, we haven't tried getting them working in the default TFS Web Access portal.)
My questions are:
Since the TFS Web Access method for creating custom properties have been updated, is that method appropriate for the SharePoint site? (I doubt it, since jQuery is necessary and isn't included by default in SP 2010, but I thought I'd ask.)
Whenever I try to test this, all I get is "Error: Unable to create 'FieldName'" with nothing in the ULS logs. Is there any way I can debug this?
Are there any examples available online that I may have missed in my searches?
After a lot of digging and frustration, I have finally gotten a simple control working. Indeed, SharePoint 2010 expects the custom controls to be formatted similarly to Web Access 2010, not Web Access 2012. Here is an example that helped:
http://code.msdn.microsoft.com/windowsdesktop/CSTFSWebAccessWorkItemMulti-ace1b01e
Also, if you install the 2008 Team System Web Access (yes, 2008), you'll get a Word document with some helpful documentation.
Here are some caveats:
The Word documentation states that the control needs to inherit from both IWorkItemControl and IWorkItemWebControl. Since IWorkItemWebControl contains all of the fields that IWorkItemControl does, and IWorkItemControl is declared in a DLL that references .NET 4.5 (not good for SharePoint 2010), I referenced only IWorkItemWebControl and it seems to work.
The documentation states that your control needs to inherit from System.Web.UI.Control to work, but the UserControl doesn't work. I had to inherit from one of the WebControls to get it to work.
The custom controls need references to TFS 2012 versions of several DLLs (which are listed in the sample download), but the only place I found them were in the GAC on the SharePoint server. So I copied them from the GAC onto my local machine for development.
Deploying is easy - all you need to do is place the .wicc file and the DLL into "Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\Tswa\CustomControls".
If I find anything else, I'll post it here.
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 a complex workflow, written in VS2010 (not sharepoint designer) for Sharepoint 2010.
Is there a document somewhere (MS?), with the recommended steps, to deploy an updated workflow, without cancelling the existing running instances of the workflow?
I can easily deploy the new workflow, however, the problem is that, I do not want to kill the existing instances of the running workflow (which is what happens by default when you deploy the workflow).
Through trial and error, I have a long list of what I think I need to do, but I really would like some confirmation.
I also need to use the new Package capability to deploy the workflow, since VS.NET will NOT be installed upon the sharepoint production server.
Thanks!
Dave
I had struggled myself with this in the past (2007 times) but couldn't find an elegant way out except completing the workflows.
Could this give you pointers - SharePoint Workflow Versioning with VS 2010
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!
I have been using Sharepoint 2010 Beta for developing an Access database solution using Issues Web Database template.
After installing the final release version of Sharepoint 2010 on the production server, I have been unable to find Issues Web Database template. Has it for some reason not been included in the final version, and is there a way of including it?
What I need to do is to install the template on the server and synchronize the content with the existing solution on the developing server.
Thanks
Web Database Templates are not available to create site collections. I dont know if this can be changed. They are available for sites and sub sites.