Reflector + BamlViewer

[rudigrobler]

Hi Guys,

Quick question, how do I protect my XAML? Here is a blog article on my
current problem:

http://dotnet.org.za/rudi/archive/2008/06/17/protecting-my-intellectual-property-xaml.aspx

If you have any sugestions, recomended software, etc... please comment
on the blog entry or here!

Regards,

Rudi Grobler

[Josh Smith]

Don't even consider obfuscating XAML, it will kill your app.  Basically, there's no good answer.  At least, none that I have ever encountered.

[Jeremiah Morrill]

Can't wait to see your results on .NET Obfuscator 3.0.

 

In theory, couldn't BAML be deserialized, converted to IL, then fuscated?  Of course you'd lose whatever performance benifits BAML gives you.

 

-Jer

On Tue, Jun 17, 2008 at 10:28 AM, rudigrobler <rudi.g...@gmail.com> wrote:

[rudigrobler]

Hi Josh,

Is performance the only reason you say that it will kill the app? Is
this also only on start up?

Regards,

Rudi

On Jun 17, 4:36 pm, "Josh Smith" <flappleja...@gmail.com> wrote:
> Don't even consider obfuscating XAML, it will kill your app.  Basically,
> there's no good answer.  At least, none that I have ever encountered.
>

> On Tue, Jun 17, 2008 at 10:28 AM, rudigrobler <rudi.grob...@gmail.com>

> wrote:
>
>
>
>
>
> > Hi Guys,
>
> > Quick question, how do I protect my XAML? Here is a blog article on my
> > current problem:
>

> >http://dotnet.org.za/rudi/archive/2008/06/17/protecting-my-intellectu...

>
> > If you have any sugestions, recomended software, etc... please comment
> > on the blog entry or here!
>
> > Regards,
>

> > Rudi Grobler- Hide quoted text -
>
> - Show quoted text -

[Josh Smith]

No, I mean your app won't work.  If the classes that have a XAML partial are obfuscated, the names/identifiers in BAML will not be "munged" to stay in sync with the names of things in code.  This causes exceptions galore.

Josh