actually i tried to migrate lists and document libraries from one site to another site in sharepoint 2013 and migrate sites also from 2010 to sharepoint 2013. But,I want to migrate web application from sharepoint 2013 to sharepoint online.
We are limited to creating Site collections only in SharePoint online. You cannot create/migrate the complete web application to SharePoint online in one go. You would have to migrate either a complete site collection or site level.
I have experience migrating with SharePoint migration tool from Microsoft (which is free software) and it worked well.
However, i would suggest to migrate individual site level as it would be easy to manage. I have tried migrating a site collection which failed after 40% and it was difficult to debug where the error was. I later figured it was the nintex form on a document library that was a culprit.
Good luck with your project!
You may use below methods to create apps
Using SharePoint Apps ( https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/get-started-creating-provider-hosted-sharepoint-add-ins )
Use the latest SPFx framework (https://learn.microsoft.com/en-us/sharepoint/dev/spfx/sharepoint-framework-overview) to create apps.
Related
I'm looking at upgrading my current TFS instance and planning to copy and restore databases as per Microsofts Advanced Upgrade which means I am pretty much installing the new product from scratch and restoring the databases then running a migration tool.
I see in the installation notes that you can integrate SharePoint with it as an optional extra. Why would I do this? Is the idea to store project documentation in a SharePoint Document library per project and be able to link to that content rather than as an attachment to the Backlog Items and Bugs in TFS?
I'm having trouble finding any documentation of team workflows with SharePoint and TFS and I suspect that its because no one really does it.
More importantly would SharePoint integration impede future product upgrades or moving to Visual Studio Online?
In my eyes, SharePoint as a TFS portal has become much less desirable due to the improvements in Team Web Access (eg Charting) but it still has some uses.
With the integration enabled, you will see a Documents tab in Team Explorer which will take you to the dedicated SharePoint Portal (created when you create the TFS Team Project) where all your documentation can be stored. Of course without SharePoint integration you can still happily link Work Items to documents in SharePoint, you just don't have a dedicated portal created for you.
If you are using one of the MSF process templates then some useful documents are created for you on SharePoint when you create the Team Project (xlsx reports etc). However, if you are using the much better VS Scrum template then no documents are created even if you have SharePoint integration enabled.
If you are using the Enterprise edition of SharePoint then you get some good dashboards (bugs, code quality etc.) and you can also publish your custom excel reports easily. This functionality requires Excel Services and so is not available in the standard edition (there are some dashboards created but they aren't that useful).
Share information using the project portal
https://msdn.microsoft.com/en-us/library/ms242883.aspx
Your team can use the SharePoint portal to share information in the following ways:
Share data contained in reports or dashboards
Share team progress using predefined or customized dashboards.
Share documents, files, images.
Share team knowledge and processes using the SharePoint wiki.
Reference process guidance for select team project artifacts.
If you want to add a portal to an existing project:
Configure or add a project portal
https://msdn.microsoft.com/en-us/library/ms242865.aspx
What are the possible functionalities that can be modified or added using sharepoint designer with sharepoint foundation 2013? In terms of programming.
SharePoint Designers main purpose is for creating or modifying Microsoft SharePoint sites, workflows and web pages.
As an example you are able to create and modify workflows but cannot compile any code or build your own custom web parts.
I have been working with SharePoint online for sometime.I have been given the task to build an app to create subsites in SharePoint 2013 online website. I prefer working with C# code. I am looking into SCOM to built the App.I want to know if this can be done or does online version only supports JavaScript COM development.
I have gone through multiple materials from Microsoft but no were its clear about autohosted app running on SharPoint online.
I have created a SharePoint App project and set it to autohost. But it throws token not found error while trying to run it against sharepoint online. Looking for advice.
Edit - I need to know if SCOM can be used to develop apps for SharePoint online site
Thanks.
Sounds like you're just starting off with SharePoint apps. SP apps use CSOM (client side object model). I personally prefer JavaScript (JSOM) MSDN JSOM Basic Tasks
If you want to develop against an online environment, then select SharePoint hosted not autohosted. If you are using the app internally then continue, if you are hoping to publish it to the app store then you can report back that this requires full control permission which you are not allowed to request in an app published to the SharePoint store.
When I first started developing SharePoint 2013 online applications I found this article on codeproject a great help.
It might be usefull for you as well: http://www.codeproject.com/Articles/690015/SharePoint-2013-Online-App-Development-Part-1.
Alternatively you could give the official Microsoft Office 365 training kit a look. It's basically the same as SharePoint 2013 online.
http://www.microsoft.com/en-us/download/details.aspx?id=14889
I am new to sharepoint online. At first I need to know the difference between sharepoint online and office 365 preview.
Preview site: https://portal.microsoftonline.com/Admin/Default.aspx which looms like below.
I have also the below site
Now what is the difference between the two. My goal is to create apps and webparts. Which one shall i choose? I have not installed sharepoint 2013 server/ sharepoint foundation. Can i create apps and webparts without installing server2013/foundation2013?
The Office365 Preview is running on the new SharePoint 2013 platform. If you want to build and monetize apps/web parts, you would need to go with this option, as it is the
latest and greatest.
Go to http://dev.office.com to get all of the resources you need including links to the software, tutorials, documentation, etc...
Microsoft provides a free Office365 portal specifically for developers who want to build apps on the online platform. With this, all you would need is Visual Studio 2012 and the SharePoint/Office SDK installed to build apps. You would deploy and debug directly on the online portal without needing SharePoint installed on your environment.
I hope this helps.
I know that Sharepoint 2010 will store almost everything into its databases. We have a reporting application and we would like to publish our reports into Sharepoint 2010. We don't have any integration kit for Sharepoint 2010. What options do we have? Can we publish our reports into Sharepoint database or how this should be implemented?
From your question, I can't tell if you want a programmatic solution or not. Either way, you can store your reports into a SharePoint Document Library
A) By manually uploading the reports to the SharePoint Document Library
or
B) By creating a simple app or web service to do the job for you
http://www.dotnetcurry.com/ShowArticle.aspx?ID=297