Joe Levi presents Greener Living through Technology

Every blog undergoes an evolution from when it’s conceived and initially published to and through its life span. I’ve tried to keep the topics of my blog relatively consistent over the years, and have tried to settle on one theme or another every couple months, hopefully these meet with your approval.

I recently decided to re-title my blog and tag line to be more in-line with what my topics generally cover, so, without further ado, here’s the change:

Joe Levi: Greener Living thru Technology

Brining technology, quality of life, geek humor, tech politics, self-defense, and environmental stewardship together.

What do you think?

I develop web solutions for a living, and often in my research and travels I come across tidbits that I find interesting and may want to refer back to later. I’ve considered using Del.icio.us and other online bookmark sites, but that puts my links in the hands of another company (and who know if they’re going to be around forever). Instead, taking a cue from Mike Dopp and others I’m going to be putting interesting links at the bottom of my posts — and on the days that I don’t have full-blown posts but still have interesting links, I’ll be creating a post just for those links.

What do you think?

Interesting Links:

• Lifetime Photos and Stories: Submit your story and photo (containing a Lifetime Product) and be entered to win more cool Lifetime Products.
• Mike Dopp’s Interesting Links of the Day.

While recompiling an ASP.NET 1.1 (legacy) application recently I was met with a series of errors that “System.Xml.XmlReader is inaccessible due to its protection level” (along with other System.Xml related messages). I couldn’t find a good answer to why I would be getting an error like this searching online, so I figured I’d share what I found in the hopes that I someone else having the same problems won’t have to dig as deep as I did.

Background: This is a legacy ASP.NET 1.1 solution that I need to support in a Virtual Machine development environment. We lost the VM that the solution was developed on but had a copy of the source code backed up. I created a new solution in Visual Studio.net 2003 and dropped all the files into the solution (including those in folders). When I tried to run the app I was met with 13 build errors regarding System.Xml inaccessibility.

Solution: Looking at the references I noticed that System.Xml was missing. Right-click References and click Add Reference. Find System.Xml.dll from the list, double-click it (to move it to the Selected Components) and click OK.

Even thought the .cs codebehind file had the appropriate “Using” statement, the reference to the corresponding .dll was required.

Hope it helps!