Tuesday, November 01, 2005

The title of Chapter 1, "Souls of the Borg", sets the mood for the authors' approach to their content--casual, sometimes pointed, and a little tongue-in-cheek in places.  This chapter is focused on how Microsoft has improved its corporate image by having so many of its employees blogging.  MS's only official site is Channel 9 (channel9.msdn.com), but there are a number of other sites as well (such as blogs.msdn.com).  It's great that Microsoft has helped its image, but that's only part of the story of what Microsoft's blogs bring to their ecosystem.  As a full time developer using Microsoft technologies, the various MS blogs have improved my development skills.  Sometimes it's little tips and tricks posted by members of the product team, or sometimes it a longer post waxing philosphic about design patterns and programming techniques.  In at least two cases, information I've found in the blogs regarding products in beta or release dates has directly influenced purchasing decisions and development plans.  There's a story to be told here, but not one I can tell just yet.  I have a brand new Dell 1850 in my living room, and a new 2850 on the way, as part of that story.  This is an important idea, that a company's blog is more than just a brand or image enhancer.  A good company can actually build a better ecosystem around itself with its open sharing of information.  The strength of the developer ecosystem will be as much a part of Microsoft's future success as its image.

The praise for Microsoft gets heaped on a little heavy in some places, and several pages circle around co-author Scoble's ascention to the Channel 9 team, but there are enough other stories in this chapter to make it very interesting.  Small businesses probably won't find too much to relate to in this chapter, but outfits like Enron, Worldcom and Tyco might want to take notice.  Pennies on the seafloor are less tarnished than those reputations, and a more human face might help those reputation and financial turnarounds.

Chapter 2, "Everything never changes", is really more of a history and a "what is blogging" overview.  Some of the data from a cited Pew study will be a year old by the time the book comes to press; at various points throughout the book, the authors cite how fast blogs are being created and being noticed, and Technorati is now tracking about 18 million blogs.  Hopefully there's time for a quick numbers update just before the book hits the presses.  I liked this chapter because it provides enough of answer to the question "What is a blog", which is the first question asked by anyone who needs to read this book.

Chapter 3, "Word of Mouth on Steroids", provides us with my favorite quote of the book (and is the title of this chapter).  The authors compare the cost effectiveness of blogging, and the phenominal rate of adoption of several Internet technologies (such as ICQ and Firefox) to bring home how powerful word of mouth can be, and how blogs play such a pivotal role in spreading the word.  We won't all rake in $287 MM from an initial $10,000, but the point should be taken by businesses large and small.  The quote comes from Yossi Vardi, the parental supervision of the ICQ creators.  In small businesses in small towns (which comprise a huge portion of the nation's economy), word of mouth makes or breaks you.  I'm looking forward the day we can start buzz about the flower shop on our blog; until then, we'll be slicing postcards apart.

Chapter 4 delves into how blogs allow normally isolated executives, such as GM's Bob Lutz or Marc Cuban, directly access their customer/fan base, and how the customer/fan base can access them right back.  The authors repeatedly state that one essential component of a blog is the ability to leave comments, and this emphasized in the two-way interactions covered in this chapter.  The CEO's voice can really soften the image of even the largest automaker in the world; in small businesses, so much of the business is built on the reputation of the owner.  A blog in this case serves as a great way for people who don't know you to rapidly get a feel for who you are, what you're about, and that that want to do business with you.

Chapter 5 gets into territory I find very interesting, and that's how small businesses ("Little Companies", as the chaper's title states) benefit from blogging.  A tailor, a church, a restaurant, a dairy and a gadget geek are some of the businesses profiled here (although the dairy has grown to become a very large business).  Some very useful tips for the small business blogger are presented at the end.  Sadly, this is really it for the discussion on how small businesses can benefit from blogging--I was personally hoping for more because I want my fellow small business owners to be as jazzed about blogs as I am.  Parts of the following chapters (except Chapter 6) focus on blogging in the context of large businesses such as Microsoft or GM.  Some of the subsequent information is useful for small businesses, but it's never put into the context of a small business, and may be overlooked or lost.  I'll have to put some of that content on this site so I don't have to explain it a thousand times.

