While I was upgrading Castle Windsor to support .NET 4.0 build scripts, I came across an interesting depricated API. If you have set Warnings are Errors in your project settings, you'll definetly get bitten by this once you upgrade your project from .NET 3.5 to .NET 4.0, if you're using SecurityManager that is.

 

We've been doing a lot of Java / .NET interop for last couple of years in our enterprise applications. On one hand, our customers used their existing expertise and infrastructure that worked better with Java based technologies like their existing Unix based servers, Sybase database (on Unix) and the knowledge of their DBA team, and we using our existing Java developers and expertise. But what Java based technology provides that we don't have on .NET world? Is it important at all?

 

In the middle of investigating the new Rhino Service Bus (more on this on later posts), I was trying to create a console application that'd act like a Console Application Server. 

There's a new kid on the block! An effort to port Java frameworks to .NET is not a new thing and it's been around since the early days of .NET 1, but integration of .NET Framework and Java Development Kit (JDK) is something I'm not used to see everyday! 

FarsiLibrary RC 2.1 is here. Some reported bugs are fixed in this release and some new features are added. Please report back any problem you may have. Please note that changes labeled as "Modified" *might* break your current application.