1. What’s the upgrade method from 2010 to 2013?
The in-place upgrade method is gone, which is good because it was never a viable option for a production SharePoint upgrade due to the lack of rollback capabilities.
When upgrading to 2013, the approach starts with a content database attachment. When the database is attached, the SharePoint 2013 servers will contain the code for both SharePoint 2010 and SharePoint 2013.
Sites in the attached database will initially operate with the 2010 framework. Site collection administrators will have an option to run a trial upgrade, preview the results, and either revert back to the 2010 version or complete the upgrade to 2013. While they are previewing the results, the 2013 version of the site is actually a copy of the 2010 site.
2. What is the difference between search and e-discovery?
Search is a function performed by any users looking for content. E-discovery is a legal process involving the location of documents related to a specific legal action. When conducting the E-discovery, there are specific pieces of functionality available to legal professionals, such as the ability to place a hold on content to keep it from being destroyed.
3. Is the workflow azure now an on-premise solution?
Both. The Windows Azure Workflow service can be hosted by Microsoft on the Azure platform. This option requires no local solution. However, you can also install this service on your local servers. This may be installed on your SharePoint server or a dedicated server.
4. If BCS can be developed and deployed within the application, how the data connection changes are taken care for migrating those applications on production environment?
The BCS connection in the SharePoint App would be updated to match the environment it was being deployed to. The updated app can be published to the Office.com Marketplace or internal Catalog. The site collection owner will see a message that the App is ready to be updated and they can trigger the update process that contains the updated connection changes.
5. So, the new Client API will have methods to get access to objects above the Site Collection?
Currently, the client API in 2010 can’t.
The Client API can be used to make HTTP requests across and within site collections. This is vastly improved over SharePoint 2010. You can access operations at the Site, Web, Lists, Libraries, Workflows, BCS, Permissions, etc. What you can’t do is higher level operations, such as working with the web application objects or other farm-level objects.
6. How can we get access to server objects?
When developing Apps for SharePoint 2013, most operations that take place within a Site Collection (Lists, libraries, workflows, BCS, etc.) can be accessed using the Client APIs. You could also deploy your own service to your environment that can be used to interact with any Server Objects and then access this service through your App. A Self-Hosted or Azure-Hosted App for SharePoint can be written using server-side technologies such as ASP.NET,
Java, or PHP and can take full advantage of their server-side capabilities.
7. Please mention what BCS is.
Business Connectivity Services. BCS provides the framework to interact with data that resides outside of SharePoint, for example as SQL Database containing your LOB data.
8. Have there been any improvements in the area of using touch interfaces on mobile devices?
SharePoint 2013 now provides the ability to create completely different looks(master pages) for the same site but for different platforms. These device channels, as they are called, provide the ability to have one look for browsers, one for tablets, and one for smartphones.
9. What changes will be made in Nintex for SharePoint 2013?
Nintex will be announcing their changes for SharePoint 2013 shortly. In the meantime, Nintex has provided a Platform Preview for SharePoint 2013 that utilizes the new SharePoint App Model.