Comments
Sort by recent activity
Simon C wrote:
Make sure you are running SmartAssembly.com from the commandline rather than SmartAssembly.exe. The com file provides a standard CLI interface, rather than opening the GUI.
Great, thanks! / comments
Simon C wrote:
Make sure you are running SmartAssembly.com from the commandline rather than SmartAssembly.exe. The com file provides a standard CLI interface, rather than opening the GUI.
Grea...
I will try to be more clear:
When I include the .saproj in the Visual Studio as follows: <Target Name="AfterBuild" Condition=" '$(Configuration)' == 'Release' ">
<SmartAssembly.MSBuild.Tasks.Build ProjectFile="EasyFit.saproj" />
</Target>
And build my project, the resulting executable gives an unhandled exception at startup (see below for details of this exception).
When I open this same .saproj in SmartAssembly and build, this exception does not occur when starting the resulting executable.
The obfuscated executable is written in a seperate folder, which is a subdir of the bin\Release folder. Obfuscation and assembly merging is applied.
It's an "System.Windows.Markup.XamlParseException" exception with the following message: "Cannot find type 'Type Name'. The assembly used when compiling might be different than that used when loading and the type is missing."
It occurs in "XamlReader.LoadBaml". So the exception appears to be related to the error messages I see in MSBuild: "Error rewriting xaml for resources/glowbutton.baml"..etc. / comments
I will try to be more clear:
When I include the .saproj in the Visual Studio as follows:<Target Name="AfterBuild" Condition=" '$(Configuration)' == 'Release' ">
<SmartAssembly....
I tried to clean the build first, but the problem remains.
Additional note: If I run obfuscation right from Visual Studio 2012, the resulting build crashes on startup. If I run obfuscation from outside Visual Studio, using the SmartAssembly user interface, the build is ok. / comments
I tried to clean the build first, but the problem remains.
Additional note: If I run obfuscation right from Visual Studio 2012, the resulting build crashes on startup. If I run obfuscation from out...