OdeToCode IC Logo

Three Things I Learned In Boston

Wednesday, October 20, 2004
  1. Navigating Boston with the aid of a speech enabled GPS device is about as useful as navigating Boston with the aid of a chatty 3 year old. “TURN LEFT”, the device says. Ok. Would that be the street 30° to the left or the street 60° degrees to the left? This happened more than once. Note to self: write down street names on next trip.
  2. I need to install Windows SharePoint Services and find out what all the hoopla is about. After hearing about SPS in the hallways and seeing it in a presentation, I want to learn more.
  3. It is possible to live on pizza, sushi, and diet coke for three days.

K Wednesday, October 20, 2004
WSS is alright. I wrote a Blog app using it. Make sure you stay away from the samples that do not use ASP.NET user controls in the web parts.
<br>Also, stay away from 900 stored procedures and 500 web pages with hard-coded IP addresses for testing purposes. :)
Andy Wednesday, October 20, 2004
Sharepoint is the world's biggest steaming pile of cr@p ever. It's great for demo's but it absolutely blows in real world enterprises. Want a maintenance nightmare, start using sharepoint.
Scott Allen Wednesday, October 20, 2004
K: Wow - where are the 900 sprocs and hard coded IPs? Are those in samples and examples people use? I definetly got the feeling there were some questionable practices going on in the WSS area.
<br>Andy: Thanks for the tip. I've sort of kept it off the radar screen until lately, but I have a feeling I need to at least touch and feel it a bit - before someone asks to put it in MY enterprise!
K Wednesday, October 20, 2004
No samples. Just some real world ASP history lessons.
<br>Understanding WSS is a good thing. Using it for real is not. Creating a setup and deployment package requires some workarounds in order to fully automate the process. I would say that it has a few more years to mature.
<br>Go Sox!!
Jeremy Brayton Wednesday, October 20, 2004
WSS != SPS. They're similar but very different from what I hear. I've only played with WSS on a test 2003 Server and it wasn't too bad. I didn't integrate Office 2003 to it, or use it in a real-world scenario but it seemed cool.
<br>If you can use what it comes with, you'll be fine. Most likely everyone's beef is with webparts and trying to make them function correctly. I've gotten a number of webparts from timheuer.com to work and some others aren't too bad either. I'm not trying to make WSS into everything under the sun either, so it functions in a way that is desirable by us.
<br>The greatest feature to me is versioning of Office documents. You can get that with ShadowCopy but it's not quite the same. That alone makes me want to use some of WSS if not everything I can. I'll be implementing it for our small 10 employee bitness soon enough, so I'd be glad to give some real world examples. Then again the word &quot;enterprise&quot; doesn't apply to us so maybe that's the real problem: scalability.
Comments are closed.