I was developing a large wrapper library for some classes from System.IO. I wanted to use the original documentation from mscorlib for my wrapper classes because the methods and properties only wrap the underlying components from System.IO. This is easily possible with the document include tag.
But there is a bug in the latest msbuild version which can drive you nuts if you don’t know what to look for.
I’m currently working porting a library into another open source project. As I have heavily extended the library my primary goal was to make it work and then compliant to the coding guidelines. A lot of my code contained in the library had automatically generated (with R#) interface implementations which contained blank lines between the curly braces. As you might know this is not StyleCop compliant. Wonderfully I was able to address the issues with the VS2010 Search + Replace dialog and tagged...
The planetgeek team wishes all our readers a happy year 2011 and all the best for all upcoming challenges! We also want to thank you for your loyalty and growing interest in our platform. Stay tuned for more interesting posts!
After eight years the skype communication protocol has been reverse engineered. See for yourself:
In this follow up post I try to tackle the more advanced stuff which is possible with the new ninject extension for Windows Workflow Foundation. The goal is to show the following topics:
Hooking into the injection chain
Possible side effects
Changing the extensions behavior
Download the extension
In my last post I raised the following questions:
How do you inject dependencies into activities without having to declare the dependencies as input arguments?
How do you build up extensions using DI mechanism?
How do you unit test components which host workflow applications or workflow invokers without actually invoking a real workflow?
In this follow up post I try to answer these questions.
Windows Workflow Foundation 4 offers a comprehensive set of tools to design, create and host your own workflows in your application. Normally when working with WF4 the only way to get your external dependencies into the workflow is by passing the dependencies as arguments to the workflow host such as WorkflowApplication, WorkflowInvoker or WorkflowServiceHost.
Are you tired of using the object property in MOQ?
Are you tired of declaring a huge amount of local variables to declare complex hierarchies?
…
Have a look at the new Mock.Of<T> feature in MOQ! Let’s see an example.
In a project I’m currently working we are using Windows Communication Foundation with automatically generated client proxies from interfaces in a shared library. This is the ideal approach for us because we are under control of the service provider and service consumer and when developing our stories for the application we can quickly introduce new service providers which then are automatically available at the client side. So far so good. But when using Windows Communication Foundation...
You can’t imagine how frustrated I was when I received my new dell business notebook with Core i7 (hyperthreading) when I tried to attach two external monitors to the docking station while running the laptop screen as third monitor… It’s just not possible! As a software developer it is really helpful to have three monitors. I usually have the following work setup when having three monitors (normally 20” with 1600×1200): First monitor (primary with taskbar): VS2010...