Building SP from source on Windows with VS2010 missing Versions.props and Includes.props

[Martin Robinson]

Are you suggesting that a .Net NameValueCollection object such as Request.Headers can have items (keys) that are accessible using the collection("key") syntax, but that can't be iterated through using the foreach Key in .AllKeys mechanism? If so, then .Net collections are seriously broken! 

The attributes don't appear in the ServerVariables collection either.

Martin



-----Original Message-----
From: dev [mailto:dev-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: 09 June 2015 16:28
To: Shib Dev
Subject: Re: Building SP from source on Windows with VS2010 missing Versions.props and Includes.props

On 6/9/15, 3:22 PM, "Martin Robinson" <martin.robinson at dai.co.uk> wrote:



>This is precisely the reason why I was trying to get a debug build 
>working!

Well, you can spend all that time, but I don't think it's going to tell you much.

>Accessing the attributes using the Request.Headers("BBCChargeCode") 
>syntax is indeed how I will do this finally, but for the time being I 
>was just dumping out everything that I get in Request.Headers, and the 
>attributes aren't there.

That's fine, but did you verify that accessing it directly also doesn't work?

It's not the same thing. The collections don't always contain all the headers actually present in many APIs.

Failing that, I'd look at the ServerVariables collection, which isn't as robust, but would provide another data point.

Lastly, I'd consider something like whether or not you changed the attribute-map file but never restarted IIS.

-- Scott

--
To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net