We build CMS's with ASP.NET using tools such as Umbraco and DotNetNuke etc
A client is asking us if we can build a site in WSS which I think is Windows Sharepoint Services.
Are there any experienced MOSS people out there who can tell me how hard we would find this?
Would it be just like learning another CMS?
Or will it be a nightmare?
Also, what software do we need to build the site in house for testing?
We don't have a MSDN subscription and use free Microsoft tools (Visual Studio Express and SQL Server Express)
Sharepoint is great for use with its own document management features, and it integrates well with Office products.
It's not such a good platform for development. The API is a nightmare, web parts are incomprehensible, and the database has a terrible structure (fields are named NumericField1, TextField2, etc. Yuck).
If you eventually need a web-facing server, MOSS is very expensive.
I will preface this by saying I am currently finally wrapping up a more-than-2 3-year project building one of the largest WCM sites deployed on MOSS in the world. We're talking thousands and thousands of content editors, nearly a million pages, millions of hits per day.
Depending on what you need, it could be moderately painful or extremely painful. MOSS is never a pleasure to use, so at the very least it will be an unpleasant exercise to deploy an out-of-the-box WCM site and make it look kinda like the design you want. However it should not be too terribly time-consuming or overly difficult.
If your needs look more like ours - do you need complex cross-loaded content on your pages? Content syndication and connected content? Flexible editor-controlled layouts? XHTML-compliant markup? Pixel-perfect design? If so, trying to use MOSS will absolutely be a nightmare.
Take note that WSS is not MOSS. WSS is the free version of SharePoint and MOSS is the paid version. MOSS is also the version designed for public facing CMS web sites.
With a bit of reading you should find MOSS relatively straight forward to develop a CMS site on top of. JP's link is a good one and I also recommend reading Andrew Connell's book Professional SharePoint 2007 Web Content Management Development: Building Publishing Sites with Office SharePoint Server 2007.
Depending on your requirements, in most cases you can work out-of-the-box with MOSS and SharePoint Designer. If you find you need more than what these can provide your learning curve will jump by quite a lot so tread carefully!
For development you will need at least a MOSS and SharePoint Designer license (as JP suggests MSDN is better and also gives you the option of using Visual Studio). Your client is going to need to fork out the licensing costs for MOSS. I think there are additional costs for public facing web sites but check with your Microsoft account manager.
See some cool stuff you can with public-facing web sites for the product at Top SharePoint.
It's not that hard. I don't find it as easy as DotNetNuke, but it's still fairly straight forward once you have some of the concepts down. There is a really great intro to CMS on MOSS at Web Content Management with SharePoint MOSS 2007. You are going to need least the lowest level subscription to MSDN because CMS is part of MOSS not WSS. Search around for deals on MSDN.
Actually if you are aware of the share point technology , then wont find it difficult to built CMS using it. Designing content management system using share point is actually possible.
Related
I am an experienced ASP.NET C# developer who is investigating using Sharepoint for document management for one of my clients. They want an intranet site with blogs and other stuff in addition but this will need to adhere to their brand guidelines.
Apart from the faff of setting up a working development environment to what extent do you get document management 'out of the box' with just using Windows Sharepoint Services? (the client understandably would rather not line Microsoft pockets further if possible)
Or put another way, how long would it take to add document management to an ASP.NET site?
Thanks
Oliver
WSS will give you all the document management capabilities that you need. If you pair it up with Search Server Express (which is also free), youget a complete solution for zero investment. We've even based a company portal of a major corporation on that. Doing it yourself in ASP.NET is a waste of time to say the least. The SharePoint platform gives you an enourmous value and the learning curve is actually not that tough
You definitely don't want to go and implement something like this yourself when a freely available (and powerful) solution like Windows SharePoint Services already exists. For most requirements I'd say the features in WSS are enough, but it really depends on what your client is looking for. For example you get:
Support for versions of documents
Exclusive check-out
Management of content types
Integration with Office applications
Meta-data
If you need to support records management scenarios, then you'd need features found in the SharePoint Server product. I'd start with WSS and see how far that gets you.
I would highly recommend looking at SharePoint Foundation 2010 over Windows SharePoint Services 3.0. It's the latest version of the basic SharePoint infrastructure (with the obligatory name change!).
SharePoint Foundation 2010 is a lot easier to work than WSS in terms of deployment, management and, especially, development. Plus there are new features in Foundation that you can start using.
Don't forget that SharePoint Designer 2010 is also free and is a great tool for customizing SharePoint.
Some links to get you going:
Download SharePoint Foundation 2010
Get Started Developing on SharePoint 2010
I went to the Microsoft Visual Studio 2010 launch event in Minneapolis yesterday and was slightly surprised by how much they were trotting out SharePoint and improved SharePoint development in Visual Studio 2010.
SharePoint is something I've largely ignored over the years as a web developer and solution architect on a small development team. I was always under the impression that SharePoint was used mostly for intranets in large corporations, and that if you were developing for SharePoint, it meant that a corporate decision had been made to use it and you as a developer probably had few (if any) options.
I realize this assumption is probably incorrect. So, what are the "cool" uses for SharePoint? What unique business problems have you solved using it? What could make a developer excited to be working on something for SharePoint?
Document libraries in a Microsoft environment. There are many nice out-of-the-box features for managing documents.
Intranet sites that have permissions setup in such a way to allow business entities to control use of the site within their group.
Project requirements lists. List in SharePoint can be customized to some degree without ever programming.
As a conclusion so far, SharePoint is a blessing and a curse. It has a lot of value-adds, though anything outside that box is difficult change, but there are indeed many 'hooks' to do just that. WSS3.0 is free for Windows Server 2003, as is SP 2010 Foundation for Server 2008, so you can get quite a bit out of that without upgrading to MOSS or 2010 equivalent.
It's probably best used in intranet/extranet scenario's, true. There's many public facing internet sites built on it as well, if you find that cool :)
See http://www.topsharepoint.com/ (I built one of the top-10 sites ;)
It's definately not the best web content management platform but it is not bad and companies like people who have learned to manage their intranet to be able to seamlessly do the same for the internet site.
Personally I find it "cool" that I can deliver functionality quickly and without building the world from scratch (I've built enough document management solutionettes and prefer not to do it ever again). But if I have to custom build there's many footholds for customization and all of the .NET platform is available. There's workflow solutions that allow business users to customize their own workflows and not bug me with them. I'm sure there's plenty of other solutions out there that can do something similar but the integration with Microsoft Office and the rest of the Microsoft world is quite good IMHO.
I don't understand the antagonism against SharePoint and find it's mostly fueled by ignorance and people trying to use the platform for something it wasn't meant to do (like being a relational database). You will have to learn it; it's not like adding ELMAH to your project, it's a really big layer in your architecture.
I want to use a CMS that can be accessed by my clients via the internet. All SharePoint usage I have seen is for intranet sites only. What I am looking to do:
Landing page for all clients, with general information.
Client login to client specific portal page with client specific information.
Accessible via the internet. The clients may or may not have SharePoint.
General and client specific wikis.
I won't be hosting this myself. I would be looking for a hosting provider as well.
I am also looking at using DotNetNuke, which has a lower cost of entry. I am open to suggestions of other CMSs, but my skills are built around C# and ASP.NET.
Before going down the SharePoint path, I wanted to make sure these things are possible.
Thanks!
Update:
Thanks to all that have given me some points to ponder. In summary, here is what I have decided to do (given my current skill set):
SharePoint can be used for my needs (my initial question). Many great example sites.
DotNetNuke as my CMS. I realize other good CMSs are available, but I prefer to stick to the Microsoft stack.
Branding will be easier in DotNetNuke.
The site will not be very big and not used by many. SharePoint will be overkill at this point.
Many of the 'modules' I am looking to use (wiki, forum, ...) seem to have more options/maturity using DotNetNuke.
Biggest Deciding Factor
Integrating a CMS solution with my software product and then installing/implementing this solution for individual clients will have a much larger cost with SharePoint. DotNetNuke will allow me to 'leave behind' the solution with the client without having them to invest heavily in SharePoint if they do not already own it.
Thanks to all!
Ed
Everything you require is supported by Windows SharePoint Services 3.0, which is included at no additional cost with a Windows Server license. However, SharePoint does have an administrative and development overhead that you could avoid using a different platform. It doesn't sound like you would really be leveraging any of SharePoint's particular strengths (document management, Office client integration, ad hoc collaboration sites, etc), so it's probably not worth the extra effort.
So in short, the answer to your question is "Yes", but it's probably not your best option with these specific requirements.
Check out the Top 17 case studies for Microsoft Office SharePoint Server 2007 and several new MOSS-based web sites. There are some nice Internet websites too.
there are heaps of SharePoint sites out there facing the internet. There’s a great list of over 1,000 of them on the WSS Demo site here: http://www.wssdemo.com/Pages/websites.aspx
All of the requirements you’ve listed are achievable with the externally facing SharePoint model. There’s an obvious cost impact of going down the SharePoint path versus DotNetNuke but it’s certainly achievable in terms of functionality.
Kentico offers SharePoint Connector which allows to publish SharePoint content to external sites: http://www.kentico.com/cms-asp-net-features/sharepoint.aspx
All the things you mentioned are possible. Note that hosting a SharePoint server can be expensive. Most hosting providers charge you a dedicated server hosting plan.
Also I'm not impressed with the default wiki solution in SharePoint. You might want to consider a 3th party wiki tool and point your SharePoint Search towards it so that the results are shown in your search results. Drawback is that you loose the security trimming.
You might also be interested in the BPOS solution. A (kind of) hosting service for SharePoint that Microsoft is offering.
Basically need to use SharePoint (because we promote MS yay!) as a content management system for an internet facing site.
How do I get rid of the default SharePoint look and feel and make it look like however I want it to?
I know the process involves creating a new masterpage with SharePoint Designer. However I prefer to code webpages rather than use a visual editor. Is this possible? Do I need knowledge of .NET?
Just check out ferrari.com for a very well made redesign of a SharePoint site.
Heather Solomon's Branding SharePoint series would be a good place to start. There's a lot you can do just with CSS, JS and HTML, but the most complete solutions (like Ferrari) require some pretty extensive customization with .NET and other SharePoint development techniques (features and delegate controls, in particular).
Your branding effort will be a lot easier if you only need to heavily brand the public-facing "publishing pages", from which you can remove most of the SharePoint-specific elements that make branding difficult.
Also, SharePoint Designer has a source view if you don't like the visual editor.
Yes it is possible to make it look like however you want it to (as you've seen from the Ferrari site). However to create that sort of site takes a lot of work.
Microsoft recommend the use of SharePoint Designer for 'designing' pages and layouts. However changing their behaviour almost always needs Visual Studio and development in .NET. You can largely avoid SharePoint Designer (which may worth considering as it can be a PITA) with an open source tool such as SPVisualDev. Use this with WSPBuilder for packaging your solutions (and avoid VSeWSS where possible).
Considering it sounds like you're just getting started, be aware this is a big topic with a reasonable learning curve. Read a good book on the topic such as Professional SharePoint 2007 Web Content Management Development: Building Publishing Sites with Office SharePoint Server 2007 by Andrew Connell. It takes you through most things you will encounter from the ground up.
I'm working my way through Real World Branding by Andrew Connell at the moment. It seems like a good demonstration, with code.
Plus the Heather Solomon articles as suggested by dahlbyk are always informative.
Just changing the theme, or creating a custom theme for the site, can go a long way towards making SharePoint look a lot better. It's also a lot less intensive then changing the master pages.
How to create a theme
How to deploy a theme
Example customization you can do with just CSS
Does the EULA allow you to disguise the fact that it's MS software?
Remember, you didn't buy the software, you're just paying for the privilege of using it.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have heard that Microsoft SharePoint was used by many companies. Could someone tell me briefly what is SharePoint and why is it popular?
What is SharePoint?
The latest version of Microsoft SharePoint software is really two different products:
Windows SharePoint Services is a free download for Windows Server. In the latest version, known as WSS v3, collaborative web sites templates include basic blog and wiki services along with list templates for Image Libraries, Document Libraries, Contact lists, Calendars, Tasks and much more.
Microsoft Office SharePoint Server 2007 or MOSS for short is built on Windows SharePoint Services. As a member of the Office Server product platform, it leverages the Microsoft Office client software to provide content on the web. Integration with Word, PowerPoint, Excel, Access and InfoPath provide rich web content from familiar content creation tools.
Why is it so popular
File Sharing
SharePoint originally became popular because it was an easy way to share documents on the web. Many organizations that adopted SharePoint in the 2003 versions capitalized on the ability to upload documents to Document Libaries and share those documents with others.
Company Extranets
One great example of this web based sharing, is a company extranet where users are not all in one location or authentication domain. Using form based authentication, accounts can be created for people across physical and company boundaries. By allowing one place for shared documents around a task rather than a corporate entity, SharePoint goes way beyond the common file share.
Content Management
There are plenty of other Content Management Systems, but MOSS incorporated the functionality of the previously name Microsoft Content Management System which itself often cost more than MOSS alone.
Search Search is greatly improved in SharePoint 2007 technologies. Search results are security trimmed, relevant and performant unlike the previous 2003 version. Bad search in SharePoint 2003 products lead to a lot of dissatisfaction with the product.
what is sharepoint
Sharepoint is really two different technologies: Windows Sharepoint Services (WSS) and Microsoft Office Sharepoint Server (MOSS). WSS is free and it comes with Windows Server 2003. MOSS isn't free.
WSS provides lots of out of the box functionality for managing documents and projects online. It manages documents in "document libraries." These are folders with permissions and different views of your documents. Projects, tasks, issues, or any tabular data, is managed in lists. Lists are similar to document libraries. They have permissions and views as well. It provides some simple search as well.
MOSS provides a better search (it's supposed to at least). It also has more publishing capabilities (WSS doesn't). And you have more control over page layouts. It's meant more for internet style sites while WSS is more for intranet sites.
and why is it popular?
WSS is popular partly because its free and partly because it just does so much out of the box. You can solve many common office requests with WSS. Stuff like issue trackers, project management and document management are trivial in WSS. That said, its a jack of all trades - good at many, master of none.
MOSS is probably less popular because its not free and having used it for a year, I don't see as much value in it as WSS. Search isn't that great. It does do a good job of creating a company directory.
I've been working with SharePoint since v.1 and I could tell you that SharePoint is a:
Document management server
Web content management server
Portal solution
Search engine
List-based repository
Collaboration site
Replacement for file shares
etc etc...
...but if I have to summarize in one sentence what SharePoint is I would say:
Sharepoint is Microsoft's Web OS.
That's real the secret of its success. Many people imagined the Web OS as something like these. A Web OS is not something that is meant to look like a desktop OS. A Web OS should be a WEB PLATFORM in which all sort of applications can be built on and users are able to collaborate with.
Think of SharePoint as the 2.0-era version of Windows :-)
Previous answers describe what sharepoint is, but don't do a good job describing why it's popular. Yes, it gives you all that neat doc-management stuff out of the box. Yes, it integrates tightly with Office.
The OOB features are 1/10th of the whole story. Sharepoint exposes a comprehensive .Net object model that lets you customize the thing to your hearts content. People are coding amazing things with MOSS 2007. With the object model, you can build and customize sites via code, in response to external events. You can write custom "web-parts" (controls hosted on special pages) that consume both internal (sharepoint) and external data.
Check out Sharepoint Blogs to see what people are doing with it.
Very good points so far but I'll try my best to add something. :)
SharePoint is not just 2 technologies. It is a set of products and technologies brought together by Microsoft into one immense product that comes in 2 flavors. The 2 flavors are Windows SharePoint Services (WSS) and Microsoft Office SharePoint Server (MOSS). MOSS does come in standard and enterprise.
[Some of the technologies used in SharePoint: Windows Workflow Foundation, ASP.NET, Web Parts, XML (included XPath, XSLT, etc), SQL, Web Services - to name a few I can think of off the top of my head]
No matter the version you choose, SharePoint allows for web-based capabilities to allow users to create, organize, distribute, and maintain information. Because of this, the most common uses for SharePoint sites are intranets and project/team sites.
SharePoint also has incredible possibilities as an application platform. Looking at the web part and workflow pieces alone you can begin to realize the potential. For example, automation of authorization processes within an organization can quickly be developed without any code using SharePoint Designer. (FYI: more complex workflows would require Visual Studio but many simple workflows can be designed using the point and click functionality of SharePoint Designer)
While MOSS only extends upon the WSS, it does add a large amount of functionality that can be very important and useful to a business. Some of the more important features available in MOSS and not in WSS are: records management, document retention and auditing policies, browser based forms (InfoPath forms without installing InfoPath on client machine), and some of the business intelligence capabilities. Amazingly we're seeing interest in the social networking features of MOSS too. (easy to read list of features not in WSS that MOSS has)
Why is SharePoint used? I was doing some research not to long ago on this exact subject and I found a research study that cited 5 key benefits:
Ease of information access
Streamlined internal communication
Increased end-user productivity
Optimized document management practices
IT time savings
Sorry if that turned into a bit of a ramble.
It's a collaboration website. All of the members on a team can update a single calendar and upload shared documents to a single repository.
I think in this case Wikipedia have it right
Windows SharePoint Services (WSS) is the basic part of Microsoft SharePoint, offering collaboration and document management functionality by means of web portals, by providing a centralized repository for shared documents, as well as browser-based management and administration of them. It allows creation of Document libraries, which are collections of files that can be shared for collaborative editing. SharePoint provides access control and revision control for documents in a library.
In a nutshell Sharepoint is all about corporative management and collaboration features. Your company have a Windows 2003 server? Here you go. WSS 3.0 is here up and running.
SharePoint is the reason I'm considering taking advantage of a suicide booth.
In all seriousness, the rest of the answers are spot on. The differences between WSS 3.0 and MOSS 2007 commonly trip people up ("why pay for MOSS when WSS is free?" for example). SharePoint is a very complex and rich product that is integrated into other Microsoft applications, like Project Server 2007 and Team Foundation Server.
Why should you care about it? It depends. There are quite a few opportunities out there for experienced SharePoint developers and administrators. It can very quickly become the singular focus of your career if you decide to put a lot of effort into learning it.
Microsoft Office Sharepoint Server (MOSS) is a combination of two previous products, Microsoft SharePoint and Microsoft Content Management System.
It has a large number of features out of the box that are very desirable for any single system, including hosting files with customisable metadata. Page and file publishing that is enabled for end users, excellent search... the list goes on.
Essentially it is designed to enhance and organisations collaboration activities across the entire enterprise, leveraging the organistations existing Office application to create an enterprise system.
Sharepoint, MS OFFICE proxy circa 2003...
remember when you emailed a copy of that word doc out to the whole company, that's what sharepoint is for, but apparently you missed the introductory gotomeeting training course.