We are migrating from sharepoint 2010 to sharepoint 2016. Content DB migration is completed. Now need to migrate the custom solution. Can you please provide the best approach to migrate custom master page? Or do i need to re-build it again?
Because the master page in SharePoint 2016 is completely different you have to create new master page (copy seattle.master for example) and apply your changes (CSS, HTML, placeholders...).
Related
I need to migrate a out of box SP2010 site to SP2016 site with 20 subsites. Could you please advise the best possible way to migrate it.
Backup and Restore the content DB from SP2010 --> SP2016 , since its an out of box site.
Perform manual migration of list,libraries,subsites using Export/Import commands and recreating in SP2016 site.
Using Sharegate tool to migrate
Looking forward to hear from you. Thanks.
Using Sharegate tool to migrate is something I can give my vote too
We have planned to migrate our SharePoint server 2010 to SharePoint Online (Office 365). Before we migrate our production site, we have tried to create a test environment in SharePoint server 2010 using the backup data of our production sites. We have tried the below steps to create a Staging environment as like our Production environment. Can anyone suggest the steps for migration or the steps we have followed is good.
Steps :
I have backup the content database.
Created a new web application and restored the backup database to this web application.
As the site is not loading and hence we created a new site
collection.
Once the new site collection is created, the site is able to load but the site and content of production site is not restored as like in our testing site.
Will restoring the database is enough to restore the site collection in the application in SharePoint or need to restore the site separately to the web application. Any suggested solution will be grateful for me to proceed.
Thank you and Best Regards,
Ragunaathan M P
If you are creating a test environment to use for SharePoint online your best bet is to use the 2016 bits. When you move your content over you need to do make sure you have upgraded the content.
So you would do some flavor of the following:
1) Backup the existing database
2) Restore the DB to the new farm
3) Mount the DB (Mount-SPContentDatabase xxx)
At this point (this is very overly simplified you should be able to render the sites.
Lots of other factors will be involved (InfoPath, Full Trust Code, Workflows, etc). However if your content is pretty vanilla this is what I would do. Dp not use the nob2bsiteupgrade option on mount or you will have an upgraded database schema, but your sites won't work.
To validate your upgrade check the logs and look at the versions table in the database. You should see a 16.x.x.x version. The other numbers are the upgrader actions and won't tell you much.
Here are some references:
Upgrade Content
Upgrade-SPContentDatabase
Mount-SPContentDatabase
If I have a requirement of displaying the a content on all the pages inside a header, Whats the best way to do that in an SharePoint 2013?
I am working on a master page that will be using the design manager and there is possibility of using the same master page in the SharePoint online too. The reason why I want to know what is the best way, when I use this same master page in SharePoint online I would like avoid redoing that entire coding for getting a dynamic data from the web service.
Several ways that I have been planning is below
- User control method
- Web part method, but requires server side coding which I doubt can used in online version
This is a complete dynamic data that will be retrieved by a web service and no internal SharePoint data be used.
Thanks for reading
Deepak
If its possible to consume web-service using jQuery/Ajax call you can go with that
Or else if you want to use c#, might need to go with provider hosted app feature (sharepoint 2013)
You can create a Visual Web Part for SharePoint 2013 Online.
Your web part will be contained in a Sandbox Solution which you will develop locally. Once development is complete you will upload the Solution Package created by Visual Studio to SharePoint Online.
https://sharepoint.stackexchange.com/questions/80164/create-visual-webpart-for-sharepoint-online
http://sharepoint-community.net/profiles/blogs/sharepoint-online-2013-web-part-deployment
I´m creating an application with SharePoint 2013/Visual Studio 2012. When I modify the aspx or ascx files, I need to deploy the whole application in order to view all changes and it will take almost one minute.
Is it possible to avoid the deployment when I change these ascx/aspx/js/css files?
No, deployment is only way how to propagate changes when using Visual Studio to develop SharePoint farm solutions.
But you can create JS/CSS/HTML pages using SharePoint Designer and when you will be done, import it to Visual Studio - SPD saves changes directly to SharePoint and you will see result imediatly...
I have seen many posts about people migrating Master Pages from 2007 to 2010 but I'm more interested in knowing more about problems faced at development level. I am planning to migration Master pages for publishing sites to SharePoint 2010.
Any help will be appreciated.
Your best option is probably to edit the 2010 master page to look like your custom master page rather than trying to modify the existing custom code - customisations tend to be simpler than the SharePoint page structure and easily pasted into the new master page.
How hard it will be depends on how closely your design matches the default SharePoint page structure - getting the ribbon to work within a fixed width layout takes far more work than it should.
There is MSDN article on this topic:
Upgrading an Existing Master Page to the SharePoint Foundation Master Page
http://msdn.microsoft.com/en-us/library/ee539981(office.14).aspx
If the master page that is to be updated was designed using the Microsoft supported customizations, then there should be no problem in upgrading the master page.