By Michael Sutton Writing Coded UI tests is usually pretty easy: using the right tool, you can simply record some UI interactions, and the tool will generate code which will replay your actions programmatically. Well, I was trying to do that for automating OzCode’s UI tests, but it wasn’t as easy as I expected. For
We have just released a fresh beta release, with tons of improvements! You can find the complete changelog here, and download the new version from our website. With this out of the way, let us tell you about the incredible news we have for our Visual Studio 2013 users: Simplify now works in Standard Mode!
By Michael Parshin The goal of this post is to give a short overview of common mistakes we, .NET devs, tend to make over and over again while debugging our beloved products, day in, day out. Debugging the whole system instead of using unit tests Reproduce, debug, fix, debug, fix, … start the whole system
By Amir Zuker The Task Parallel Library (TPL) was released officially along with .NET 4.0 and it’s the new way of implementing and consuming asynchronous work. This post assumes you have basic experience with the TPL already, if not you can read more about it here. In this post I will discuss the scenarios that
Our Chief Architect Alon Fliess, and CTO Pavel Yosifovich recently attended the MVP Summit in Redmond. They met up with Channel9’s Robert Green to talk about OzCode on the Visual Studio Toolbox Show. Here’s the video for your enjoyment!
While developing OzCode, we work with multiple class types that represent a parsed C# code file: objects that represent things such as if statements, while loops, assignment expressions, and so forth. As you can imagine, the class hierarchy of these objects is quite complex and large – Underneath the base type there are dozens of
<p>We here at OzCode Software are really big fans of the .NET open source community.</p> <p>From NuGet to NHibernate to NUnit, you can hardly do any serious .NET development work today without coming to rely on these great collaborations between people from different countries, working together to create quality software for the benefit of us
Recently, while fixing a few memory leaks, I was surprised at just how easy it is to unknowingly cause a serious memory leak by doing simple, mundane things in WPF. In this post, I will summarize the most common pitfalls to look out for. Be careful when binding to a regular property This is probably
While debugging deep class hierarchies in Visual Studio, I was often annoyed by having to constantly expand the “base” nodes to get to see the members I wanted to see. This happens because Visual Studio only shows fields and properties declared on the given type, and tucks all the members of the base classes under
By Tamir Dresher Visual Studio comes with a built-in Visual Tree Visualizer which is really useful, but in order to start using it you have to find a reference to the instance of the FrameworkElement (i.e. UserControl, Window etc.) that you want to visualize. Getting the reference to the desired FrameworkElement is especially hard if