.net connection pooling enforces good coding patterns
Yes it does. It punishes you for not following the recommended patterns. By breaking your applications.
This 4 year old discussion has finally become productive (after I joined it ).
Jokes aside, MS has finally come up with some convincing explanations backed by repro code. Not really a full explanation for behavior that I observed, but still very useful.
If only I got a penny every time I say to someone “I told you so”. But I never really say “I told you so” to anyone.