Learning Sharepoint [closed] - sharepoint

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm starting a new job involving Sharepoint design/development. While the job will involve training courses on Sharepoint and other technologies I haven't used, I am interested to get a headstart and learn a little more about Sharepoint.
Are there any good articles explaining Sharepoint development and what I need to know (being a beginner in the technology)? I am strong with C# and ASP.NET as I use it everyday (job or no job), it's just the Sharepoint specific stuff I wonder. I am checking out MSDN. I did check out some other threads on this, but I am not really looking for a book.
A better question would be what blogs are there which focus on code snippets and best practises?
Thanks

There are lots of SharePoint virtual labs. They are good b/c they let you get your hands on the technology without too much of the setup hassle. :)

http://www.microsoft.com/click/SharePointDeveloper/html/Default.html
This site has the information I started with when learning SharePoint: webcasts from TechEd by Andrew Connell and Rob Bogue and the hands-on-labs that go along with them.
There are very many SharePoint MVPs that have blogs that are easy to find and many of them hang around on twitter so it's easy to get help.
http://andrewconnell.com/blog/archive/2008/11/25/Free-MSDN-Webcasts-amp-HOLs-for-MOSS-2007-WCM-Development.aspx has info on some newer webcasts
http://www.sharepointpodshow.com/ and http://www.methings.com/podcast/70342/MOSS-Gone-Wild.php
are 2 excellent SharePoint Podcasts.

A few months ago I was looking for decent SharePoint articles just to get an introduction to the technology. I found an entire section on CodeProject dedicated to it. Check it out if you haven't already, I found a number of good articles there.

Also, check out the SharePoint dev wiki

In addition to all the links provided by others:
Microsoft has a Best Practices Resource Center for SharePoint Server 2007 on Technet
The official SharePoint Team Blog has some good info.
Sharepoint Joel has a list of Top 100 SharePoint blogs, though a year old provides a good starting point of blogs to look at.
Several MSDN articles such as:
Disposal Best Practices
Common Coding Issues using the SharePoint Object Model
Edit: Also just noticed that the Patterns & Practices team has a SharePoint Guidance project on codeplex.

