+972 52-548-6969
Yet another internal issue
time to read 1 min | 100 words
I want to give a nice error message when windows integration is enabled. Now, WCF has this ability, and while it took me a while, I managed to track down the way they do it to this method:
HostedTransportConfigurationManager.MetabaseSettings.GetAuthenticationSchemes(base.HostedVirtualPath);
Which, of course, is internal.
Bad WCF, no cookie for you.
This is something really useful that I could make use of.
But, of course, Framework Design Guidelines says that you should make everything internal.
Argh!
Comments
I've had similar problems with Windows Forms a lot in the past, so I will readily admit that the BCL could benefit quite a bit from a more open approach to API design.
However, I don't recall that the Framework Design Guidelines state that you should make everything internal. I use the Framework Design Guidelines a lot when I do TDD, and have never experienced any conflicts.
Although the Framework Design Guidelines are very specific in certain details, IMO they are quite open for interpretation when it comes to higher-level design, such as designing for testability.
Sometimes, I think you blame the Framework Design Guidelines for more than there's evidence for...
Mark,
Allow me to rephrase that, I don't like the FDG as they are expressed in the design of all too many parts of the framework
As far as I can see, it's not so much the FDG that are too blame, but rather an (over-)emphasis on forward compatibility.
I guess that it's a side-effect of producing commercial software, but I agree that we could do better than history has shown.
Comment preview