Monday, September 29, 2008 #

“Web 2.0” – A Lame Marketing Term That Means Absolutely Nothing!

Technorati Tags:

I always love it when you get a cheesy executive/manager who really stretches & attempts to sound technical but fails badly by using the term “Web 2.0”.  First off, this term means absolutely nothing specific.  I once had a non-technical CIO tell me that “JavaScript based Web Services are what Web 2.0 is all about”.  Right then and there I knew he was really reaching for the stars to sound Savvy or technical, but in reality it really comes off pretty cheesy to a developer.

What does the number “2.0” have to do with the entire internet while the evolution of Internet is changing daily?  So when do we call it “Web 3.0”?  When do we call it “Web 4.0”.  What is “Web 2.0”?  Is it only AJAX?   You can’t version the entire internet and its daily evolution with a version number!  lame.

Just see for yourself, it really does not mean anything specific: http://en.wikipedia.org/wiki/Web_2.0

I guess if I could think of any logical reason if one existed as to why we are possibly still hearing this at the workplace, is that non-techies could us “Web 2.0” as their attempt to say “ANY new idea for the web”.  But again, I’m sorry to say that just because O’Reilly originally talked about this marketing term in some conference doesn’t mean we need to adopt it and label the entire Internet some versioned number!  That’s just ridiculous.

Comments?


posted @ Monday, September 29, 2008 2:36 AM | Feedback (6)  

Enterprise Library 3.1 Log Errors

Technorati Tags:

Today, I came across a couple of confusing errors while trying to re-setup logging again on a new PC and running my web application.  It was throwing an exception logging error for Enterprise Library in my Data Layer.

Error 1:

“Format of the initialization string does not conform to specification starting at index 45”

This is a pretty common error that simply pertains to an incorrect DB connection in your config file (web.config, etc.)

The problem on my end was that I had setup the DB connection string quite a while back for the web app using the Enterprise Library Config Tool.  Recently I copied over the code to a brand new machine and when trying to run this app, obviously, the connection string was no longer valid but I did not see that until I got this error in my EL exception handling code.

Error 2:

“Inaccessible logs: Security Error”

After fiddling around with the exception and logging blocks in the Enterprise Library Config tool a bit, I was not able to get the error to go away.  However what I do think fixed it was ultimately closing out VS 2008 and re-opening VS 2008 in Administrator mode on my Vista machine and as soon as I did that and re-built the website, that error went away.

Here’s the example code where it was throwing the error:

   1: catch (Exception ex)
   2: {
   3:     if (ExceptionPolicy.HandleException(ex, "Elbalazo.DataLayer.Exceptions"))
   4:     {
   5:         throw;
   6:     }
   7: }

posted @ Monday, September 29, 2008 2:02 AM | Feedback (1)