code
Walkthroughs in the Windows Terminal Repository -
This seems like a useful technique to help code contributors without code maintainers having to commit time they haven’t got to designing the implementation of a feature.
#
I thought we had learned these lessons before, but maybe not!
never assume that colleagues won’t try to do something that they think should work , just because we haven’t told them that the feature is available (or not) 😄
time spent writing good automated tests is rarely wasted - they are your saviour when you revisit code that you last looked at months previously and try to understand what that “cowboy builder” (your past self) did exactly!
#
Background
In our business we operate a number of customer-facing web services which use an IdentityServer3 identity provider as the single source of identity. We have customised our setup to allow two sources of federated identity, and to pull certain claims from our CRM.
We have a new requirement to integrate a hosted instance of the excellent Discourse discussion forum, also using the same single source of identity.
Discourse does not support OpenId Connect, rather its own particular form of SSO.
#
Today was rebuilding a solution that had been updated to xunit2, and kept getting random test failures, usually with some kind of conflict with Rhino Mocks. The fix seemed to be to turn off the parallel testing. A little googling turned up this which suggests Rhino Mocks does indeed have a problem in a multi-threaded test environment
#
If you need to use ILMerge, you must use an unencrypted strong name key for your assembly
If you change the strong name key for your assembly, CRM thinks it’s a whole new assembly, so it might pay to create new ones explicitly
If you are now including the generated CRM early-bound classes through ILMerge instead of as a source include, remember to add [assembly: Microsoft.Xrm.Sdk.Client.ProxyTypesAssemblyAttribute()] to all deployed assemblies
#