sfeldman.NET

I have attended Enterprise Development with NServiceBus course last week. Interestingly, a lot of questions I had back a while ago where answered. Either I was missing the knowledge, or not asking the right questions. Either way, what I was trying to accomplish a year and something ago with BizTalk could be done ten times simpler with NSB. BizTalk was a great tool for mapping, but definitely neither a services platform nor a bus. Long-term running processes with BizTalk (aka Orchestrations) felt plain wrong. The fact that one was not able to test the bread and butter of a business process w/o having a full end to end integration testing was mind blowing. Creating messages outside of BizTalk has felt like a shameful sin.

1. It’s publicly documented

Just a few weeks ago I wrote a small application that would allow a designer to work on markup and CSS and when those are saved, changes automatically uploaded to an FTP and local browser that is usually sitting on the second monitor is refreshed. That was a fun side little app to do.

A while ago I had a conversation with a gentleman who resisted .NET development on the client side reasoning it that in case .NET framework doesn’t exist, installer won’t fail. WiX 3.6 Beta is out and it solved the “problem”. Reminds me of situation when “business code needs to be efficient to take less memory” situation. We’ve all seen that code die slowly and painfully

Asserting arguments is essentially a healthy practice. What I don’t like, is the fact that since day one ArgumentNullException used a string for argument name, and now with .NET 4.5 almost knocking on the door, there’s still only string option.

In my last post I have described the move from NAnt to PSake that is based on PowerShell. One missing piece for making the whole experience smooth was Visual Studio support for PowerShell syntax and some Intellisense. Gladly, I have run into PowerGUIVsx, that does just that: syntax highlighting, intellisense, and even debugging. Sweet!

My exploration of automation and CI has started around somewhere in 2007. Back then it was more of a guess and trial, trying to figure out what I don’t know and should learn. Automated build scripts was the first thing I needed to learn. Back then, NAnt seamed to be the best candidate, and quite frankly, it was the first thing that looked solid to me, therefore making it my default. Ironically, I had my first build script working with Visual Source Safe.

There’s another kid on the .NET obfuscation block – totally free and plays nicely with command line - Eazfuscator.NET. It also has a NuGet package available for download, though it’s not up-to-date.