Nootn.com.au

Search This Blog

Contact

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

If you would like to get in touch for any purpose, you can either contact me on a social network:

...or use this form:

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Run PowerShell from .NET program without System.Management.Automation

I have run into the problem a couple of times where it's not "easy" to add a reference to System.Management.Automation in order to execute PowerShell scripts from .NET code. I found a way around it which works for simple scenarios where you might just want to execute some script and read the standard output plus error output.

Command Query Separation to better manage Async and Caching for Performance

I have done a fair bit of reading and experimenting with a concept people call "CQS" or "CQRS". For a good discussion about the possible difference see Greg Young's post . From here on in I am going to assume they are the same thing for simplicity. I am not going to do an in depth post about why you should or should not use this pattern/concept, I will only provide an overview. I am however going to show you one common application where I have found it brings great benefits using an ASP.NET MVC Web Application which relies heavily on server side caching of data and async controllers.

Code Coverage with OpenCover - example with NUnit (can run in TeamCity also)

I am a fan of code coverage as long as you aim for 100% coverage "of code that should be tested". I don't think you will get some of the benefits of code coverage if you just turn it on for all code and say "let's aim for 80%". A good code coverage tool should allow you to specify what to include or ignore by namespace, class name and even attributes (such as the "GeneratedCode" attribute). OpenCover is a nice code coverage tool as it meets these needs and it's Open Source. Later in this post I will go over how to set it up just using batch files to keep it nice and simple. I use code coverage to set myself goals so I know what I am aiming to test in a certain time period. For example, I could say "by the end of the week I want to have all my MVC Controllers tested" - so I add a filter to include the controllers in the code coverage report. So I use it as a way of " defining success " while writing tests. Keep i