Archives

This came up in the newsgroups and is a common thing that people want so I thought I would share it here (as the newsgroupie was happy with my solution).

Since the dawn of the SharePoint 2003 man, views have been ways to filter information. Of course they're public views for everyone to see. But what if you want to have views just to show data filtered by a user (for security reasons). The first answer would be "Well Bil" (as I often refer to myself in the third person) "you could just have everyone in the company create personal views and they would be, well, personal". Uh yeah. Okay, two problems with this. First, while they are "personal" they're also "public" if you know the URL to get to them. There's no security on them whatsoever and security through obscurity just doesn't cut it. Second, having everyone in a company (unless you're a company of 10) isn't really feasible. We need a better way.

Enter the [Me] filter. Yup, plain old silly little [Me] that we see in the help files for creating views. Lets say you have a list of Sales results and for whatever reason (yes, I've seen this in organizations before) the powers that be don't want Sales Guy #1 (Joe) to see Sales Guy #327 (Ricardo) information. We have a list with various Sales figures but we have a cool thing called "Created By". This is the built in field that tags the item in the list with the name of the person who created it (makes sense doesn't it?). So now we can go into the default view and add a filter. Select the "Created By" field as the filter and enter [Me] as the value it has to equal. Voila, Abbacadabra, and Presto Chango. The view now only shows Joes sales figures to Joe and Ricardo's to Ricardo. Magic huh?

If you need an "admin" view then you can just create a personal view that doesn't have the filter and do something like group by the "Created By" field. Okay, so you're looking at your browser and saying "But Bil, you just told me that the personal view isn't personal and anyone can see it". Yes, well this is SharePoint and doesn't always provide the best solutions for everyone.

An alternative that you can do though to really hide this info is possible (hide as in your security guys won't be beating you upside the head if you create a personal view). Create a new document library and give whomever access you want to it. These would be the important people with Armani suits that want to see all of the sales figures just because it's part of their performance expectations for the year. Now create a new Web Part Page and put it in this library. On this Web Part Page drag the Sales list onto it. Crack the page open in FP2003 and convert the list to a DataView Web Part (oh yeah, you're getting it now right?). Now apply whatever filters you want to the list and save it. Since the Web Part page is in a Document Library, the security is applied to the library so Ricardo and Joe won't be able to see it but the big, powerful execs will. Problem solved (I hope).

Okay, the posts are probably going to be fast and furious (sans Vin Diesel) for the next month or so as we kick off the Visual Studio 2005 launch (and throw in the appropriate SharePoint info here and there). If you're still waiting for your MSDN download to complete (like I am) then you can check out the 2.0 Framework download here or the SDK download here. This is the final version stuff so get developing! No more betas, no more release candidates, no more what flavour of product x should I use with framework y?

Also if you haven't already signed up for the 2005 Visual Studio Launch Event I urge you to do so now. Seats are filling up across the country so some places are in waiting mode now. This is the biggest launch event in Microsoft's history and frankly, the products just kick ass (go ahead Eclipse and Java guys, slam me all you want). The main launch event page can be found here. Sweaty Steve Ballmer is going to be kicking it off in San Francisco on November 7th. I saw him at the MVP Summit as he gave the keynote there. Steve is an excellent presenter and really gets the crowd going.

As for the Canada launch, it kicks off November 8th in Toronto with lots of great stuff. I'll be working at the Calgary event at the Stampede on November 24th (and maybe head up to Edmonton for the launch there on the 15th) so come by and have some fun. We're going to be doing some cool stuff at the launch with the Cabana idea that started at TechEd. Basically an informal area where you can sit down, talk about VS2005, SQL Server 2005 or whatever (yes, SharePoint) and relax with some MVPs and Microsquishies. We'll have some whiteboards setup and be there to answer questions, talk about the new products, and whatever else strikes your fancy. It's going to be a blast.

Like I said, lots to post on the new products, on what's going on in SharePointLand (especially with 2.0 support now [well, except for SPS]) and other goodies going on. So stay tuned for some cool stuff.

Just found out that the release version of Visual Studio 2005 and various goodies are now available on MSDN Downloads. This includes Visual Studio 2005, Visio for Enterprise Architects (2005), and SQL 2005. These are the standard and professional editions of VS2005 but not the Visual Studio Team System line.

Gentlemen, start your engines!

Thanks for the IM AC!

EDIT: I managed to download SQL Server 2005 and Visio but couldn't get the IDE before both MSDN and the downloads turfed. According to Microsoft they are working on it but expect to get your download later with the other products coming online within a few days as well.

EDIT 2: DVD images are now online and the download site seems to be functioning again. Hope there's nobody on dial-up that's trying to get this stuff. Also watch for some cool announcements next week about VS2005 and what's going on in my corner of the world.

How much is a SharePoint blog worth to you? Based on some research by Tristan Louis on how much a blog is worth (based on linking, popularity, phases of the moon, whatever) Dane Carlson wrote a small applet that will calculate the value of your blog. Just input your blog's URL and it comes back with a value and a small snippet of HTML you can put on your site. Here's mine:

While it's completely silly and who knows what the calculation is based on, my blog showed up to be worth about $45k. Fitz came in at $44k so not sure if that's good or bad. Anyways just for kicks, I wasted 15 minutes of my life and here's the rundown on how much most of the SharePointHeads blogs are worth (in descending order of value, just so we can show up each other in our little circle of freakness).

So next time one of us spouts off perls of wisdom just remember that you're getting high priced information for free (based on this incredibly scientific system, can you feel the sarcasm dripping from your browser yet?). BTW, Scoble's blog (which some say is the mother of all blogs) comes in around $2.2 million for comparison.

My blog was getting lonely so I thought I would post a quick tip for people.

By default, when you create a new sub-area in SharePoint Portal Server (off the Home page) it will be a content area. From there you can create sub-areas and whatnot but what if you want the new area to use the News template? Or one of your own custom ones?

Navigate to your Portals home page

Click on Change Settings

Click on the Page tab

Change the Subarea Templates option to be able to use any template

Voila. Done. Now when you create a new subarea off the home page, it'll ask you what template you want to use for it. I don't know how many times I keep having to do this when I setup a new dev portal and how much frustration it brings me that I have to blow away my area, change the setting, then recreated it.

This Official SharePoint Portal Server Tip brought to you by the letter "P" and the number "42".

I don't often point my blog to other peoples but I thought this was relevant (and way overdue) and it was a Sunday afternoon and I'm not wearing any pants. Susan Bradley, our SBS Diva, has posted an excellent comparison of plain-jane WSS against Small Business Server (SBS) and it's use of WSS here. As with most Microsoft products coming out these days (VSTS, Navision, CRM, Project Server, etc.) they all use WSS for their document sharing and collaboration junk. SBS is no exception and Susan nails the differences between the two in a nice entry. This question comes up a lot and there seems to be a lot of bickering about WSS vs. WSS on SBS so hopefully this clears things up as they are really the same thing, just configured differently. No magic. No mirrors. Just options. Go read. Now.

Just a bunch of little things to update on where things are at here. First off, thanks for the excellent response to the beta request for SharePoint Builder (I really need to come up with a better name). It was overwhelming so I had to cut it off so please don't send in any more requests to be on the beta. We have a very large and very excellent group of people who are going to beat the crap out of it (including some softies, thanks guys!).

I have a few presentations planned over the next few months and into 2006 that I'll be showing at upcoming conferences. I have to put together a list but I'm pretty close to having something like a 6 month list of where I'll be and what I'll be presenting. Should be a fun, whirlwind tour of various places I haven't been. Lots of SharePoint stuff and talking to people and whatever other trouble we can get into.

Some people have emailed me about the missing "deep dive" posts I was so pumped up about. One of the problems with software that's in alpha or beta stage is that the creators, at any given point, may decide to drop features, change screens, etc. Something I was trying to avoid with the blog series was to show you something that might change in the future. The last thing anyone wants is someone quoting my blog from 6 months ago saying "Well Bil said it had this feature or that button" yet it isn't there in the final product. At this point, V3 is too young to be talking too much in depth about as things are changing, some things are completely missing in the UI, and others will eventually come with time. So I've put those aside for now and when the public beta comes out (sometime early in 2006 last time I heard) then I'll dust them off, update them with the current build and present them so you guys can work with them interactively with the product itself. Should be fun but to avoid the pain and suffering I'm just going to hold off on them and keep feeding you guys V2 stuff for now. Yeah, boring but hey, nobody said it was all glamour and glitz.

And for the love of all that is holy, someone tell me where I can get a copy of Stubbs the Zombie for the XBox in Calgary? It came out today but for whatever reason (that can only be pure torture for us zombie game freaks) we can't find it anywhere. EB Games says they'll be getting it in a week. A week! What's up with that?

Fast on the heels of the WSS SP2 release, Microsoft now brings you SPS SP2. In case you're confused about the letters, this is Service Pack 2 for SharePoint Portal Server. Yup, now you can have SP2 goodness with both WSS and Portal Server (remember kids, they are two different things). First off, here's the link so start your downloads.

The following Knowledge Base articles provide information about the various fixes included in this service pack.

Ted Teng, who's been contributing a lot to SharePoint (especially his MSD2D articles), is posting a short series on connecting SharePoint and SAP. I had the (mis)fortune of having to do this with a previous project I was on (can you tell I loathe SAP?) and while it's interesting, having to deal with SAP (at least in our environment) was just plain painful. Having no .NET developers on the SAP side of things didn't help as I just wanted to call a Web Service but unfortunately we had to interface to the BAPI calls and thus the whole .NET connector garbage is there. Ted's posts can be found here (Part I: Setup) and here (Part II: Defining the Proxy).

Anyways, just a couple of things to add on Ted's posts. His IT guy said in his first post "It would require no additional server components. Your .Net Applications would communicate directly to R/3 46C via RFC with the inclusion of a single Assembly DLL." In the immortal words of Albert Nimziki, "Uh... Mr. President. That's not entirely accurate." In addition to having to deploy the SAP.Connector.RFC.dll we also had to deploy the SAP.Connector.dll. This is the core of the connector when then proxies calls through the RFC protocol to SAP. I didn't see the SAP.Connector.dll mentioned in Ted's diagram so I thought I would mention it here. If you install the connector through the install program it doesn't show up because it's tossed in the GAC in your development environment but for deployment to a WSS server (where you don't want to install anything except WSS, trust me) you might miss it.

Also (our environment again) we needed to update the SERVICES file (found in %WINDIR%\system32\drivers\etc directory). This file contains alias' to the SAP system with the protocol to us. While you do set the name of the server you're connecting to in the Server Explorer and it can resolve via DNS no problem, internally the connector will use the SAP alias (or whatever the heck they call it) to make the actual RPC call. So if you get some odd error like "cannot find server sapdp00" in your exception, this might be the cause. Again, our environment so YMMV.

Doing it this way, I was able to include the SAP setup as part of our build so the other developers didn't need to install the connector or anything. They just copied three DLL files to the server and updated the SERVICES file (the LIBRFC32.DLL couldn't be deployed to the bin directory like the connector DLLs could so we had to copy it to %WINDIR%\system32 for everything to work). Oh yeah, one more thing. If your IT people in SAP land update the BAPI calls (in any way, even just recompiling them) then you'll need to regen your proxy classes. I separated them out in our solution and put them into an isolated service layer so we didn't have to deploy our entire solution when SAP changed. Hope that helps.

Despite having a title that just sets off bells in my simple brain, I have to first off say that SharePoint isn't content management anyways. Never was sold that way. That's what Content Management Server (CMS) is for. Okay, the next version of SharePoint will elevate to some kind of Enterprise level as it collides with CMS and provides some very cool content management features. All of this will come in due time of course, but to say that SharePoint isn't ready for Enteprise CM today is like saying it's not ready for high performance workflow transactions either (and can't run your latest XBox game for that matter).

The article goes on with a few points that are kind of like an alien autopsy where the patient is all blurry and unrecognizable and it's hard to tell if it really is an alien or not. You know, the show where they got Commander Riker to narrate it thinking that this would provide some level of credibility to an already cruddy video that looks like it was shot in the Star Wars Kids basement. Oh right, the article.

"Limited Database Scalability. The default database for SharePoint Services is the Microsoft Data Engine. Its storage capacity is limited to 4GB for all content managed on a given server instance. Go beyond this and you need SQL Server, which gets expensive."

Sigh. Yes, we all know the 4GB limitation on the database and it's pretty clear to most humans (at least those that take a minute to read the Administrators Guide) that you wouldn't use MSDE (or WSMDE which is what ships built-in with WSS) for anything other than development or a small team site. And SQL Server being expensive? I don't know about you, but the standard edition is about $800 USD (prices vary) which isn't that bad if you want to service a few thousand users (which you could on a single decent box, as in a $2000 desktop running it, I know, I've done it). If you have a company of 50 employees and you're not using SharePoint to store the universe, then 4GB is enough but I can't say I've ever seen a company that wouldn't lay out a couple of thousand dollars for hardware and software to serve up databases for the all it's employees applications. I don't see that as limited, but that might just be me. Yes, SQL Server can be expensive if you're talking about a multi-cluster box with hot swappable failover but then what isn't?

"Weak Searching and Navigation. It's difficult to find information spread across different workspaces."

Hmm. Search my name in Portal Server at the last company I was at and all documents and list items I authored or was mentioned in come up. If you're only talking about running Windows SharePoint Services, then yes, the cross site search is weak. Why is it weak? Because it isn't there. It's not a designed feature (although there are add-ons that you can get to do it). Okay, Portal Server isn't Google when it comes to searching (yet) but when a company the size of Microsoft shifts all of it's internal search projects to use SharePoint as the search engine, that says something. Again, I wouldn't call it weak but it depends on how you're looking at it.

"Lack of Security for Regulatory Compliance. There's no built-in means to apply security or manage the document lifecycle at the individual document level."

Agreed but again, it wasn't made for that. If SharePoint was pitched as "Your Enterprise needs for Regulatory Compliance in a box" and didn't deliver then you have every right to bitch and complain that it isn't there but stop asking a pig to fly. This all changes with vNext so stay tuned. I know that doesn't help today but there are products on the market (free as in beer) like the 80-20 compliance server and the SOX accelerator that make up for this.

"Software Licenses Costly. Windows SharePoint Services is usually free. However, organizations will most likely have to buy SharePoint Portal Server and SQL Server and, potentially, third-party records management software. Based on retail pricing, a typical SharePoint-based ECM environment will cost $270 to $320 per user to acquire."

Not sure what's meant by "Windows SharePoint Services is usually free". It's always free. Here's the download if you don't believe me. Yes, you need a Windows 2003 Server (and licenese and CALs to run it) but the software is free. As for Portal Server, I don't recommend people go out and buy it if they don't need it. For some reason, the community at large immediately thinks they need Portal Server and, more often than not, they don't. WSS usually is more than enough if you're doing something like departmental team sites or project sites. Also I don't know of any company that pays retail for Microsoft software. Either you have a Volume License agreement or something else where you pay an agreed amount. I don't of any company that pays retail unless you're two people and a small dog. The last company I was at had 7000 seats so licensing was pretty minimal as far as cost went (a users desktop which included Windows XP and CALs for servers [including SharePoint] ran about $50/user. When you get up in those numbers, cost is a bit of a wash compared to other software (take a look at Oracle's price gouging for example). Costly? Sure, if you're dumb enough to fire up a SQL cluster and a Portal Server for 10 people.

A lot of this just boils down to getting what you need and being smart about it. Too many times I hear the same kind of thing about SharePoint (or any other MS product) and how it fails at this and fails at that and is costly blah, blah, blah. When you have about a hundred employees, a couple thousand dollars isn't much for say a Windows Server, SQL, and a WSS site. With a couple of hundred users, Small Business Server is a good option and priced well (and based on WSS for it's document and collaboration features). With a few thousand users, another SQL Server and even Portal Server isn't that costly IMHO. And yes, I've lived and breathed these situations so I'm not just blowing wind out my butt (although I'm sure people will say otherwise in response to this post).

One more thing about cost, I just checked the Ferris page and they now have an entry on Oracle's Content Services and how's it's ECM ready. Of course it's by the same author as the SharePoint one, David Via. Wonder if he'll go on how amazingly cheap economical the Oracle solution is (not!). Of course when you factor in the Oracle database licenses (SQL Server), then there's the Oracle Portal product (SharePoint Portal Server), the BEPL process manager (BizTalk), the Oracle Collaboration Suite (WSS), and the other add-ons you need to get the full potential of it. Well, come back to me and we'll do cost comparison for the full stack and see who comes out on top.

So I don't know who get's paid at Ferris Research for their research, but I think they need to look at some research basics before diving into my territory again.

While we as mere mortals can't show you Office 12 screenshots or talk about functionality, if you're looking for the goods on Office 12 and the UI in particular I highly recommend you to check out Jensen Harris and his UI blog. He's the program manager for Office (or some part of it, I can never get the pecking order straight with softies) and an all-around nice guy. His presentations at the MVP Summit were great and he's been blogging quite regularily on the new UI features (as well as a great series of blogs on how the UI grew up to what it's becoming). So check out his blog here.

By now you've probably heard of Windows Workflow Foundation (WWF, what a 'nuther great Microsquishy acronym) which is the workflow engine to be embedded in the next version of SharePoint and the Office servers (which also means it'll be in Navision, CRM, Project Server, Team Server, SBS, SPS, and everything else that uses WSS under the covers). Follow me so far?

Anyways, I keep hearing from people a lot of confusion over BizTalk vs. WWF so I thought I would point you to Scott Woodgates blog on the subject as it clearly spells it out the best explaination about this (in case you need to explain it those that are still trying to get it).

In a nutshell:

Workflow within applications = Windows Workflow Foundation

Workflow across applications = BizTalk Server

Nice. Check out his entire blog entry here on the subject if you need more detail. Not directly SharePoint related, but just in case you need a quick elevator speech on the subject. Enjoy (and thanks to Scott for doing this as it much needed in many communities).

A new rounds of MVP awards is up and there's a lot of new ones and some old ones that have returned (like Angus even though we try to get rid of him, we love the little Aussie). Congrats to everyone who made it into our crazy and bizzare club. The recent MVP Summit made some great press with Microsoft and it explains what an MVP is and why we're here (as I tried to do horribly did a few posts ago) so check it out here and here.

Also shout outs to Heather Solomon, a long time SharePoint contributor, who joined the club this time round. Much deserved and we'll be seeing you under the table at the next Summit. Again, congrats to everyone. Here's to another great year of sharing and change!

Update: Here's a list of all the new SharePointHeads in MVP land (with links that I could find for their respective sites/blogs):

Chris Johnson has posted with what is probably the better mousetrap for recycle bin functionality in SharePoint. And you don't have to wait until V3 to get it. The guys in MS IT created yet another ISAPI filter that sits in front of the WSS one and intercepts any deletion requests and copies the to-be-deleted-file to a file share. Very slick. You can check out his post here and grab the source, scripts, etc. from the GotDotNet workspace setup for this tool here.

One thing to mention is that the filter will copy files to a file share so you could restore from that. My suggestion for anyone who has too much time on their hands (like us MVPs according to some people) is to have it post the file into another document library. That way you could have end users restore their own documents. With a simple event handler on that library (or a nightly task that runs a small command line app) you could purge the recycle bin library of any documents older than a set date (say 30 days). A little more work, but with a few changes you could get very close to a duplication of V3 and it's recycle bin capabilities (even going so far as to create two libraries, one for end users to restore from and one for admins to). Doesn't take up as much space as the "copy everything" concept and could be quite managable.

P.S. I should have known, but the response for getting in on the beta for my SharePoint Builder tool (what a lame name huh?) was overwhelming (120 requests so far!) so the beta is closed now. Thanks to everyone who's out there to help. You'll be hearing from my email soon.

We were talking at the MVP Summit and I mentioned there are two pet projects I want to get done by the end of this year. Today I'm revealing the first one which is a graphical editor for SharePoint Xml files (ONET.XML and SCHEMA.XML in particular). This is similar to something like NantPad which does the same thing for NAnt files. I got pretty fed up with editing the Xml files by hand (and even using something like XmlSpy is a pain, not to mention costly) and didn't see that changing for V3 (the Xml files have been reduced and are nicer to work with, but they're still there). So I wanted something better.

Features of the tool:

Client based editing so you can work offline

Publish to server and reset from inside the tool to see results immediately

Graphical editing of all nodes in ONET and SCHEMA

Validation of nodes so your output isn't screwed up

Context Menus so you can just add stuff without having to know all the Xml behind it

Ability to read in ONET and SCHEMA files from existing SharePoint sites for editing

Visible output of Xml as you build it

Ready for V3 as it understands both 2003 and v3 versions

Great Taste! Less Filling!

Email me if you want in on the beta (oh god, there goes my spam count). Looking for people to not only kick the tires but help shape the features and usability of it. Cheers!

The last four weeks has been interesting for me. Besides living out of suitcases, I've met dozens of interesting individuals at PDC and even more talented and diverse people at the MVP summit. All unique in their own right and with their varied perspectives, opinions, and thoughts on technology, architecture, and software design. With the general community at large, more often than not, most people don't know what this whole MVP thing is all about. Sure, there are a few paragraphs and the elevator speech dotted around on various websites but what do Most Valuable Professionals mean to you and why should you care? I mean, what's it all about?

Call us commnity leaders, technical champions, or simply ubergeeks. We, like yourself, have a strong passion for technology and a deep desire to share our knowledge with you. We get excited when we see a problem as we look at it as a challenge to solve. We are the builders, the dreamers, the listeners of change. Like the Microsoft campus itself, the technical community at a vast sea of knowledge and full of diversity. Like each building on the campus, the community itself is unique with each of its problems, ideas, and solutions. This is the very fabric that makes this multiverse an interesting place to work and breathe within. The attributes that make us stand apart in this world are those that eventually bring us all together.

In an effort to build on what Microsoft strives for (and to resonate with what Steve Ballmer said) we are people in the community and here, both as individuals and members are representatives and communicators of this balance between innovation and customer collaboration. We're not magicians and we're not soothsayers but we do position ourselves as a bridge between you and Microsoft. Most of us are employees or consultants who have to work with Microsoft technology each and every day. We have to live in the same world that you do so there is no Us vs. Them here. We're just human but that passion we share around technology is something we have in common and we want to strive towards making a better world where things just work.

It is this self-sustaining action itself that feeds and grows so not only do we, the MVPs, need these retreats with the Microsofties, but also to be messengers of your experiences and concerns. We emphasize with your pain when a technology doesn't work as advertised because we've gone through it too. We want to help drive the cahnges necessary to see the things we hold true and watch them evolve and grow over time. Without you and without Microsoft we cannot instigate this change. The three of us form a techno-eco-system, each depending on each other and feeding each other through experience to change. One voice yelling is strong but a whole chorus is much better so we are here to help form that chorus.

The information absorbed this past week during the summit isn't just another stack of white papers to add to. It is a powerful ball of knowledge that we are here to share with, grow around, and explore together which will come out in time as Microsoft reveals the bits and pieces of the pie. The Office 12 and vNext version of SharePoint release is almost a year off now and there is going to be thousands of blogs, screenshots, videos, articles, and books as the next evolution in collaboration forms. So leverage us. Remember us. Use us. We go off on our tangents and rants but in the end we're here to provide an outlet for you to share and for us to grow with it. Its going to be a long ride and I'm sure there will be bumps (there always are) but looking to the road ahead, it's going to be a great trip.

So that's it for another year and the Microsoft MVP Global Summit comes to a close. It was an excellent week, even if it was an exhaustive schedule. Getting to meet everyone face to face was nothing short of fabulous. It's sort of like a U.N. Meeting, but for geeks. I don't know how many times I laughed at silly jokes that nobody would get if they didn't boot up a laptop everyday or deal with an IT problem. There was a lot to take in so we'll be digesting this information for sometime now. I can imagine there are literally thousands of OneNote pages with scribbles on them from the weeks adventures which will eventually make their way into someones blogs someday. Even Gary Bushey was completely alert and awake as evidence from the picture below (with Brad explaining the synopsis of Serenity to us).

I have to tip my hat (okay, so I don't wear a hat but hey it's just an expression) to Microsoft for putting on the event for us. These kind of things are a monster of co-ordination and you could always find a 'softie standing around to help you or give you some directions or drop another t-shirt in your bag (okay, so there were some serious transportation issues but we'll ignore that for now). Also a tip of my hat (remember it's just an expression, no hat here) to the other MVPs who got to travel from all over. Some people had to travel for 20+ hours on planes (or some from Kirkland which is 5 miles away) but it was well worth it having everyone together. I'm sure each of the MVP groups are a little closer now after meeting up with each other and exchanging tales (at least I think this is true for the SharePoint ones but I can't speak for others).

I want to say goodbye and thanks to everyone I met up with if I didn't get a chance to do it in person. Also shout outs to the various MVPs I came across (in no particular order except what my brain can recall):

And of course our MVP lead April Dalke and the every popular propeller-head Fitz (my apologies for those I missed as I'm sure I missed a few). Live long and prosper (okay that was completely geek-ridden but cut me some slack as it's been a rough week). Here's to seeing you guys again soon.

I spent the afternoon of my last day in Seattle downtown taking some pics of the town and what it has to offer. It's a pretty city with a lot of interesting architecture and sites to see. As with many cities that you don't live in, there are odd type behaviours that stand out. The farmers market is one such thing in Seattle as they toss fresh fish (mmm... fresh fish) around and put on a show for the various hangers on. In any case, check out my pics on Flickr for some neat things I ran across. It seems each city offers something different and unique for visitors (even if the natives look at you like an idiot as you take pictures of things they see everyday).

As with everything, it's tough to say goodbye but, as they say, we'll always have Redmond.

It's Saturday morning as I enter this but the last few days have been an incredibly exhausting time. Our schedule on the campus starts around 5:30 when you get up, usually entails a half hour bus ride from the hotels and then various sessions. Yesterday was the most exhaustive of the schedule as our brains were saturated with presentation upon presentation. Again, a lot of stuff I've seen at PDC but the experience of having the product teams here and interacting with them makes drinking the Kool-Aid much more paletable.

The day was full of cool sessions and has got a lot of us thinking about what we'll be doing for the next year as we help you guys get up to speed on the new products, ease your migrations and pain points if you going from the current version to the new one, and generally look at doing what we do with our technology areas; push the envelope of what is possible. There's been a lot of inspiration this week, a lot of in-depth conversations with people, and a lot of new horizons to discover as we continue to integrate, innovate, and communicate our experiences and yours with the SharePoint technology stack and look at ways to really drive the creation of business solutions on the platform to the n-th degree.

After what seemed like a whirlwind day of sessions yesterday, we wound down with a trip to the Experience Music Project (EMP) and the Sci-Fi Museum (SFM) at the Space Needle last night. It was a pretty packed event but lots of interesting stuff to see. If you have a chance to check it out when you're in Seattle, give it a try. So it's off to breakfast now with the final sessions wrapping up today, saying goodbye to everyone and a BBQ to end the week. Here's to hoping the weather is good for us today.