|Page 1||Page 2||Page 3||Page 4|
Q25: What’s new with Development in SharePoint 2013
Ans: Apart from the new App Model for Creating Custom Components, Microsoft has added a few new Namespaces to work with newly added – Social,Event Receivers,Delegate Controls,Callout Popups and other Custom Components in SharePoint 2013.In addition to these classes a few new templates in Visual Studio 2012 has also been added to Create better solutions.See the Complete Developer Samples at sharePoint 2013 Development samples
Q26: What’s the new App model?
Ans: SharePoint 2013 Introduces a Cloud App Model that enables you to Create apps.Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. An app may include SharePoint components such as lists, workflows, and site pages, but it can also surface a remote web application and remote data in SharePoint.To see how its different from Farm solution see the post SharePoint 2013 – Apps Vs Farm solutions
Q27: What kind of Apps Can Developed?
Ans: The Code for an app runs in different places, depending on where your app is hosted.They never run in the context of SharePoint Server, but they will run in the context of the browser or in the context of the hosted platform.You Can Develop three kind of Apps –
Provider-hosted and autohosted apps – In the cloud
Apps that have a mix of Components in SharePoint and in the cloud
Q28: What’s new with Visual WebPart in SharePoint 2013?
Ans: A new Visual WebPart Template has been added to Visual Studio 2012 for Creating Visual Webparts for SharePoint 2013. In this new Template both the User Control and WebPart Classes are merged to Create one template unlike SharePoint 2010 where you had a separate ascx and webpart file.Also, now you can Create both Sandbox and Farm solutions using Visual WebPart Template.
Q29: What’s the new TilesViewWebPart in SharePoint 2013?
Ans: SharePoint 2013 Introduces a new “Getting Started” WebPart that has “Tiles” to provide an easy access to some of the main links in the Site like – adding lists\libraries,Creating masterpage etc.To Programmatically Create this new WebPart a new abstract base class TilesViewWebPart has been added in SharePoint API.You have to Create a Custom Webpart and Inherit from TilesViewWebpart and Override GetTiles() to Create Custom tiles.
Q30: Can you Create & Deploy Sandbox Solutions in SharePoint 2013?
Ans: Sandbox Solutions are depreciated in SharePoint 2013.You can still Create them and deploy them but they are not supported by Microsoft (not 100% sure about this though).
Q31: Can we deploy Solutions Created in SharePoint 2010 in SharePoint 2013?
Ans: Yes. Most of the Solutions Should work fine but it is Recommended to Re-Create a Solution in Visual Studio 2012, Re-add all the features,Components and then deploy it to SharePoint 2013.
Q32: Why Would you Recommend Re-Creating Solutions?
Ans: SharePoint 2013 provides Support for both 14 Hive and 15 Hive.Both the directories are Created by default.So if you deploy a SharePoint 2010 Solution that refers to say _layouts folder, the reference will be made to 14 Hive and not 15 Hive by default. To make the solution refer to 15 Hive’s _layouts folder you need to Re-Create the Solution in Visual Studio 2012 and fix the _layouts reference to add ’15’ into it.
14 Hive – _/layouts/custompage.aspx
15 Hive – _/layouts/15/custompage.aspx
Notice the reference of 15 in _layouts folder reference.
Q33: How do you Force a Solution to be Deployed to 15 Hive and not 14 Hive?
Ans: If the solution was Created in Visual Studio 2010, you would add SharePointVersion=”15.0″ attribute in Solution’s manifest.xml file to force it to deploy in 15 Hive instead of 14 Hive.If the Solution however is Created in Visual Studio 2012, you don’t need to do anything, it gets deployed to 15 Hive by default.
Q34: How do you Deploy Solution to 14 hive or 15 Hive without modifying Solution.
Ans: In SharePoint 2013 with the new “CompatabilityLevel” parameter of Install-SPSolution cmdlet you can now Deploy your wsp Solutions to 14 hive, 15 hive or both.
Q35: Can you Deploy Master Page and Custom Css from SharePoint 2010 in SharePoint 2013?
Ans: Master Pages and Css has Changed a lot in SharePoint 2013.You can deploy a master page in Master page gallery but the styles from old core.css needs to be updated.
Q36: Can you use Fabulous 40 templates in SharePoint 2013?
Ans: As per MSDN, Microsoft is not Creating any New Versions of these Templates.The old Sites based on these templates Can be upgraded only if the Templates are Installed successfully in SharePoint 2013.You can try installing wsp of Fab 40 with CompatabilityLevel as 15 and upgrade the existing site collections.
Q37: Are there any Changes to Solutions deployed in \bin directory and GAC in SharePoint 2013?
Ans: You can no longer add partial trust Solution Packages to the \bin directory.Any files deployed to the \bin directory must be full trust. Any deployment scripts needs to be updated to make sure that they specify the correct trust level. After the release of .NET Framework 4.0, the GAC was split into two, one for each CLR.
c:\windows\assembly is the location for .NET versions 1.0 through 3.5 and c:\windows\microsoft.net\assembly is location for all the dlls for project Created in .NET Framework 4.0.
Q38: How are Sandbox Solution Migrated in SharePoint 2013?
Ans: Sandbox Solutions are upgraded with the Content databases.
Q39: How would you a Migrate a Site Collection in SharePoint 2013?
Ans: 1. Backup and Restore SharePoint 2010 Content database in your SharePoint 2013 farm.
2. Run Test-SPContentDatabase cmdlet to identify missing Components along with potential errors and related warnings. Check the upgrade log and deploy any missing components and re-run the cmdlet to verify.
3. Attach the Content database to the desired web application using Mount-SPContentDatabase cmdlet.
4. After successfully mounting the content database to web application, the site should be accessible in 14 mode.
5. Next, to Upgrade the site to 15 Hive, Navigate to SiteUpgrade.aspx page in Site Setting of your site collection.
6. Click on “Upgrade the Site Collection” button.
7. During the upgrade The SiteUpgrade.aspx page shows the progress and provides a link to an upgrade log for troubleshooting purposes.
8. Site Collection Should now be accessible in 15 mode.
|Page 1||Page 2||Page 3||Page 4|