Sharepoint was a disaster for me (as I've said before), but I'd be willing to give it another try once .Net 4.0 and VS 2010 are released.
I would definitely download the VS 2010 beta and give the new Sharepoint integration a spin. I hear that it is a big improvement over what we have now.
As for documentation, msdn was the best learning resource I could find. It was more concise than what you will get with most books, although books usually provide a storyline and cohesive progression of learning.
Hope that helps, Good luck.

Codeplex is good for examples of developement. Given the rate of change with "best practices" I have seen some books that have become out of date quite rapidly.
I personally have gained a lot of valuable knowledge from looking at questions on forums like this one, trying to replicate the issue on a developement VM. I would recommend having a VM for "play" as hands on will run you up against many of the strengths and weaknesses with different approaches.
If you can get a backup of an existing content database you are using, having lots of documents and document libraries is good for hitting real data and trying out different search configurations etc.

One additional site you shouldn't forget is myrampup.com. It's a community-based training site which will help you get the knowledge you need to develop solutions on the SharePoint platform.

Before learning SharePoint development, learn what SharePoint can do. Use it and become familiar with its features. Many people's first thought is to develop new features when much of what they want to do can be done with existing SharePoint features. It's a huge, complex product.

I've found some very good videos for learning Sharepoint at Point8020

Very good reference for SharePoint Object Model:
http://www.etechplanet.com/post/2009/08/28/Overview-of-SharePoint-Object-Model.aspx

A good starting resource is the Microsoft RampUp Site it's a free resource that has 2 tracks for SharePoint for developers. Each track consists of articles, slide casts and virtual labs to help you gain an understanding of what goes into developing for SharePoint. They are not all inclusive but it should give you a good starting point.
There is also a user centric overview on the Microsoft Office Site for SharePoint 2007 that can help get you an understanding of some of the features in SharePoint.
I don't know if any of the resources have been update yet for SharePoint 2010, but hopefully those will follow soon.
Also check Microsoft Learning with SharePoint 2010 around the corner you might find free courses. Microsoft usually releases free online courseware for new products around the time of release.
For uo to date announcements check out the SharePoint Team blog, usually there's lots of good information around there.
Good Luck.

Related

Overview of Sharepoint 2010 and 2013 capabilities?

I'm looking for a page that provides a good, fairly basic and brief, end-user targeted overview of the capabilities of Sharepoint 2010, and another that does the same for Sharepoint 2013. I searched microsoft.com and couldn't really find much. Most of what I found was based on the assumption that the reader was familiar with Sharepoint already and was upgrading from an older version. I was hoping to find something for folks new to Sharepoint, checking it out for the very first time. Something kind of like a product info sheet that you'd see in a trade show booth, maybe.
Any pointers to something along these lines would be appreciated.
Background:
I work for a large university, and we offer Google Apps, Box, and Sharepoint (2010 now, 2013 soon) as options to support collaborative projects. I'm trying to help our user community understand the different capabilities of and optimal use cases for each tool. I've found good overview material for Box and Google Apps, but I'm getting stuck finding this for Sharepoint. And -- as luck would have it -- our users tend to be the least familiar with Sharepoint.
It's often hard to find decent information about SharePoint on the internet.. ;)
Maybe some of these links will help, but most probably you have already seen them all:
http://www.slideshare.net/pointbeyond/comparison-webinar3
http://sharepointpromag.com/blog/sharepoint-2010-vs-sharepoint-2013-small-step-or-big-jump
http://www.rharbridge.com/?page_id=966 [from a technical point of view]
http://www.fpweb.net/sharepoint-server-2013/features/end-user/
http://www.cmswire.com/cms/social-business/sharepoint-2013-social-features-highlights-019624.php
http://office.microsoft.com/en-001/sharepoint/sharepoint-2013-overview-collaboration-software-features-FX103789323.aspx [collaboration feature overview - and it's official! ;)]
JFYI: there are also a couple of frameworks and platforms available which improve the social capabilities, for example MatchPoint Snow is one I have heard of.
Update:
Ok, if you're willing to actually convince people to use SharePoint, try following query - I think there are some good results there (but maybe there also too tech-targeted): https://www.google.ch/#q=why%20should%20i%20use%20sharepoint
For example:
http://www.rackspace.com/knowledge_center/whitepaper/6-things-every-manager-should-know-about-microsoft-sharepoint
http://www.degdigital.com/blog/why-sharepoint-2013-considerations-for-your-platform-selection/
http://newsletter.stc-carolina.org/How+to+Encourage+Good+Use+of+SharePoint

Guidance on the most effective way to learn sharepoint

I am a .NET developer with a few years of experience in Winforms, WPF and some ASP.NET with C#. What would be the best way for me to go about learning sharepoint, as a developer? I would be Learning on my spare time, My work currently has nothing to do with sharepoint, but I have seen a bit of what sharepoint can do and I felt that It is a technology worth investing my time in.
I am interested In books, videos, possible training, webcasts, videos, blogs, forums, communities and any advice you may have.
I made a pretty detailed list here that I have accumulated over the past 5 years trying to learn SharePoint - I hope it helps:
Best way to learn SharePoint
I always receive the emails about SharePoint training. But it needs to pay $100+.
Here is the one.
http://elearning.left-brain.com/event/preparing-for-sharepoint-v15?code=EP3328D1
One of the ways to get started learning about SharePoint is to use Sharepoint Hands Labs. You can read about it here SharePoint 2010 Hands on Labs. Also interesting tutorials are Sharepoint Labs on Codeplex and
SharePoint Server Virtual Labs on MSDN.
Good luck!
I took the official Microsoft SharePoint 2010 developer course and that was very useful. Several different companies offer it but it isn't cheap. Also SharePoint 2010 Development with Visual Studio 2010 was a big help as well. Also find out if your city has a SharePoint user group in it. Mine does and it is a great way to network with other SharePoint users and developers.
Here are a couple resources that may help you get started.
http://msdn.microsoft.com/en-us/sp2010devtrainingcourse.aspx
http://msdn.microsoft.com/en-us/library/ee557253.aspx (Download for the examples is near the top)
And I would likely start with either a custom event receiver or a visual web part and just work on accessing data in a list.
http://msdn.microsoft.com/en-us/library/ff728093.aspx (Custom event receiver that prevents deletes on a list).
For books I like
Inside Microsoft SharePoint 2010
Professional SharePoint 2010 Development
Real World SharePoint 2010: Indispensable Experiences from 22 MVPs
Also as a first step you should install SharePoint and get a feel for it, once you do that look at SharePoint designer as it can accomplish a lot of tasks that users normally want.

Where to start learning SharePoint 2010?

I recently started at a new job where I'll be working with Sharepoint 2010 to set up (or actually upgrade) an intranet. Unfortunately, I have no experience with SP2010, and the last time I touched SP2007 (or a virtual server for that matter) was four years ago.
I'll be attending a course soon, but until then I have to make myself useful. I've already managed to install a working Sp2010 server and have played around with some web applications and site collections, and trying to find out how Sharepoint Designer works, but I don't really have an idea what I'm doing or what goals I should set for myself to actually learn useful stuff.
I've also watched some tutorials, but most are really problem-specific (problems I don't have yet) or dive into the code (which I won't, probably).
So.. where to start?
There are a lot of great training videos on Channel9.
Sahil Malik's book is organized as what are the basic things all SharePoint 2010 developers need to know. http://www.amazon.co.uk/Microsoft-SharePoint-2010-Solutions-Professionals/dp/1430228652/ref=sr_1_1?ie=UTF8&s=books&qid=1283973447&sr=8-1
It is a good place to start.
I would suggest video tutorials because:
They are FREE!
They give you more context than just reading what to do.
A quick search will get you specific topics.
Check out Bing videos on SharePoint 2010. There's lots of great content out there to get you going fast.
when i started with SP2010, i began by searching:
New features in Lists and Document
Libraries New search capabilities
DocumentSets (they are very interesting!)
Office Web Apps (Excel and Word web access)
A little bit of FAST Search Engine
Integration with silverlight
Changes in the object model
Workflows
New tools in VS2010
(MSDN, codeplex, codeproject, stackoverflow, and several blogs from Sharepoint MVPs are good places to look for)
I don't know if this would help but that's where I started.. if you need specific help you can find several groups in linkedin.. there are a lots of MVPs helping..
Good luck!
I would recommend you to check out the SharePoint guidance on codeplex. It comes with at sample portal application that is explained and with best practices and guidance for creating a SharePoint site. I am sure that this will provider vital information and knowledge for your project.
Kr., Bernd.
Follow the below link to learn sharepoint. It contains sharepoint tutorial videos and all.
http://www.fastsharepoint.com/
Basically i started my sharepoint learning with the following examples:
Create a feature to change site title
Create a feature to change site theme
Create a feature with feature stapling
Create a feature that activates another feature
Create a site through code
Create a list through code
Populate a list with data through code
Create a lookup column in list through code
These are the basic examples that you can understand what is Sharepoint as a beginner.
Please see the below link for more beginner programs:
http://blog.sharepointhosting.com/Downloads/SharePoint-Tutorials.aspx
Litso install a dev box on you machine and get started.
Try doing some migration from one server to the other.

Career in SharePoint? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I would like to learn SharePoint. Are there any jobs for SharePoint professionals in this recession time? I have .NET knowledge.
To say there is a demand for SharePoint would be an understatement. Because prior to 2007 SP developers were very few and far between, there are precious few people out there that as of now have enough SP experience to work on the really complex projects.
However, SharePoint is not going away, and will be growing even further with the release of MSSPS 2010 next year. If you're a good ASP.Net developer looking to find a niche, then SharePoint would be a good way to go.
My #1 tip for new SharePoint developers: Download the WSPBuilder Visual Studio add-on, and install it before you start any custom SharePoint work. By seeing how the add-on structures your projects and adds SharePoint capital-F Features to SP Solution Packages, it will make it a LOT easier for those concepts to click in your head.
My #2 tip: Inside Microsoft Windows SharePoint Services 3.0 - the best book, hands down, to really explain how SharePoint works, top to bottom. Read this cover to cover, and you'll know more than at least 30% of the SharePoint people out there.
I'd say two sites are worth checking:
MS SharePoint Developer: http://mssharepointdeveloper.com
My RampUp: http://myrampup.com/
These sites contain a lot of information on SharePoint development including the labs and a Virtual PC with SharePoint and Visual Studio.
SharePoint is Microsoft's fastest growing product. It's complex to administer and develop for, and SharePoint expertise gets a pretty nice premium (at least, in the three markets I'm familiar with: Dallas, Seattle, and central Midwest). I get a few calls a week from recruiters who want my SharePoint knowledge.
If you want to be a SharePoint developer, you will need to be familiar with .NET and either C# or VB.NET, so it looks like you're covered there.
The first thing you should do is spend some quality time reading the SharePoint questions here to see what kinds of issues SharePoint developers face. There are some excellent SharePoint folks on SO.
There is still plenty of SharePoint work around. However, most companies hiring SharePoint developers are looking for someone who is already an expert and will be able to help the existing .NET team learn SharePoint.
There is enough demand that you don't need a huge amount of experience to be considered an expert. However, you'll need at least some time on a real SharePoint project before you can get a job as a specialist. Your best option is probably to be working as a .NET developer for a company starting to use SharePoint or a consultancy that has both .NET and SharePoint projects.
You can go to job sites such as http://www.indeed.com/ to gauge the demand for different products/technologies in your area.
A few places I have worked customized SharePoint pretty extensively.
Personally I see quite a bit of SharePoint use locally. I have gotten a few head hunting calls about SharePoint jobs recently, so there does seem to be demand here.

Objective reasons for using a wiki tool over Sharepoint? [duplicate]

This question already has answers here:
Developer Documentation: Sharepoint Document Management vs. ScrewTurn Wiki [closed]
(11 answers)
Closed 7 years ago.
Duplicate
Developer Documentation: Sharepoint Document Management vs. ScrewTurn Wiki
I have been tasked with picking a wiki tool for a development organization, comprised of several different development teams. Sharepoint is installed and upper management would prefer this to be used, but in the past it has only used when PMs are forced to use it. None of the developers will update it with content that needs to be shared. I developed in Sharepoint and I liked it, so I have nothing against it. But for this to work I need something I can get everyone using, so Sharepoint will not work.
Step one is to convince management why Sharepoint will not work. We need the typical wiki features:
WYSIWYG, Clean interface, Easy to use, Attach Files to pages, Support for groups of users, Open source, Hosted Locally. (Maybe others I am not considering now?)
Can anyone provide a list of objective reasons why Sharepoint is not the solution we can use to take our first step?
There are many such products out there so step 2 should be easier.
SharePoint is the exact opposite of a wiki: A wiki is lightweight, easy to use, obvious, quick, doesn't get in the way.
To elaborate: A wiki allows your to jot down an idea quickly and moving details to the next page. In SP, people start to create processes, editing rights, workflows.
Wikis are designed to not get in the way. SP is designed to prevent you from doing "something bad"; whatever that might be. Wikis are driven by the idea that brainstorming works in open space while SP is driven by FUD: Who can see this information? Can it be used against me? How can I prevent someone to see/edit something?
Note: This is not a critique of SP per se; it's just how it used in most organizations. If you look at the security settings and edit rights, you sometimes feel like the workers of the company must all have been inmates in some high-profile prison (or should be).
I have absolutely no sharepoint-foo at all, but the sharepoint setup by IT at my employer has a wiki that we can use for documentation. Wouldn't that be good enough? Works ok-ish in firefox on mac, so I'm a happy camper.
SharePoint is best when using many of it's features (eg DM, WCM, workflow, collaberation etc) - you get a lot of it's benefits from the synergy of using all these things together with a common interface.
In any one area though, it's far from the 'best of breed' application - so, if you want a product for a specific job (eg a wiki), SharePoint isn't the most fully-featured/easy-to-use/delete-as-applicable product to be using - there will be products that do that (single) job far better.
You could also try looking at this question to see others experiences with SharePoint wiki's
I have used MediaWiki, Instiki and Sharepoint. Sharepoint does not work correctly with firefox on purpose. Its wiki functionality is an after thought. All kinds of additional features nobody use. But it does appeal to managers.
Instiki can be up and running in less than a minute and MediaWiki has everything you could need. Sharepoint annoyed most people on our team so nobody wanted to use it which meant a lot of knowledge was lost.
Which version of SharePoint are you using WSS 3.0/MOSS 2007 includes both wiki and blog functionality.
Although the SharePoint wiki isn't as feature-rich as most, the fact is that if your developers would not update a SharePoint wiki, chances are that they would not update any other kind, either.
I recommend creating a SharePoint wiki, and then actually reading the starting page, where it gives the definition of wikiwiki. I recommend only using a wiki (of any kind) for documents that can be written quickly, so that developers can get back to developing as soon as possible. Let the structure and accuracy grow over time. Just get the facts into the wiki quickly.
Wikis offer workflows, Document management and more too. I would disagree with those who say you can't do this in a wiki. Check out Confluence by Atlassian

Resources