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
Related
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
I'm a bit confused about what I can use to develop for: It's a soup of letters: VBA, VSTO, Interop, etc... I'm in need in develop a MS Project 2013 control. So, what can I use to develop it? I prefer develop in C#, but if it isn't possible, I can develop VBA anyways...
Maybe I can help a little bit with the soup of letters. VBA is the oldest technology in your list. It is primarily used for scripting (automating) things in MS Project based on old visual basic operations on the MS Project object model. It typically works inside a specific MS Project file. VSTO is the modern version of VBA that Microsoft introduced to take advantage of .NET. It is still file-centric, but now you can use a modern object-oriented language like C# or VB.NET to write your control. A third approach is to write a separate .NET application that can work with any MS Project file. An example of this is the COM-Addin approach. A COM Addin is C# or VB.NET application that you compile and package separately. Then you register the Add In on the machine so that MS Project knows about it and calls it when needed.
Both VSTO and COM Addins are written in .NET, whereas MS Project only speaks COM. Thus both rely on the Microsoft COM-Interop libraries when they talk to MS Project. These libraries are called 'Primary Interop Assemblies' and they enable the translation between COM calls and .NET calls.
There's a comprehensive book on all of this by Andrew Whitechapel called Microsoft® .NET Development for Microsoft Office. It's no longer sold directly on Amazon, but you can still find it through other sellers. I've left out a few other related techniques that you can find in Andrew's book. Another expert is Rod Gill. He's written a book called VBA Programming for MS Project '98 through 2010 with an Introduction to VSTO. It's more VBA-centric than Andrew's book, but you may find it helpful. I'd recommend that you Google Andrew and Rod and also Misha Schneerson, formerly at Microsoft. Both Andrew and Misha have moved on to other technologies now, but you'll find that they give you good cookbooks for doing this sort of thing.
Hope this helps.
About a year ago I was working a CRM2011 customization project and found a website / blog that had 50+ development tools for CRM 2011. Sitemap editor was there, Ribbon Editor, VS plugins specifically for CRM tons of java & jquery tools like intellisense.
Some like the sitemap editor I remember the name but others not so much. I know this isn't specifically a programming question but I was hoping someone might know the blog or at least people can chime in with their tool(s) to help me build my toolbox back.
Thank You
I believe you're referring to the following site:
http://everythingcrm.net/2012/01/24/over-40-useful-dynamics-crm-2011-tools-utilities-scripts-controls/
You could also search in codeplex, there are tons of CRM tools available.
The CRM ToolBox is a good start
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.
I am new to developing for Office Forms Server / MOSS 2007. I have to choose between designing my web-based forms and writing code for them in Visual Studio Tools for Applications (aka VSTA) or Visual Studio Tools for Office (aka VSTO). VSTA is included free as part of the license for InfoPath 2007; VSTO, also free, requires Visual Studio 2005 / 2008. I have licenses for both of the products and cannot easily decide what the pros and cons of each IDE might be.
This explains it better than I can: http://blogs.msdn.com/andreww/archive/2006/02/21/536179.aspx
Given the fact that the license for VSTA comes with InfoPath, I'd probably run with that.
To add to Bennor's answer I would avoid writing code "behind" InfoPath forms entirely. This is a desperate attempt to make 'dumb XML' as much as possible instead of "smart" XML that is entangled with code. Failing this, my next choice is VSTA because historically these solutions (at least the ones I have written) have a lower security risk and can run on more diverse Office environments.
The last resort is to use VSTO. This is my bias... most of my VSTO investments are in Microsoft Word.