What A Difference A Revision Makes - IConfigMapPath Is Inaccessible Due To Its Protection Level

A few people mentioned that they had the following compiler error when trying to compile HttpSimulator:

HttpSimulator.cs(722,38): error CS0122: ’System.Web.Configuration.IConfigMapPath’ is inaccessible due to its protection level

Well you’re not alone. Our build server is also having this same problem. Now before you curse me for releasing something that doesn’t even compile, I’d like to point out that it works on my machine.

Fortunately, we have our expert build problem solver, Simone Chiaretta, to look into it.

After a bit of snooping, he discovered that the reason that it builds on my machine is that I’m running Windows Vista with IIS 7.

The System.Web assembly on Vista is slightly newer than the one on Windows 2003/XP.

VISTA: v2.0.50727.312
Windows 2003/XP: v2.0.50727.210

So there you have it. Now you finally have a good reason to upgrade to Vista. HttpSimulator to the rescue! (Sorry, I know that punchline is getting old).

I’ll see if I can create a workaround for those of you (such as our build server) not running on Vista.

Comments

11 responses

Steve • June 20th, 2007
Funny, I was about to upgrade to Vista anyway. Just picked up a new WD raptor to start it this weekend!

Haacked • June 20th, 2007
Anyone know how to easily implement an internal interface?

Tomas Restrepo • June 20th, 2007
This actually hilights something I noticed a couple of months ago and still can't understand: why the heck is the vista build of .NET FX 2.0/3.0 different from the XP/2003 build at such fundamental levels? (for example mscorlib has extra types/methods not found in the other builds).

Steven Harman • June 20th, 2007
@Steve: (Not me... but the other Steve) I did the same thing when I made the jump to Vista - I went with a 74GB 10K rpm Raptor and I've got to say, it's pretty snappy!
I then have an internal 250GB 7.2K rpm SATAII drive & and an external 160GB 7.2K rpm SATAII drive for all non-OS stuff... like source code, documents, virtual machine images, installers, etc...

Zack • June 20th, 2007
Vista is the best... except UAC. That doesn't work so well when you're trying to use Visual Studio.

Jonas • June 22nd, 2007
HAACKED,
Don't you know that you ALWAYS have to add ALL your referenced assemblis to your source safe ?provider ?
And if you are (un)lucky you work in a place where these things are REALLY hard .. fill out 5 forms explaining why you need these additional dependencies.. What platforms will we support... XsX
Just create a brance named C$\HAACKED\COTS\MS\IIS7 ;)
Glad Midsommar!!
/Jonas Nilsson

Chris May • July 1st, 2007
Is there any fix for this to get it working on XP?

Haacked • July 4th, 2007
Not yet. Sorry.

Steven Burman • August 27th, 2007
Hi all,
I am getting this problem on my build server also. However, locally it works and I am running XP. The revision number for System.Web on my development machine is v2.0.50727.1378.
My build machine is running 2003 Server R2 and the revision for the System.Web.dll is v2.0.50727.42.
I am currently running the updates to see if this will perhaps sufficiently upgrade the revision of the dll so that the HttpSimulator can work. I will reply here with my findings.
<fingers crossed>
Steve.

Steven Burman • August 27th, 2007
Good news people.
Updating my build server (2003 Server R2) with the latest updates has updated the System.Web revision to be v2.0.50727.832. This appears to be sufficient to solve the IConfigMapPath inaccessibility issue.
In summary :
XP is working with v2.0.50727.1378
Windows Server 2003 R2 is working with v2.0.50727.832

ADITI N • September 23rd, 2007
Upgrade to .net framework 3.5. This updates system.web.