Kudos for JetBrains - TeamCity Notification

I have been used quite a few of source control systems and build systems, such as ClearCase, CVS, SubVersion, CruiseControl, GitHub, and Team Foundation Server.

TeamCity is a new one for me. But I always know JetBrains will always have some great products, just like ReSharper which is one of my core tool-set. TeamCity supports both Java and .NET software development teams and integrates with the most popular VCSs, IDEs and development frameworks to ensure a smooth and stable development workflow.

I am most impressed by how easy it is to setup and how many build notifications TeamCity supports. Kudos to JetBrains.

It supports Windows system tray notifications;

It also supports RSS so I can read from my RSS reader.

Demystify Roslyn

Today I watched the video of //build/ C# 5.0, VB 11, Visual studio 2011 New Features from Anders Hejlsberg - Windows Runtime support, Asychronous support, Call Information attributes, Roslyn project, Script engine etc.  Mostly interested to me is that it demystify what Roslyn can do. It is indeed very cool.

The foundation of this Roslyn is a new C# compiler, written in C# (and a new VB compiler written in VB too, see the VB Team blog for details). This compiler is written as a library that exposes a rich public API. Next up is a new language service written purely using that public API and exposing its own extensibility points to allow 3^rd parties to do amazing things inside Visual Studio with that language understanding.

Traditionally, compilers are black boxes -- source code goes in one end, and object files or assemblies come out the other end. The Microsoft “Roslyn” community preview changes that model by opening up the VB and C# compilers.

Compilers in “Roslyn” provide APIs to allow tools and end-users to share in the wealth of information the compilers have about code. The Microsoft "Roslyn" CTP previews the new language object models for code generation, analysis, and refactoring, and the upcoming support for scripting and interactive use of C# and Visual Basic.

Picked Silverlight 4.0 over WPF 4.0

It has been two months to work on a POC for a new client, a major marine transportation company. I am the sole SunGard technology resource along with BAs to work with the client. It is very rewarding to work on the archeticture from ground up. It gave me the chances to compare the technologies side by side. We have hand-picked the following technologies the in-house transportation scheduling engine.

• Silverlight, and XAML
• MVVM, and Prism
• Unit tests, MSTest, MOQ, and TDD
• Multi-threaded programming, and TPL
• Distributed System, and NServiceBus
• Entity Frameworks, and WCF Data Service
• WCF, and REST
• FitNesse, SliMTest, and Acceptance Test
• Telerik Silverlight Controls
• Distributed Cache, e.g. SharedCache, AppFabric
• Oracle ODP .NET client to Oracle Financial System

Visualization is the key of the POC. The reason that we pick up Silverlight over WPF is that the map performance. Telerik Map Silverlight Radcontrols is performing much better than WPF with the DeepZoom technology. The map is the highlight of the POC. It visualize the routes, the locations, the boat speed, and scheduling features. On the plus side, Silverlight can also support multiple platforms like Apple MacOS. So Silveright wins. To be honest, as a developer I would never like Silverlight over WPF. But the map is just so beautiful and more informative than any other means. WPF doesn’t support it as well as Silverlight.

TPL Dataflow Presentation

With quite good responses to my presentation about .NET Task Parallel Library (TPL) to both the office SunGard and the client BoA/ML, I am asked to give another presentation to the first meeting of SunGard Houston .NET interested group. This time I am going to add TPL Dataflow (Visual Studio Async) to the talk. There are a few good points about TPL dataflow which I am very pleased with. I am pretty sure the presentation will generate a lot of interests in the techie community of the office.

First of all, as we all know, in particular TPL did not focus on problems best expressed with agent-based models or those based on message-passing paradigms. TPL Dataflow is focused on providing building blocks for message passing and parallelizing CPU- and I/O-intensive applications with high-throughput and low-latency.

Secondly, you can actually use Rx in Task Dataflow. Rx is predominantly focused on coordination and composition of event streams with a LINQ-based API, providing a rich set of combinators for manipulating IObservable<T>s of data. You can let data flow blocks to be exposed as both observable and observers, therefore enabling direct integration of Rx library.