Consultant blogging is the topic of Chapter 6.  It's here we meet Ernie the Attorney, whose fate after Hurricane Katrina was unknown for a short time, and was covered on the author's blog during the crisis.  For consultants (and I've been in this position), blogs serve as a very cost effective way to market oneself and display your knowledge.  Sometimes, as is the case with several patent/IP lawyers who started blogging at nearly the same time, and began collaborating.  Today, the three are trusted colleagues, and the whole of their blog is greater than the sum of the parts.  It's important that you as a consultant can be contacted via your blog, and that you follow up with those who contact you (more foreshadowing of the server story).  If you're a consultant, you're usually advised to get to networking events, sponsor user group meetings, etc.  Add Chapter 6 to that list, and be sure to pass it along if you ever repeat the list.  I think this chapter is important enough that it could be offered as a stand-alone ebook for "consultants who don't get it", because it's all about the consultants who do get it, and the success "getting it" brings.

The obituary for the PR professional is premature at this time; however, the one can almost hear the bell tolling for the ones who don't take notice of, and embrace, blogs.  Much as Scoble lays out the criticism of Microsoft on his blog and in this book, Shel (I think Shel wrote this one) uses Chapter 7 to take his profession to task.  Interviews with PR mucky-mucks such as Richard Edelman (one who "gets it") provide a very interesting look at how the PR business will (or should) change in the next few years.  This has the same feel to me as when I was a research scientist in a lab in 1997, and someone figured you could make money selling stuff on the Internet ("our Internet" as we scientists thought in those days).  On the one hand, it was kind of exciting; on the other hand, many of us thought "well crap, there goes the purity of the thing".  And this is the message to the PR people from Shel--don't treat the blogosphere like it's simply another way to spew forth the same old press releases, because your obit is on the city editor's desk, just waiting...

"Blogs and National Cultures" is Chapter 8.  Interesting...very interesting.  We start out with what I thought is a "no duh" moment--the authors were surprised to find more blogs in Japan than China.  Well, China ain't exactly a free country; ask Google (or visit elgoog, which was originally one way to get around state censorship), or Yahoo or MSN.  The authors pick back up on this a little later in the chapter, but are careful not to ruffle any feathers.  We also meet prominant bloggers from France, Germany, Spain and Japan, and see how national culture has affected the adoption of blogging.  That's one reason why I love America so much--there's such a diversity of people here that practically anything will become at least somewhat popular here, and this chapter reminds me just how special our culture really is.

Chapter 9--"Thorns in the Roses".  No, not about the flower business--it's about the pitfalls of blogging, and there are some.  We look at how Howard Dean's campaign was more of an echo chamber than actual phenomenon, and why Saddam Hussein should not blog.  My second favorite quote of the book is the section title, "The Dull Should Not Blog".  This is one of the chapters that focuses on larger businesses, and gives the short shrift to "Little Companies", but if small biz owners can reflect on what's presented and apply it to their own situations, there is some useful information in this chapter.

Even though there are no official blogging rules, it is possible to blog incorrectly, and Chapter 10 shows us some examples.  If you like those "World's Dumbest Criminals" stories, you'll enjoy this chapter.  Hugh MacLeod of Gaping Void fame makes an appearance with his Lame Blog awards, and advice on what not to do.  There are stories of blog salvation in this chapter as well, which mean that even if you are lame in the beginning, you can overcome that.  Kind of like how after gradutaion that acne cleared up and you got your braces off and showed up at college really hot, and no one knew you were a total geek in high school.  Not that I have any experience in that (and no, I did not go to grad school for a second chance of overcoming lameness, thanks for asking).  Point is, it's possible to overcome initial lame-ness, and Chapter 11 ("Doing it Right") is all the stuff you should've done at the beginning, presented in a numbered list with commentary.  You will see changes to this blog as a direct result of the information in Chapter 11, starting with the title.  I'll explain the title and retire it as soon as I think of a better one.  I think some of the content focuses a little too much on Google results--again, I admit they're important, but they aren't the end all and be all of what will comprise your success as a business.

By now, we've all heard the stories of that guy who got canned from Google for blogging, or that girl who got canned from Yahoo for the same thing.  Turns out, the girl (Heather Armstrong) is the one who coined the term "dooced" for being fired for blogging.  Content she posted on her blog, www.dooce.com, is what got her canned.  Chapter 11 looks at "How Not to Get Dooced".  This is another one of those chapters that puts its content in the context of big business.  To be sure, there are liabilities on bith sides when employees blog and post something they shouldn't.  Although small businesses can't get fired per se, they can get themselves ostracized from their communities.  I referred to Butler as a "rusted out steel town" in an earlier post, and I was a little worried about doing so.  A lot of people will agree with me (I personally think Butler has a bright future, and that's why we own a business here), but some will take offense.  There is a lot of pride in this town--the Jeep was invented here, Pullman cars were made here, George Washington fought here, and the original "Night of the Living Dead" was filmed here (OK, actually 10 min south in Evans City, but if you don't know where Butler is, Evans City is probably just as meaningless).  Being too flippant can be bad for business.  Honesty is good, but even that should be metered out in small doses at times.  Your blog is not a private conversation among a few close friends, so be careful what you say--your company or your community could dooce you.

We saw more terror and natural disaster this past summer than I really wanted to in my entire life.  Much of the most poignant coverage of these events came from people actually there, experiencing them, and posting to their blogs.  We experienced these events through their eyes, rather than from a safe camera distance, and that's a huge change in how we'll perceive future events of the same ilk.  Even with smaller crises, blogs play an important role because of the speed at which information can be disseminated, and Chapter 13, "Blogging in a Crisis", has examples of how blogging did change the crisis, or how a crisis could have been avoided.  NASA, Kryponite, Intel and Six Apart are case studies.

What's coming down the road for us?  Chapter 14 has some ideas.  It's no understatement when I say my iPod is the device I waited my whole life for.  What's next is anyone's guess, but I bet I'll like some of it.  This chapter looks at RSS, podcasts, vcasts and tagging, and how the blogosphere is likely to be influenced by them all.

We wrap up with Chapter 15.  It's your typical feel-good-by-tying-it-all-together-in-6-pages chapter, but it still feels good to read it.  The authors feel we've moved into a "Conversational Era" of marketing because of blogging.  Marketing is no longer blasting images or sounds at you a zillion times a day, but may be moving toward more of a soft-sell approach, providing information you want, when you want it, and letting you make an informed decision.  Those who inform stand to gain, while those who don't, won't.

And now for my feel good wrap-up:  I'm still jazzed.  Blogs have great potential for small businesses, and I'm appointing myself as a blogging evangelist to the small business community.  I will be recommending this book to quite a few people, and providing follow-up commentary here to relate some of the big business leanings to small businesses.  I'll try not to be lame, but no guarantee about geeky.

Tuesday, November 01, 2005 10:22:59 PM (Eastern Standard Time, UTC-05:00)

Looks like this is as close as we're going to get to the Pittsburgh area for a while: http://centralpenn.web121.discountasp.net/home/CodeCamp/tabid/57/Default.aspx

Tuesday, November 01, 2005 6:51:30 PM (Eastern Standard Time, UTC-05:00)
 Monday, October 31, 2005

I just picked up my new letterhead, and it looks great.  Ed Lackman at Guideline Printing was incredibly helpful in selecting the papers and working with Lynn Capestrani at Advertising Concepts to get the colors and bleeds just right.  It's amazing the variety of papers available today, and how much technical information on each Ed has stashed in his head.  Lynn also designed the PowerPoint template I use (you can see that in my SAF 2005 presentation).  Lynn and Ed's expertise made the whole process incredibly easy--I just had to pick a few things I liked, and they handled the rest.  Painless.  If you need design and print services in or around Pittsburgh (well, anywhere for that matter--they're digital), I definately recommend both of them.

Everything features my logo (which you can see on my homepage at http://www.rjdudley.com).  The original logo concept was designed by Molly Masood, but she got swamped with other work, and so Lynn and I traded some work with one another to polish it off and get everything printed.  You can see the proofs below; the bright blue was toned down to a more navy-blue for the actual pressing.

Business Card Proof

Letterhead Proof

Envelope Proof

Monday, October 31, 2005 7:49:45 PM (Eastern Standard Time, UTC-05:00)
 Friday, October 28, 2005

Way cool, Eric!

This is the first in a series of articles showing how to integrate a Crystal Report Manager into DotNetNuke. This article will step through creating a private assembly using Visual Studio as the development environment and using the Data Access Layer in DNN.

Full article at http://aspalliance.com/733

Friday, October 28, 2005 3:34:34 PM (Eastern Standard Time, UTC-05:00)
 Thursday, October 27, 2005

I'm part owner of a flower shop in Butler, PA (The Bloomery, thanks for asking).  Butler is a rusted out steel town about 35 miles north of Pittsburgh, and about 15 miles north of the suburban sprawl.  We're having a holiday open house on November 6, and to promote the event, we're doing a postcard mailing.  We had 700 sheets of cardstock printed with postcards 4/page.  We then spent several hours cutting the cards apart.  We pared our mailing list down to about 2600 people based on proximity and purchases.  Mailing labels and return address labels had to be printed and applied, and stamps purchased and applied.  We're in for close to $1000 just in copies, stamps and labels, plus the hours and hours of our time.

By contrast, it would take me about 10 minutes to put the same information on our blog (at www.floristblogs.com), or about half an hour to get really artistic in the blog post.  Now, we're a long way away from 2600 people in this town reading blogs on a regular basis, let alone our shop's blog, but the time will come when we can really scale back the expense and effort it takes us to reach our customer base.  Cindy Closkey, one of the founders of Pittsburgh Bloggers, lives here in Butler and is doing her darndest to spread the word.

I hope the time is soon.  I want this week's evenings and 1 grand back.

Thursday, October 27, 2005 9:53:31 PM (Eastern Standard Time, UTC-05:00)
 Wednesday, October 26, 2005

I'm going to have to read this book twice.  "Naked Conversations" has me jazzed.  I'm probably supposed to be reading this book with a critical eye, but I find myself so interested in the content that I lose myself in it.  The writing style is casual and informative, and solid tips are worked in between the vignettes of bloggers.  So far, it's been part history lesson, part glimpse of the future, with a focus on the end result: relating to customers.  One aspect I really like about the book so far is the wide variety of people who are included.  Favorite quote so far: "Blogging is word of mouth on steroids."

One annoyance: page numbering restarts with every chapter.  I prefer not to have to refer to "page 10 of chapter 4", but rather "page 142".

I will definately be recommending several people add preorders of this book to their Christmas lists (consider this a personal recommendation for anyone reading this; there's a handy link below for your use).  And hey, my uncle's a master plumber in NH, so y'all may have your blogging plumber soon.

Wednesday, October 26, 2005 9:30:17 PM (Eastern Standard Time, UTC-05:00)

Developing Automated Tests Using NUnit and VB.NET
source: http://www.byte-vision.com/NUnitAndVBPrint.aspx

This article describes how to write unit tests in Visual Basic .NET using the market standard automated unit testing tool NUnit 2.0.

Wednesday, October 26, 2005 7:59:33 PM (Eastern Standard Time, UTC-05:00)

How to report off a flat XML file through a Visual Studio .NET application

source: http://support.businessobjects.com/library/kbase/articles/c2015522.asp?ref=devzone_net_howto

This short KB article has sample code that demonstrates how to trpoty off a flat XML file using Crystal Reports .NET.

Wednesday, October 26, 2005 7:58:19 PM (Eastern Standard Time, UTC-05:00)

There are several causes for this message, you should read all the information before trying any one of these solutions.

1) This is a known issue in some versions of Crystal Reports, and there is a hot fix at http://support.businessobjects.com/library/kbase/articles/c2012318.asp.

Note that although the article's metadata indicate this hotfix is for CR .NET, the body copy speaks only of CR 9.0.  As such, apply this hotfix with some trepidation.  On Win XP systems, you may want to make a retore point in case the hotfix messes up your installation.

2) On a Win 98 machine, exporting to HTML 3.2 or 4.0.  There is no known fix at this time.  http://support.businessobjects.com/library/kbase/articles/c2013300.asp

This error message seems to stem from problems in crqe.dll, which is the Crystal Reports Query Engine.  If you search the knowledgebase at support.businessonjects.com for crqe.dll, you'll find additional articles that aren't specific to this error message that may also help/

Crystal Reports .NET Programming
If you're new to Crystal Reports, or just to CR .NET, this is the book you need. Part how-to, part programming reference, lots of simple examples in both C# and VB.NET.

 

 

 

Wednesday, October 26, 2005 7:54:37 PM (Eastern Standard Time, UTC-05:00)
 Tuesday, October 25, 2005

Shel Israel and Robert Scoble's new book, "Naked Conversations" arrived today, looking like the bizarre love-child of the USAF's Project Blue Book reports and the exam books at Allegheny College.  Thankfully, they have a real cover aready designed. 

Separated at birth?  Decide for yourselves.

Tuesday, October 25, 2005 12:50:42 PM (Eastern Standard Time, UTC-05:00)
 Monday, October 24, 2005
The DotNetDoc made me do it!
 
Congratulations, Richard!
Your IQ score is 135

This number is based on a scientific formula that compares how many questions you answered correctly on the Classic IQ Test relative to others.

Your Intellectual Type is Facts Curator. This means you are highly intelligent and have picked up an impressive and unique collection of facts and figures over the years. You've got a remarkable vocabulary and exceptional math skills — which puts you in the same class as brainiacs like Bill Gates. And that's just some of what we know about you from your test results.

Not to pick nits, but the second sentence should start "You have a remarkable..."

Here's the link: The Classic IQ Test.  You'll have to create a free profile, but that's what GMail is for.

Monday, October 24, 2005 9:19:48 AM (Eastern Standard Time, UTC-05:00)
 Tuesday, October 04, 2005

Specifically, to optimize blog entries for search engines, MoreVisibilty advises its business clients using blogs on their site to focus on a very limited set of keywords in any blog updates. The main keywords should appear it the title of the blog entry, and the same keywords should also be mentioned one to three times in the blog entry itself, based on its length.

Read more at http://www.internetretailer.com/dailyNews.asp?id=16268.

Tuesday, October 04, 2005 7:54:37 PM (Eastern Standard Time, UTC-05:00)
 Monday, October 03, 2005

One of the best sources of content ideas are the statistics for your website.  If you run your own website, your host should have a statistics package that gives you summary information, or you can look in the raw log files.  What you want to find are the search engine referrals--the phrases people typed into the search engine that led them to your site.  You want to dig through these search phrases, and find ones that relate to your business.  By focusing a blog posting on these phrases, you'll draw people to that blog post when they search for these terms.  Make sure you link to specific products or categories on your site.

If you remember Chad and Bob talking about "search engine optimization", this is one part of doing that.  The idea is to put content on your site or blog that is interesting to potential customers, and that will be found in the search engines, hopefully turning searchers into customers.

Monday, October 03, 2005 9:23:58 PM (Eastern Standard Time, UTC-05:00)

In a previous post (http://aspadvice.com/blogs/rjdudley/archive/2005/05/21/2595.aspx), I showed one way to protect files from direct download by configuring IIS.  In a shared hosting environment, this usually isn't possible, so I'll show another way to protect these files.

First, a little review.  Out of the box, only certain file types are mapped to the ASP.NET ISAPI filter.  These include .aspx, .ascx, .ashx, etc.  If these pages are requested, IIS hands off processing to the ASP.NET filter.  Otherwise, IIS serves the file directly (or hands it off to another ISAPI, as necessary).  There are also a number of file types mapped to ASP.NET that are protected by the HttpForbiddenHandler.  This is an HTTP Handler that prevents direct download of files of the specified type.  If you examine the <httpHandler> section of your machine.config file, you'll see the list.

It would seem that simply adding a file extension to the <httpHandler> section and have the HttpForbiddenHandler prevent its download would be great, but unfortunately, you need to also configure IIS for any new extention you want handled, which is the problem in the first place.

However, there's a little trick we can use.  Let's say you have a file named "protected.pdf" which you wish to prevent direct download of.  You can rename this file to "protected.pdf.resources", and since the .resources extension is already forbidden, users will not be able to download this file directly even if they can guess the file name.  Try it and see.

When it comes time to allow users to download the file, you can use the System.Web.HttpResponse.WriteFile method to send the file to the user.  You may have to clear the response and add a content type to make this all work correctly, as shown:

strFileName = Server.MapPath("protected.pdf.resources")

strFileId = StrFileName.ToString.Replace(".resources", "")

With HttpContext.Current.Response

   .ClearContent()

   .ClearHeaders()

   .ContentType = "application/pdf"

   .AddHeader("Content-Disposition", "inline; filename=" & strFileId)

   .WriteFile(strFileName)

   .End()

End With

Monday, October 03, 2005 7:42:02 PM (Eastern Standard Time, UTC-05:00)