Ben H Blog - Keep it Simple, Then Refactor.

I ran into an interesting issue this morning with one of the sites I’m working on.  I’m using Ajax and some JavaScript to do multiple things on my site.  We rolled the site out to production and started getting “Access Denied” JavaScript errors all over the site.  We were NOT getting these errors in test and I could not understand why.  I searched online to see if I could get any clues about how to fix this.  I found one article that discussed this error being related to security when working on window objects that are in two different domain (ie. trying to use “http://www.mydomain.com” and “http://mydomain.com” as config values on the same site).  So, the problem turned out to be that we were doing some domain forwarding and cloaking through zoneedit.com.  The cloaking displays “www.mydomain.com” in the address bar no matter what page you go to in the site.  Turning the cloaking off fixed the problem.  Cloaking is not a real high requirement for us so just turning that off is OK for us.  I’m not sure if there is a fix to get both the cloaking and the JavaScript to work.  Our site is working fine now so I’m not going to pursue it, but if someone finds the answer to that question please post that comment here for future reference.

This has nothing to do with .Net, but I thought there might be a bunch of people out there with Vonage that might be affected by this.

Vonage Patent Infringement

Many of you may have already seen this and fixed it.  I know that I had dealt with this once before, but I could not remember the fix.  So, I figured I’d blog it so if\when I come accross it again I can use this post as a reference to the workaround.  Here is the scenario:

We have been using the CTP version(s) of Ajax for many months now.  The RTM version was released and the validation controls were moved to a different release and were not included in the RTM version.  These controls that were left out caused the following error:

There is a great post here or here that explains this error in more detail, but I will give you the cliff notes version real quick.  This error is directly related to these Web.Config entries:

<tagMapping>

<add tagType="System.Web.UI.WebControls.CompareValidator" mappedTagType="System.Web.UI.Compatibility.CompareValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add tagType="System.Web.UI.WebControls.CustomValidator" mappedTagType="System.Web.UI.Compatibility.CustomValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add tagType="System.Web.UI.WebControls.RangeValidator" mappedTagType="System.Web.UI.Compatibility.RangeValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add tagType="System.Web.UI.WebControls.RegularExpressionValidator" mappedTagType="System.Web.UI.Compatibility.RegularExpressionValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add tagType="System.Web.UI.WebControls.RequiredFieldValidator" mappedTagType="System.Web.UI.Compatibility.RequiredFieldValidator, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add tagType="System.Web.UI.WebControls.ValidationSummary" mappedTagType="System.Web.UI.Compatibility.ValidationSummary, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</tagMapping>

If you are not using any of these controls then you can simply remove these entries.  They are located in the <pages> section in the Web.Config.  I would try this first and recompile to see if this fixes the issue.  If you are using the Validation controls then you will need to download this dll and reference it from your web project.  You will aslo need to change the Web.Config settings from above to look like this:

Just wanted to put a quick update out here to let everyone know my schedule for the next couple of months.  Below is a list of my upcoming speaking engagements:

April 3^rd: Launch Speaker at the Vista and Office 2007 Launch for the South Colorado .Net User Group

April 14^th: Simple Design Patterns That Solve Real World Development Issues at the Code Camp in Salt Lake City Utah

May 21^st: Simple Design Patterns That Solve Real World Development at the Denver .Net User’s Group

Please join me at these events to learn about .Net and have some fun as well.

Once you install Vista you start getting some annoying security messages when trying to remote from Vista to Servers or PCs that do not have the latest version of Remote Desktop.  I found a cool post on Scott Forsyth’s blog that discusses how to turn this off and the risks\rewards of doing so.  Check it out here.

I just upgraded to the 2.0 version of Blogjet to see if i can get it to connect to my blog correctly.  Here are a few test pictures: