any way to obfuscate .net 3.5 with xaml?

[kirk]

after obfuscating an assembly which uses xaml, i get a crash when i
invoke the program. i think it relates to the xaml/baml files staying
intact while the rest of the code gets obfuscated.

i've tried excluding _all_ of the namespaces just as an excercise but
it still doesn't work

any idea?

[Ryan Williams]

It shouldn't have a problem with the 3.5 framework. I haven't had an
occasion to try it with xaml, but I can easily imagine it
failing...it's going to be doing reflection all over the place, and
obfuscar scrambles the metadata needed to match the xaml to the
underlying code. Without also obfuscating the references in the xaml
to match the code, or without skipping obfuscation of the parts of the
code referenced by the xaml, it's pretty unlikely to work.

[kirk]

Thanks, eventually what i did is:
move XAML forms/control into a 'xaml' namespace and exclude
and exclude this
<SkipNamespace name="XamlGeneratedNamespace" />


one more question, im trying to streamline this into a buildprocess in
postbuild:
im always getting this:
Unable to read specified project file: C:\Work\Workspaces\vs2k5\..
\config.xml

all the paths exists, if i take the commadn and run in commandpromt,
same result, any ideas?

[Ryan Williams]

It might be the ".." in the path...does it work if you put the absolute path?