Kindly provide all free Utilities/libraries details here so that we can make a one stop shop for users to find free utilities
Mine contribution
mixed authentication
SharePoint AJAX Toolkit for SharePoint 2010
Microsoft Patterns & Practices - SharePoint Guidance
SharePoint 2010
SharePoint 2010 Service Manager - Easily turn SharePoint services on/off on your dev box.
SharePoint Manager : A visual representation of the SharePoint object model that lets you interact with lists, webs, etc.
U2U CAML Query Builder for SharePoint 2003 and SharePoint 2007. Its a worth have for SharePoint geeks anyway!
All the tools and functionalities that are available within the essential CKS:DEV Visual Studio 2010 extension http://cksdev.codeplex.com/ are absolutely essential for anyone developing any code related solutions in SharePoint 2010.
I'm also a big fan of the Starter Master Pages http://startermasterpages.codeplex.com/ which helped me a lot when I had to create my first 2010 project.
For rapid virtual environment creation, I do like the scripts available within the Auto SharePoint Installer http://autospinstaller.codeplex.com/
Finally, don't forget that SharePoint Designer 2010 is free like it's little brother, and unlike the awful mess that was the previous edition, this new release is much more stable and less clumsy (It's still not something I would easily recommand but it helps to get some things done when you know what you are doing).
Related
As there is a drastic change in architecture from SharePoint 2010 to 2013, I would like to know what are the restrictions for a developer while developing Solutions/Apps for Office 365.
In SharePoint 2010, only sandbox solutions were allowed on Office 365, but in SharePoint 2013 the sandbox solutions are depreciated and App model is introduced. Would be glad if someone can throw some light on what is allowed and what is restricted on Office 365 in the new 2013 environment.
Sharepoint 2013 is a game changer, starting with the fact now is possible to use framework 4.5 and, since the new release of visual studio 2013, it's possible to use MVC. From a developing point of view you have to know there are two flavors:
Sharepoint hosted. In this case, your whole application is installed within the Microsoft servers. Because of this, you MUST use client object model and javascript. No server code at all. So you will configure your sites, libraries, lists, etc with 365 and then access this information using the Sharepoint javascripts libraries. If you are familiar with js ans sp js the you won't have any problem.
Autohosted. In this case you can choose between azure or your hosting (provider hosted) in both cases you can use a more traditional aproach, with your server code, classes, aspx and so on. The difference is when you deploy your application, in this case the app is installed just as a reference in 365 and all the code in your hosting provider. In fact all your application will be displayed in 365 within an iframe. Keep in mind you will be dealing with lots of cross domain scripting.
Last but not least, you have one final flavor, but it's not 365, Sharepoin onpremise, in this case this is your own sharepoint, you create, manager, develop or deploy whatever you want. This is very similar to the current sp2010 model, so, I guess you already now what you can do.
For more information:
http://msdn.microsoft.com/en-us/library/office/apps/fp179930.aspx
http://blogs.msdn.com/b/amigan/archive/2012/12/10/part-2-introduction-to-sharepoint-2013-app-model.aspx
I had a question: I wanted to begin programming in Sharepoint and I thought I could get some pointers in which of Sharepoint 2010 Foundation, Sharepoint 2010 Client... etc to download so I can learn to program for Sharepoint.
Thanks and Regards.
If you want to install Sharepoint 2010 foundation you should read this post:
https://msdn.microsoft.com/en-us/library/office/ee554869(v=office.14).aspx
It worked properly to me
First of all, I suggest you to create your own SharePoint trial site on O365, so that you don't have to install on Premises. Then, do video tutorials from which you can learn quickly. After you are comfortable, you can install SharePoint on Premises.
At this date you are probably better off with SharePoint 2013 but it doesn't really matter.
Install SharePoint 2010 foundation or 2013 foundation from WPI (Web Platform Installer). Also install Visual Studio from WPI if you dont already have it.
Use a Server Os, running SharePoint in Windows 7 is possible but I wouldn't recommend it for beginners. You must have a 64-bit enterprise or ultimate version of win 7 in such case. If you insist on win7 here is the official documentation on how to do this. http://msdn.microsoft.com/library/sharepoint/ee554869(v=office.14)
Youtube is your friend when it commes to how to startup with SharePoint development. Browse, Look, Read.
Good luck
If you would want to install SharePoint 2010, first install it in your virtual machine I would recommend to use first chapter of the book "Real World SharePoint 2010: Indispensable Experiences from 22 MVPs". It contains information about how to install SharePoint 2010.
Microsoft provides all related softwares like Windows Server, SharePoint Server, Sql Server free for trial purposes for a period of 180 days. The only thing where you have to invest is in a good hardware.
You may download evaluation version of sp2010 from here: http://www.microsoft.com/en-us/evalcenter/evaluate-sharepoint-server-2010
To create virtual machine you might want to download VMware Player which is a virtualization software package supplied free of charge by VMware, Inc.
If you don't want to spend time on installing SharePoint you may use something like cloudshare or microsofts own windows azure.
There are plenty of videos on YouTube on SharePoint which help you understand basics of SharePoint 2010 and to begin programming on SharePoint 2010.
Regards,
Hiren Gondhiya
Can Sharepoint apps be developed in a Visual Studio 2010 dev box only or does the dev box need to connect to a Sharepoint server? Can the Sharepoint Server be a stand alone machine (no domain controller between the two machines)?
The best practise for SharePoint development is to use a virtual server that contains the SharePoint install itself (and a copy of the portal you're working with), because assuming you are programming directly against the SP API, you will need to be executing your code on the machine that contains the Sharepoint installation itself.
You can program against SharePoint from a non-SharePoint machine through the use of the standard set of SharePoint web services provided, and you can of course create your own services (again sitting on the SP box/VM) to interrogate too. The catch to this approach is that you'll be dealing with return types that are primitive or XML based and you won't have the luxury of SP objects, for example SPUser, SPSite, etc, but for simple query operations at least this is not a bad approach.
IMHO, however, you've far greater flexbility programming against the API itself (Microsoft.Sharepoint.dll) so I'd advise you to get a VM going with all the necessary installs. Yes, it's a pain and time-consuming to set up, but well worth it.
As for Stand-alone options: SharePoint 2007 is not supported on anything non-server in terms of OS, so you'll need something like Server 2008 in order for it to work. SharePoint 2010, however, whilst claiming to only work on Server 2008, can actually work on Windows 7 (Pro and above) with a few hacks. You also have the benefit of 'sandbox' feature deployment in 2010, where you don't in 2007, meaning dev work is more cleanly isolated and less of a risk to a farm as a whole.
Good luck!
You can develop for SharePoint 2010 using VS 2010 using a stand alone setup - this is supported by Microsoft and very much recomended. Infact most of the tools built into VS2010 that will make your life significantly easier will only work with a local copy of SharePoint 2010.
MSDN - Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7...
Yes, if you have Windows 7 or Vista (you need WAS - Windows Activation Services). We have tried it but found that it was better to develop on a Windows 2008 with your own AD.
It will depend on what you are developing, for webparts you will not notice the difference. You will notice the difference when working on the security part og the app.
Sahil Maliks book has a whole chapter on the different options.
you can do sharepoint development by copying certain dlls to your local enviroment but to my understanding this is unsupported and the recommended practice is to use a virtual machine or development on the machine in which the service resides.
I want to obtain some work experience information about sharepoint server.Shall I install trail version of Sharepoint on my machine ?If trail version is allowed ,where is the point do i really need to start?
SharePoint 2007 requires Windows Server, but SharePoint 2010 can be installed on Windows Vista and 7.
In my opinion, these 2 books are excellent as starting point:
Inside WSS
Inside MOSS
You can use the free version of Sharepoint. This is Windows SharePoint Services 2007 or SharePoint Foundation 2010. If you are new to SharePoint then you would be better off using the new 2010 version. This is still in beta but should be released really soon.
As pointed out by Timores, you can install this on Win 7 or Vista but if you plan to do development for customers then you should use a server platform like 2008 R2.
Assuming you are a complete newbie to SharePoint, you should spend quite a lot of time learning the platform and architecture. There are many great books and web sites you can refer to.
After that, the sky is the limit. It really depends what you want to do with the platform.
MOSS 2007 / SharePoint Enterprise 2010 is a very large, very complex beast. If you feel happy/bored with WSS/Foundation then give the full product a try.
For me, it's taken 2 years to feel confident with SharePoint development. I fought the beast for a year but now we have arrived at a comfortable standoff. :)
I haven't touched sharepoint in years. If I want to setup a development environment to get up to speed, what options do I have? I don't have an MSDN license, is there anyway I can get up and running for free? (for development only)
You need a Windows 2003 Server (or 2008 Server, but I have no experience with that), no way around that. You can then of course use Visual C# 2005 Express and the SHarepoint Services 3.0 if that's your target.
If you want to do development on Sharepoint 2007, you have to buy a Sharepoint 2007 license, which has a pretty hefty fee attached to it.
As a SQL, SQL 2005 Express works fine for development.
There is a good Article how to set up Sharepoint on a Single Server:
http://blogs.msdn.com/martinkearn/archive/2007/03/28/how-to-install-sharepoint-server-2007-on-a-single-machine.aspx
You CAN use a Trial Version of Windows 2003 and Sharepoint 2007 though if it's only needed for a limited time (i believe the Trials run 180 days).
There is no way you can have a MOSS 2007/WSS 3.0 development for free but a Microsoft Action Pact is so cheap to get. :)
There is a nice blog to read to get the requirements and the steps to get a full MOSS 2007 image up and running here : How to Create a MOSS 2007 VPC Image: The Whole 9 Yards.
The action pack is fantastic value, you can use the Windows Server from that, as well as SharePoint Enterprise / Standard.
If you're just (re-)starting out in SharePoint development, there's a lot of value in just using WSS 3.0 and not (yet) using MOSS 2007. The basic vocabulary is going to be exactly the same at the development level, and you can accomplish a huge amount without ever feeling like you need MOSS to learn.
You could always download the Sharepoint trial VM here and then install the express version of visual studio.
You can download an Office SharePoint Server VHD from Microsoft. This allows you to run a virtual Windows Server & SharePoint Server on your personal machine using Virtual Server.
I recently went through this process and wrote a blog article describing how to setup a virtual Office SharePoint Server.