October 30, 2008 • 2:01 pm
That’s simple buy a house that needs to be finished in the meantime switch jobs and on top of that move out of your current appartement.
I’ve not been writing as much as would like, but I can’t seem to find the time. Lately I’ve been watching more closely to LINQ, Nhibernate, EDM, Windows Server 2008 and Visual Studio .net Codename ”Orcas”… I know that’s a lot but I can’t keep up and I would like to explore as much as humanly possible under current conditions.
Anyways my findings in short are:
LINQ: nice
NHibernate: same as LINQ = nice + advantage current support .net 2.0 and older versions.
EDM: yeah well… nice as well 
Windows Server 2008: mmm still beta, should say enough.
VS.Net Orcas: surprisingly “stable”.
Filed under: .net, .net 2.0, .net 3.0, .net 3.5, Visual Studio .Net "Orcas", Windows
Anson Horton wrote a very nice article for the MSDN magazine June 2007 edition. It gives you an overview of how LINQ (Language Integrated Query) has evolved from the idea of the concept to an actual technology. A nice extra on this article is that he shows a lot which new language features in C# 3.0 made it actually possible to come to version on LINQ we have now. It’s thanks to Lambda Expressions, Extension Methods, Anonymous Type, Implicitly Type Local Variables, Object Intitializers and Query expressions that LINQ can offer you a very nice language enhancement to query for example objects, dataset, xml, …
Check it out at:
http://msdn.microsoft.com/msdnmag/issues/07/06/csharp30/default.aspx
Filed under: .net, .net 3.0, .net 3.5, LINQ, Visual Studio .Net "Orcas", Visual Studio .Net 2005
F or those that like to get started with the new Microsoft products Expression Blend and Expression Design. You should check out these links below. They give you access to tons of FREE video tutorials hosted by lynda.com
Links:
- Getting started with Expression Blend
In Getting Started with Expression Blend , Lee Brimelow covers all the basics that every designer and developer of WPF and Silverlight content needs to know. He starts with an overview of how Expression Blend fits into WPF and Silverlight workflows, then guides viewers through the process of creating and manipulating objects, building timeline-based animations, and exporting compositions into XMAL for use in Visual Studio.
- Getting started with Expression Design
From basic vector-based drawings to professional three-dimensional graphics built with Live Effects, Ted LoCascio covers the full range of possibilities in Getting Started with Expression Design. He starts by explaining Expression Design’s interface and how to work with documents, then moves on to cover working with objects and applying fills, strokes, and effects for best results. Exercise files accompany this training.
Enjoy!
note: the lynda.com logo is protected by copyrights. Suddenelfilio.net is not in any way affiliated with lynda.com or any of its partners.
Filed under: .net, .net 3.0, Expression Blend, Expression Design, Visual Studio .Net "Orcas", Visual Studio .Net 2005, WPF
April 20, 2007 • 12:16 am
I saw the notice on Informationweek that Microsoft released a beta of the VS.net Orcas.
Find out more here.
Filed under: .net, .net 2.0, .net 3.0, .net 3.5, Asp.net, Asp.net 2.0, Asp.net Ajax, General, Visual Studio .Net "Orcas"
January 19, 2007 • 3:07 pm
I’m currently trying out the Microsoft Expression Blend designer (formerly known as Microsoft Expression Interactive Designer). I must say it’s already very nice, the only I still can’t seem to get working is the integration with visual studio .net 2005 to edit the code behind files… Anyway that’s not what I wanted to talk about.
We probably know that you can do marvelous things with WPF it’s like a Flash designer but for .Net developers : Not sure Adobe is going to like that. So why should you constrain yourself to the old looking windows? Why not try something more different.
The image below shows you the kind of application I mean.
As you can see the image has something extra stick out in the left upper corner. To achieve this you just set the WindowStyle to None, Background to “transparent” and AllowTransparancy to “True”.
This will give you a borderless and transparent window. In this example I’ve set the background of the grid using an ImageBrush that will allow me to use a customized background image
….
Next is the actual image that represents the out-of-border network drive. This is nothing more than an image placed in that particular position. Okay the application is ready to run.When you run the application you’ll see that you can’t drag the application to another location on the screen…
To solve this problem you need to add a Thumb. A Thumb is a WPF Control that can be dragged around. You can declare a thumb that has the same size as your window. When you do this the application will kind of funny because all you see is a light gray area. To prevent this overlay set the Opacity property of the Thumb to 0.
Next thing to do is to implement the DragDelta event of the thumb. It’s this code that will actually move the entire window. The code for this is pretty simple:
Public Sub onDragDelta(ByVal sender As Object, ByVal e As Primitives.DragDeltaEventArgs)
Canvas.SetLeft(Me, Canvas.GetLeft(Me) + e.HorizontalChange)
Canvas.SetTop(Me, Canvas.GetTop(Me) + e.VerticalChange)
End Sub
That’s it… you can now drag the window around.

Filed under: .net 3.0, WPF
I was helping a colleague of mine this week with some exception handling in WCF. The problem we were facing was that when we send a faultexception we lost important information about the original exception like the innerexceptions. Although it may not be best practice to send all of the exception information to the client we still wanted to find a way to get this done.
We tried various possibilities and ended up with the binary serialization of the original exception. To send it to the client we converted the serialized exception to a base64 string which is ideal for this sort of scenario’s. Then on the client side we just deserialize the base64 string back into an exception. We still use the WCF faultexception but we use the reason property to store the base64 string for transport.
We also tried the XML serialization but this gave to much trouble on the data property of the exception class because it was marked not-serializable due to the IDictionary interface it implements.
Another thing we looked at was using reflection to rebuilt the exception, but this was too complex and can cause a performance overhead.
Below you can see a sample of the ExceptionFormatter class that we created. Actually it’s nothing more than regular binary serialization with the constraint that the serialized object must implement the ISerializable interface. Oh yes mind the line breaks !
Imports System.Runtime.Serialization.Formatters.Binary
Public Class ExceptionFormatter
Public Sub New()
End Sub
Public Function Serialize(ByVal objectToSerialize As Runtime.Serialization.ISerializable) As String
Dim formatter As New BinaryFormatter
Dim mem As New IO.MemoryStream
formatter.Serialize(mem, objectToSerialize)
Return Convert.ToBase64String(mem.ToArray)
End Function
Public Function Deserialize(ByVal base64String As String) As Runtime.Serialization.ISerializable
Dim formatter As New BinaryFormatter
Return formatter.Deserialize(New IO.MemoryStream( Convert.FromBase64String(base64String)))
End Function
End Class

Filed under: .net 3.0, WCF