windows SP build - nsapi SDK?

[Paul Henson]

On 8/2/2022 2:13 AM, Rod Widdowson wrote:

> You might want to think about that version number - I'm not sure what
> you are doing but changing only the last digit will be a safer 
> option.

I must confess I hadn't really thought about the version number; this 
initial build was just a "figure out how to actually do it" on a 
checkout of the main git branch. Now that I've got it working, I applied 
a patch for a client to test that will hopefully fix an issue he is 
having running IIS on one box and the shibd process on another through 
an Azure load balancer that is making the persistent connections 
unhappy. I suppose it might be confusing that the test build I gave him 
had the same version number as the official production one 8-/ but I 
think he is sharp enough not to get them confused. I probably should 
change it next time I compile a test build though, thanks.

> I would also strongly suggest that you look at the executables and 
> Dlls that are installed to make sure they are what you expect them to
> be.  The version rules are quite simple but they are also subtle and
> quick to anger.

Hmm. what else would they be :)? The only versions of the dependencies 
and the SP are the ones it needed to compile, unless you mean random 
things like Microsoft library DLLs. In which case I'm probably one of 
these guys ;), I try not to get too deeply involved with the intricate 
internal details of Windows <sigh>.

https://previews.123rf.com/images/cgart/cgart1112/cgart111200017/11656159-three-monkeys.jpg

Thanks…

-- 
Signet - The Art of Access
https://www.signet.id/