We are Microsoft, and we will steal your IP

I will not be the first one to observe that MS steals things rather routinely. Not even the 2nd. Not even the 3d.

Enter WPF, the MS's new, glorious replacement for the boring, obsolete WinForms. WPF is a marriage between XML and C#/VB etc. Its windows and user controls are designed in XAML, the extension of XML for GUI.

Data binding is the King in XAML, and it is a perfect match for the MVVM pattern toutes as the 'next best thing' for software development and the natural pattern for WPF.

So, we embark on the binding process for some control, only to find out that the XAML editor in Visual Studio does not see your classes. Why?

After a long and tiresome investigation you find out that in order to be visible to XAML data binding, your classes have to be public. Huh? Why can they not be internal with InternalsVisibleTo element set to the public key of the assembly that contains the XAML? I will tell you why.

Microsoft did it so that once all your code runs in their Azure cloud they have access to the classes, properties and methods in your assemblies. Under DMCA they may get into legal trouble for un-signing and disassembling your assemblies in order to snoop on your code. So, they force you to make your classes public in order to see them w/o violating DMCA.

Posted by: LinuxLies at 12:26 PM | No Comments | Add Comment
Post contains 252 words, total size 1 kb.