Brain overloading... must release knowledge!

Lots of good stuff going on here. I'm winding down on a fairly intense SharePoint application development project (a Contract Management system). Still a month (or 6 you never can tell with these "agile" projects) left but things are working well. 100,000 lines of SharePoint configuration (lists, sitedefs, etc.) and 100,000 lines of C# code between 3 developers over 3 months. Not a bad effort. Out of which I have to say my SharePoint knowledge (and frustrations) have soared to new heights and I'm just full of stupid little SharePoint giblets that I'll be sharing over the next few weeks (OneNote is a great tool for capturing all  these little thoughts).

On the publishing front, I'm starting to write articles for the new SharePoint Advisor magazine. Still haven't figured out what my first one will be one (feel free to toss out some ideas if you're looking for something specific that you want me to dive into). I'm also putting together a proposal for a new book on SharePoint. I want to do something in the same flavour as the O'Reilly Cookbooks (Problem/Solution/Discussion) so I'm starting that now (again if you're just itching to get something in there now's your chance). We'll see how this goes and if I can keep up the pace of my 12+ hour days along with another 4-6 hours writing. Luckily I truly only sleep 3-4 hours a night. To bed around 10 or 11 and up at 2 or 3. Guess my body is just used to it that way (I would have used the term trained by my body is anything but trained).

Visual Studio Team Systems is rolling and I'm just getting past a few quirks in the Beta 2 stuff. A few things I would have really liked to see:

  • I would really like to just drag one project into the reference of another. It's such a pain sometimes to bring up the dialog to set references to projects that are in my solution. Maybe I'm just complaining because b2 keeps crashing on me with this.
  • Why can't we rename classes in the Class View? We can rename them in file form (which magically will rename the class) and we can rename the class in the Designer. So why not in Class View?

These are silly and nitpicky I know and for the most part are fine the way they work now. Just some things I thought would be nice to have.

And here you thought this was going to be a well informed, thought out, and highly knowledgeable post.

1 Comment

  • I'm currently just keeping the project I'm working on in check with VS2005 by sucking the project into it once in awhile. This is just to ensure that whatever we're doing in 2003 is going to port well (and for documentation purposes). I haven't got the WSS setup with ASP.NET 2.0 yet but probably will do that after we deliver the project initially to see what we need to when we do upgrade.

Comments have been disabled for this content.