Mark XAP released for WP7 using

.NET obfuscator and automated error reporting

Mark XAP released for WP7 using

Postby cohowap » Thu Jun 02, 2011 6:43 pm


Mark released works fine in the GUI, but when doing an automated build using I'm getting the below error.


[exec] SmartAssembly v6.1.0.48
[exec] Copyright c Red Gate Software 2005-2011
[exec] Loading project C:\\BUILDROOT\\MyApp\\MyApp.saproj
[exec] Analyzing...
[exec] Preparing...
[exec] Creating Assembly...
[exec] OK
[exec] SmartAssembly v6.1.0.48
[exec] Copyright c Red Gate Software 2005-2011
[exec] Loading assembly C:\\BUILDROOT\\MyApp\\Obfuscuated\\MyApp.xap
[exec] System.IO.DirectoryNotFoundException : Could not find a part of the path 'C:\\Windows\\TEMP\\963444a3-6261-4c46-a69c-3ee7b47d412a\\AppManifest.xaml'.


External Program Failed: C:\\Program Files\\Red Gate\\SmartAssembly 6\\ (return code was 1)

Here is the code I am using to mark released (NAnt script):

<exec program="" basedir="${SmartAssembly.ExePath}">
<arg value="/build" />
<arg value="${Build.Root}\\MyApp.saproj" />

<exec program="" basedir="${SmartAssembly.ExePath}">
<arg value="/markasreleased" />
<arg value="${Build.Root}\\Obfuscuated\\MyApp.xap" />

It looks as if SA is unpacking the xap then doing something, but before it can, the temp dir is blown out.

Any ideas? Do I really need to markasreleased?
Posts: 3
Joined: Thu Jun 02, 2011 1:19 pm

Postby Brian Donahue » Mon Jun 06, 2011 10:20 am


I would pin this issue down to the rights of the account running the automated build task rather than SmartAssembly. The way SA works with Silverlight is to extract the .XAP built by Visual Studio to the %TMP% folder, process the DLL(s) inside and re-zip the files back into a new .XAP file.

Looks to me as if the issue is that can't find the extracted files in the temporary folder where they're supposed to be.

You can try running the build task as a different user (from the looks of it, you are using the SYSTEM account) or grant modify rights to the files in c:\\windows\\temp to whatever account runs the build.

Highly unlikely, but this could also be caused by some AV/security program so you may want to check that out, too.
Brian Donahue
Posts: 6590
Joined: Mon Aug 23, 2004 9:48 am

Postby medeia » Mon Apr 30, 2012 1:08 pm


I know this is an old topic, but I have the same problem. Could you tell me if you found a solution to the problem?

Posts: 1
Joined: Mon Apr 30, 2012 12:49 pm

Postby Brian Donahue » Mon Apr 30, 2012 2:58 pm

No - sorry there was never any follow-up. I'm 99% sure this is nothing to do with SmartAssembly and is an environmental issue.
Brian Donahue
Posts: 6590
Joined: Mon Aug 23, 2004 9:48 am

Return to SmartAssembly 6

Who is online

Users browsing this forum: No registered users and 0 guests