Automate al the things…
The Visual Studio Team is in the process of switching the debugging engine (at least since VS 2013). Today I experienced a really scary behavior.
Here is a screenshot of the legacy engine and the new one – both failing to show me that the List<T> contains 75 items, but in different ways.
Junctions are really useful.
Pretty simple with the search and replace of Visual Studio using Regular Expressions:
Ok, this is kind of a rant post. I acknowledge that Microsoft is really really doing a good job at certain (developer) spots (ASP.NET, Visual Studio, IIS, SQL Server, …). But NOT at the browser developer tools – I’m listing my issues here, hoping the IE-Team will listen and make the world better for everybody.
I do component based development. Meaning I have 30+ repos, builds and each of them has 1-10 projects – The main library project, tests, samples and so on.
The new framework version is out. As with every new release it seems to me that the search indexes on Microsoft downloads have not been rebuilt yet. So I abuse this blog post and note the download links to myself…
Get the public key for the InternalsVisibleTo attribute from a string name key pair file:
I really like FxCop. But in a debugging session it can be useful to save time by temporarily disabling the code analysis. Sadly there is no *global switch* to turn it off and on again. So here is my approach: