I have been trying to look into the versioning architecture for Microsoft Sharepoint. Does anyone know about the same?
The major versions of SharePoint are: SharePoint 2007, 2010, 2013, 2016, 2019, and SharePoint Online.
For detailed information, refer to following article:
https://en.wikipedia.org/wiki/SharePoint#Versions
Related
Is TFS 2015 is compatible with SharePoint 2016? Google search shows it is not compatible but didn't find any updated reference.
It's probably not compatible. The TFS integration with sharepoint is, at this point, more or less abandoned in favor of more flexible built-in dashboards, graphing, and reporting capabilities. You can still use Sharepoint for document management without having it explicitly integrated with an instance of TFS. I always recommend examining what you're using Sharepoint for in the context of TFS. I think you'll find that it's unnecessary to have it integrated.
In Dynamics CRM 2011 SDK the Xrm.Page Script Library template was at SDK\Templates\Xrm.PageScriptProjectTemplate location. But in CRM 2013 SDK no such location exists.
Also no such file campe up in folder search.
Do anybody have an idea about this?
I was the author of that template and chose to distribute it in the CRM SDK for CRM 2011. However, things got really busy and we just didn't have the bandwidth to maintain it. A third party solution: CRM Solution Manager (http://crmsolutionmanager.com) picked up the form scripting parts of it and added improvements along with many other useful capabilities. I would take a look at their solution if you found it helpful.
As far as I know the template has not been released for CRM 2013.
You can use the CRM 2011 one, but of course will not contains the new client methods introduced with CRM 2013.
I want to learn sharepoint, can someone give me a quick overview of the various core things to learn in sharepoint? Is it a single installation of a product or does it have various components to it that have to be installed separately?
Is there a book that you could recommend that would be the idea first book?
MSDN is great place with a lot of information about SharePoint development and Inside Microsoft SharePoint 2010.
If you plan to develop custom solution (programming) the good books are:
SharePoint 2010 as a Development Platform http://www.apress.com/9781430227069
Designing Solutions for Microsoft SharePoint 2010 http://msdn.microsoft.com/en-us/library/ff770300.aspx
And a good book about some SharePoint 2010 features - Real World SharePoint 2010 http://www.wrox.com/WileyCDA/WroxTitle/Real-World-SharePoint-2010-Indispensable-Experiences-from-22-MVPs.productCd-0470597135.html
Is there a best practice for versioning SharePoint features?
Our SharePoint product gets a release every 3-6 months, and we need a way of clearly differentiating between the new version and the old version. We also need to support simultaneous installations of the new and old feature so that clients may test the new stuff before deploying it.
Versioning Features is not supported in Sharepoint 2007. In Sharepoint 2010 you can Version Features like you normally would version assemblies.
See the following post for more details: Feature Versioning and Upgrades in SharePoint 2010
Here is a excellent webcast by Jeremy Thake on feature versiong and upgrade :
http://sharepointdevwiki.com/display/SPPodCasts/2010/06/22/SPWebCast+019+-+Deep+dive+into+feature+versioning+and+upgrade+support+in+SharePoint+2010
Check out chapters 8 and 9 of our free SharePoint development guidelines. We have been using this strategy successfully for the last few years in both SP2007 and SP2010.
I have used SharePoint's export/import tool in SharePoint 2007... Wasn't too thrilled with it. I am now having to do the same thing in SharePoint 2010. First off, just as a refresher, what all is migrated when using the export/import utility? And, is the export/import the same in SP 2010 as it was in SP 2007? If any issues have been seen with the SP2010 export/import utility, I would like to hear that as well. Thanks in advance.
From my experience Powershell export/import works much better in SharePoint 2010 than the stsadm versions did in 2007. However, I also know that export/import improved considerably over the full lifetime of the 2007 product and continued to receive updates up to at least SP2, maybe further with hotfixes and cummulative updates.
I haven't found much missing after experimenting with the flags when exporting then importing a list or a library. I haven't tried the moving sites as much, but I know it is improved over the release version of SharePoint 2007.