Ambiguity in WPF Library| Visual Studio Rescue
Last night I coded my simple applications J
Get this …
As usual in managed environment, I chose the Windows Forms library just because the Microsoft.Win32 will run unexpectedly in partial trust environment … by adding Windows Forms assembly into my WPF projects that is a simply solutions .
5 minutes after
Again? Which one I choose? Well I chose System.Windows.MessageBox since its use native library for WPF 3.5 rather than using Windows.Forms
3 minutes after the second case
Whoa Again? However in this case, the Path class is do a different things... so it's not a big deal it's simply a different namespaces J
1 minutes after the third case
I really love this dialog when I'm using VSTS J
Namespaces Ambiguity, Business Process unit testing... Visual studio seems save my time today...
Ciao | Ridi