I think that as a "general skill" for a .NET developer, familiarity with SharePoint isn't particularly important.
Developing with SharePoint has a long, moderately-steep learning curve and in my experience, what you learn isn't particularly transferable to other areas; it's only useful when you're actually working with SharePoint. I'm about 9 months into my first role as a SharePoint dev and I still feel like I'm barely scratching the surface of what I can "do" with SharePoint. I haven't used Visual Studio 2010's SharePoint integration yet (because I'm still stuck supporting MOSS and VS2008), but some of the online demos look pretty cool. It reminds me of the stage when ASP.NET development in Visual Studio was starting to improve with the built-in web server etc. in VS2005... ie. when they actually started seriously looking at improving the development experience. On Fri, Jun 11, 2010 at 10:47 AM, Arjang Assadi <[email protected]>wrote: > On 11 June 2010 09:43, David Connors <[email protected]> wrote: > > There is another list called OZMOSS for this sort of stuff (asking for > devs > > that is, not sledging Sharepoint :) > > So this must be the list for sledging Sharepoint! :) > On that note, does share point matter? ( i.e. from a .Net developer > point of view ). > > In VS2010 there are options for sharpoint dataSources, anyone uses > that or knows what it is about? > > Kind Regards > > Arjang >