The implementation is extremely flexible and give the developers a lot of options. TPL Dataflow is comprised of "dataflow blocks," data structures that buffer, process, and propagate data. They can be either sources, targets, or both, in which case they're referred to as propagators, e.g.
ActionBlock, BufferBlock, BoadcastBlock, WriteOnceBlock, TransformBlock, BatchBlock, JoinBlock, and BatchedJoinBlock.

.NET 4.0 TPL Rocks!

I’ve been working with multi-threaded programming since C# v1.0 with Visual Studio 2003. Before that, I have a few years working on multi-threaded programming in Java and C++.

There were a few things I hated on multi-threaded programming: imperative programming, implicit contract, and heavy thread composing; Thread interacting with WaitHandles like ManualResetEvent and AutoResetEvent; concerns about the race conditions, dead locks, live locks, thread starving etc. The last but not the least is the debugging. When there is something going wrong, it is really hard to debug without a good tool.

Task Parallel Library, or TPL, is a new .NET 4.0 new library, an component of the .NET 4.0 Parallel Frameworks. After I used it in my project, I felt Microsoft really hit the ball off the park this time.

TPL is EASY. TPL is just like the easy button. It is easy to use. It is easy to debug. It is easy to boost the performance of your application. If you have not started to use it in your project, I would strongly recommend you to start to use it or encourage your developers to use it.

Tasks vs Threads -> Tasks don’t equal to threads. You can think of Tasks are threads without all the threads’ drawbacks. Threads are single core, expensive on resources, such as 2M user mode memory plus kernel constructs. Thread needs time to startup and dispose. The most important is that the context switching the performance killer.

TPL is better in performance than using thread:

· Task scheduler has been highly optimized to utilize multi-processors with the brand new thread pool.

· There are less startup and tear down (mostly I/O) time for tasks than for threads.

· There is less time spending on context switching for tasks than for threads when threads are more than cores. Performance will degrade if the thread manager is not multi-core aware and thread running time aware.

· Memory (I/O) has been pre-allocated for the thread pool.

Here are some tips I learned to use TPL:

-- -- TPL Tips – Creating Task

· You can pass delegate to the constructor, either Action or Func. You can pass LINQ expression as well.

· You can create Task and run it right away. Or you can just create a task and declare it’s running condition.

· You can define TaskCreateOptions, such as LongRunning, or AttachedParent

· You can pass in Cancellation token.

-- -- TPL Tips – Passing data

· You can pass any object inherited from System.Object

-- -- TPL Tips – Returning

· This is way better than old TheadPool.QueueUserItem

-- -- TPL Tips – Waiting

· Waiting is a good way to declare parallelism

· Wait, WaitAll, WaitAny

-- -- TPL Tips – Cancelling

· Cancelling is cooperative

· CancellationTokenSource can be used once.

· Cancellation Token can be passed into task creation or waiting

· The beauty of the cancellation token is once the cancellation token source is cancelled, if the task has not been scheduled, it will not be executed.

-- -- TPL Tips – Continuing

· Task.ContinueWith

· Task.Factory.ContinueWhenAll()

· ContinuationOptions (OnlyOnFaulted, OnlyOnCancelled, NotOnRanToComplete)

· Continue with ParentTask.Result

-- -- TPL Tips – Composing

· AttachedToParent

8. -- TPL Tips – AggregateException

9 . -- TPL Tips – Cool Tools

· Parallel Tasks (see the location of code)

· Parallel Stacks (see the stack of the code)

What is hot in the coming releases in .NET 5.0?

Task DataFlow (TDF) – is based on Concurrency and Coordination Runtime and Visual C++ Asynchronous Agency 2010. Currently it is based on.

Visual Studio Async - async and await keywords. You can await anything, not only Task and Task.

Like I mentioned, if you haven't started to use TPL, you should start now. TPL is easy to use, easy to debug, easy to boost the performance of your application.