Comments
Sort by recent activity
Hi
Sorry - it got a bit out of order, but if you look at the post preceding that last one, I did use dotNetPeek on the assembly both before obfuscation with SA and after obfuscation and noted the differences.
What email address should I use for sending in the assembly ?
Cheers
Kal / comments
Hi
Sorry - it got a bit out of order, but if you look at the post preceding that last one, I did use dotNetPeek on the assembly both before obfuscation with SA and after obfuscation and noted the d...
Hi Brian,
Thanks for the response. If this issue can be fixed by using a licensed copy of SmartAssembly, then that is definitely good news. It is a shame that we can't test the use of the assembly ourselves with the evaluation version, but if we have an assurance from Redgate that we will be able to obfuscate our WP 7.1 assembly and let our customers use it in their projects without this Silverlight dependency, then I am happy to proceed and get the licenses we need.
Many thanks for your assistance!
Cheers
Kal / comments
Hi Brian,
Thanks for the response. If this issue can be fixed by using a licensed copy of SmartAssembly, then that is definitely good news. It is a shame that we can't test the use of the assembly...
Hi Brian
I checked with dotPeek and for the unobfuscated assembly it shows one reference to:
mscorlib, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e
When I expand that reference, I get the mscorlib assembly with the WindowsPhone71 profile.
For the obfuscated assembly, it references the same mscorlib but also System.Windows.Browser (System.Windows.Browser, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
Can you give me a pointer on what compiler settings might be causing this problem - I'm happy to try things out, but I am very confused as to why this is happening at all with an empty, unmodified project and I'm not sure where to start with poking around at compiler settings.
Cheers
Kal / comments
Hi Brian
I checked with dotPeek and for the unobfuscated assembly it shows one reference to:
mscorlib, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e
When I expand that reference...
Further to my last message, this is the output from msbuild when compiling the assembly:
CoreCompile:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Csc.exe /noconfig /nowarn:1701,
1702 /nostdlib+ /errorreport:prompt /warn:4 /define:DEBUG;TRACE;SILVERLIGHT;W
INDOWS_PHONE /reference:"C:\Program Files (x86)\Reference Assemblies\Microsof
t\Framework\Silverlight\v4.0\Profile\WindowsPhone71\mscorlib.dll" /reference:
"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\Silverlight v4.0\Profile\WindowsPhone71\mscorlib.extensions.dll" /reference:"C:\Program F
iles (x86)\Reference Assemblies\Microsoft\Framework\Silverlight\v4.0\Profile WindowsPhone71\System.Core.dll" /reference:"C:\Program Files (x86)\Reference
Assemblies\Microsoft\Framework\Silverlight\v4.0\Profile\WindowsPhone71\system
.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Frame
work\Silverlight\v4.0\Profile\WindowsPhone71\System.Net.dll" /reference:"C:\P
rogram Files (x86)\Reference Assemblies\Microsoft\Framework\Silverlight\v4.0 Profile\WindowsPhone71\System.Windows.dll" /reference:"C:\Program Files (x86)
\Reference Assemblies\Microsoft\Framework\Silverlight\v4.0\Profile\WindowsPho
ne71\System.Xml.dll" /debug+ /debug:full /optimize- /out:obj\Debug\PhoneClass
Library1.dll /target:library Class1.cs Properties\AssemblyInfo.cs "C:\Users\K
al\AppData\Local\Temp\Silverlight,Version=v4.0,Profile=WindowsPhone71.Assembl
yAttributes.cs"
All references are definitely only to the WindowsPhone71 profile of Silverlight. / comments
Further to my last message, this is the output from msbuild when compiling the assembly:
CoreCompile:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Csc.exe /noconfig /nowarn:1701,
1702 /nostdlib+ /...
Hi Brian,
As I said in my last post, I am now just trying to obfuscate a completely empty new Windows Phone 7.1 class library project. So, there is *no* custom code in it, *no* assembly references other than the ones added by Visual Studio. VS shows that the mscorlib reference is to the Windows Phone 7.1 profile mscorlib.dll reference.
I tried editing the .saproj to remove all the references added by SA except for mscorelib, for which I then set a MandatoryPath property to point to the WindowsPhone71 mscorlib. After the build, SA has modified the .saproj file again - the MandatoryPath remains in the .saproj file after the build, but the additional reference to System.Web.Browser is back in there.
Are you saying that you cannot reproduce this problem with the steps I outlined in my previous post ? If not, do you have any idea at all why this behaviour might appear on my machines (plural, I have tried on two different development machines), but doesn't appear in your setup ?
Cheers
Kal / comments
Hi Brian,
As I said in my last post, I am now just trying to obfuscate a completely empty new Windows Phone 7.1 class library project. So, there is *no* custom code in it, *no* assembly references ...
Hi Brian,
Thanks for looking into this for me!
The main difference is my application is a Windows Phone application - and applications hosted in the browser are not supported (see http://msdn.microsoft.com/en-us/library ... 95%29.aspx - Unsupported Features). The entire System.Windows.Browser namespace is not available on Windows Phone (you can see this in the SDK docs when you check the version information - see http://msdn.microsoft.com/en-us/library ... 95%29.aspx - Using the Reference Documentation).
So I would expect everything to be fine with a "regular" Silverlight app, but not with a Windows Phone app.
I'm wondering if one or more of the SmartAssembly.* assemblies are actually regular Silverlight. I am currently using an eval version, and so I wonder if you have some Silverlight GUI that pops up when the app runs and if it is this that pulls in the System.Windows.Browser reference. Of course, I could be barking up totally the wrong tree, but might be worth checking with the dev guys.
Cheers
Kal / comments
Hi Brian,
Thanks for looking into this for me!
The main difference is my application is a Windows Phone application - and applications hosted in the browser are not supported (see http://msdn.micro...
Hi Brian,
To sum up, you are protecting a DLL assembly using SmartAssembly, then referencing that assembly in another application, and when you compile that application, you get this error?
Yes, exactly. The error is showing in Visual Studio. As I don't get this error with the unobfuscated DLL I'm certain that I don't have any reference to the System.Windows.Browser assembly in my code and I'm fairly sure that there aren't any references in the other dependencies, but I do see a bunch of additional assembly references in the .saproj file with SmartAssembly-specific names, so I wonder if that has something to do with it ?
Cheers
Kal / comments
Hi Brian,
To sum up, you are protecting a DLL assembly using SmartAssembly, then referencing that assembly in another application, and when you compile that application, you get this error?
Yes,...