# Sunday, August 24, 2008

Final Cut!

Finally - bathroom is finished. Today was just installing the light fixture and patching a couple rough spots on the walls. As of tonight all the tools are back in the garage and everything's done! Couple thoughts...

1> When installing drywall, cut your openings smaller then req'd and then make them larger once the drywall is in place. Avoids patching later on when you're trying to finish things like electrical.

2> Tub surrounds rock. Way easier than tiling and actually look pretty classy once in place.

3> While it's good to focus on details, don't sweat them too much. We could have patched those drywall corners till the cows came home. Once they've been painted and the room is filled up they look outstanding. Better than most of the corners in our house.

 

#    Comments [1] |
# Sunday, August 10, 2008

Day 3

Got the vanity and shower finished today! All that's left is the ter-lette and we're done!!

#    Comments [4] |
# Wednesday, August 06, 2008

Day 2...

Tile's down. Good progress today.

#    Comments [0] |
# Saturday, July 26, 2008

Bathroom Progress

Despite ongoing concerns that our bathroom will never be done we made outstanding progress today. Finished painting; 4 coats because of the mold problem - 2 coats kilz sealer, then 2 coats kitchen and bathroom latex paint). Also finished installing a new subfloor for the tile (composite backer board called Easyboard instead of the 40 year old particle board). Starting to look good!

 

#    Comments [0] |

Work Note - Aristo F&I

Quick note that Aristo F&I went into pilot last wednesday!

#    Comments [0] |
# Monday, June 23, 2008

ASP.Net Web.Config Impersonation

I found something interesting on one of our test boxes today. Our generic web listener uses a web.config file to impersonate a user with enough security access to perform basic file i/o as well as some database stuff. This impersonation command is pretty simple. Here's our web.config below...

<configuration>

   <system.web>

      <authentication mode="Windows"/>

         <identity impersonate="true" userName=".\SomeUser" password="SomePassword" />

   </system.web>

</configuration>

Note how we use .\ to indicate what I thought was the current domain... it's not!

Turns out that .\ refers to the current computer... and if you're running on a domain controller it's no big deal - the domain controller is the current computer. However, on the 1% of servers we manager where our box is not the domain controller we need to manually add an extra user account to the local machine for this account. As long as this account has sufficient security our lister works like normal!

And it's amazing that there's no documentation on this .\ component anywhere on the web!

#    Comments [0] |
# Friday, June 20, 2008

Send-To with Vista

One of the tools I absolutely love in windows is the Send-To feature. Basically you can setup a list of programs which will show up whenever you right-click on a file and hover over the Send-To menu item.

I use this feature all the time as I developed a little ftp uploader which takes a file as a parameter and sends it to our corporate FTP site. Turns out in Vista they moved the location of this folder slightly. It's now in...

C:\Users\<username>\AppData\Roaming\Microsoft\Windows

I found this information on another developers blog. Good info!

http://geekswithblogs.net/dlussier/archive/2006/12/30/102366.aspx

#    Comments [0] |
# Saturday, May 24, 2008

Sourcegear Vault Issue

We recently began using the Sourcegear Vault Enhanced Client for Visual Studio. Intermittently we would receive errors accessing our Vault Server. Something to the effect of...

"The Vault server could not be contacted to perform the operation."

You'd try the operation a couple more times and eventually it would go through. After a bunch of digging I found a couple articles on the Sourcegear support forums that pointed me in the direction of the default proxy settings.

http://support.sourcegear.com/viewtopic.php?t=735

What was really interesting was that a> this happened usually when working offsite and b> it happened predominantly through the Visual Studio IDE Client... the normal Vault GUI was fine.

It turns out that this default proxy setting is stored in an app.config. When I compared the VaultGuiClient.exe.config with the devenv.exe.config (Program files\Microsoft VS 2008\Common7\IDE)  I found that the Vault GUI had specified to use the system proxy settings while Visual Studio had specified that no proxy existed.

Since changing the devenv.exe.config to match the vault gui config the issue appears to have disappeared. Here's what our new devenv config file looks like... note that the defaultProxy section is the important bit.

#    Comments [0] |
# Monday, April 14, 2008

The math behind Electronic Document Management

One of the key ideals behind Electronic Document Management is that it's supposed to save you money. The idea is that by eliminating some of the paper requirements you can cut down on supply and maintenance costs. It's one of those arguments that I've heard a number of times and to be honest I'd mostly ignored it.

My thought was that KNOWING you had electronic copies of each service order was well worth the investment and that the ongoing management and filing of these documents had such a time savings that the financial ramifications weren't as big a deal. Turns out I was wrong...

 

So here's the premise...

Each work order written inside of a Dealer Management System typically consists of 6 copies.

1 x Hard Copy approving the work.
1 x Technician Copy, so the tech's can note their work.
2 x Closing Copy, one for the customer, one for the dealership.
1 x Warranty Copy for the the manufacturer (if applicable).
1 x Accounting Copy, for the accounting system.


So, a store with 12 technicians doing 5 service orders per day would generate 360 documents per day.

12 techs x 5 service orders x 6 documents per service order = 360 documents


The same store, over the course of a year would generate almost 100,000 service documents.

360 documents per day x 5 days per week x 52 weeks per year = 93,600


Based on our experience each of these documents costs around 4 cents to print. When you take into account paper, toner, and printer wear and tear this adds up pretty quickly.

4 cents per document x 93,600 documents = $3,744 per year.


And these numbers are for an average sized shop!

I still believe that alot of the benefit behind electronic documents is the ability to better manage and store your information, but these kinds of figures do make a compelling financial argument.

#    Comments [0] |
# Thursday, February 28, 2008

You call that Snow!

Next time anyone complains about weather in Calgary I gotta forward this picture of a snow pile outside a Canadian Tire in Quebec... it was probably 50 feet high...

#    Comments [0] |