*Words of Wisdom From The Elder

Listen To This Episode 

http://deepfriedbytes.com/podcast/episode-29-let-s-rumble-with-the-rails-rumble-champs/

In this episode we found the Rails Rumble 2008 Champion team while at the CodeMash 2.0.0.9 conference in Sandusky, OH.  We sat down with the Rails Rumble champs to discuss Ruby and their award winning site MeetInBetween.us.

We talked about Ruby, Rails, Gems, Why Ruby, C# and much more.

This is a short simple post that shows how to remove the auto attached messages generated by ESET Antivirus in Outlook.  This is a sample message that shows what gets attached.  Obviously this can be very annoying and junk up emails.

__________ Information from ESET NOD32 Antivirus, version of virus signature database 3952 (20090320) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com

The fix is simple.  First, select the ESET NOD32 Antivirus drop down in the Outlook toolbar and choose “scanner setup”.

On the setup page select the “Email Protection” option in the list on the left. Then set the two drop downs to “Never”.

Click OK. That should remove the messages from the body of your emails. 

IE8 was released yesterday during the Mix keynote yesterday.  I installed IE8 on my machine yesterday and rebooted late last night (yes I ignored the warning to reboot immediately all day).  When I came in this morning I had a fresh rebooted machine to start the day with.  I opened up IE8 and went to the first place I go usually, email.  Here’s what I saw:

For those that don’t know, this is the GMail interface.  For full disclosure, the GMail interface is not perfect.  I have had the user interface render weird things like this before.  As a matter of fact, a few weeks ago I had a messed up user interface for over a week before it corrected itself, and this was in Firefox, yet IE rendered correctly.  Given the history I pulled up Firefox to see if it  was rendering weird.  Here’s what it looked like.

Honestly I’m not sure what is going on, I’d be interested if anyone else is having the same issue with GMail not rendering correctly.  It could be a lab setting I have causing the problem or Google Gears. 

Not giving up too easily I decided to clear the history / cache / etc.

Then I restarted.

Same result.  I then pressed the ALT key to get to the tools menu and chose the option “Developer Tools”.

What happens when you do this is you get the developer tools for IE8.  This allows all sorts of things such as searching the DOM, profiling javascript and rendering, debugging and much more.  It is a very welcomed tool for developers I know.

If you can read the screen above, the browser mode is in IE8 compatibility view but the document mode is in IE7 standards.  The document mode has three options: 

I selected the IE8 standards option and my screen refreshed and the page was rendered like:

However, that change doesn’t “stick” for restarts.  It appears Google has some changes to make to GMail.  By the way, every other site I’ve been to works as expected. 

Listen To This Episode 

http://deepfriedbytes.com/podcast/episode-28-networking-silverlight/

In this episode we sat down with John Stockton, RIA Developer at Ascentium, at the Codemash 2009 conference.  We discussed a variety of things when networking Silverlight applications such as REST and WCF. 

This past week we were building some integration tests for a new feature we are adding into our framework.  In order to do the integration tests we needed to enable Service Broker on the SqlExpress database so SqlDependency could be used.

NOTE: Before you try to run this, be sure you are using the correct version as noted on MSDN.

Microsoft SQL Server 2005 Express Edition (SQL Server Express) database engine supports Service Broker only with a different edition of SQL Server 2005, such as Workgroup, Enterprise or Developer edition. Service Broker functionality is not supported between two editions of SQL Server Express.

The easiest way to enable ServiceBroker is connect to your database file and within the TSQL Editor run the following commands.

   1: alter database [C:\PATH\TO\DB.MDF] set NEW_BROKER

   2:  

   3: USE master;

   4:  

   5: ALTER DATABASE [C:\PATH\TO\DB.MDF] SET ENABLE_BROKER;

To see whether or not these commands work, run the following commands.  You should see that broker is enabled.

   1: USE master;

   2:  

   3: SELECT name, is_broker_enabled FROM sys.databases where name = 'C:\PATH\TO\DB.MDF'

DISCLAIMER: We have not finished running our tests yet to see if this works as we expected.  Stay tune for updates.