SmartAssembly - 6.5
Using SmartAssembly with ClickOnce
If you use SmartAssembly after you have built your project, you will not be able to deploy it using Microsoft ClickOnce. This is because SmartAssembly has modified the assembly.
To use ClickOnce to deploy your assembly, integrate SmartAssembly directly into the build process in MSBuild.
- Create your project using the SmartAssembly project settings page as normal.
Note: The main assembly must be in the \obj\Release folder, and NOT in \bin\Release. The location of the destination assembly does not matter. - Edit your C#/VB.NET project with an XML editor (or Notepad).
The project file looks like the following:
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
...
</PropertyGroup>
...
<ItemGroup>
...
</ItemGroup>
<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
<!-- To modify your build process, add your task inside one of the targets below and uncomment it.
Other similar extension points exist, see Microsoft.Common.targets.
<Target Name="BeforeBuild">
</Target>
<Target Name="AfterBuild">
</Target>
-->
</Project>
- Add a few lines after the
<Import Project>node:<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
<UsingTask TaskName="SmartAssembly.MSBuild.Tasks.Build" AssemblyName="SmartAssembly.MSBuild.Tasks, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7f465a1c156d4d57" />
<Target Name="BeforeBuild" Condition=" '$(Configuration)' == 'Release' ">
<CreateProperty Value="true">
<Output TaskParameter="Value" PropertyName="RunSmartAssembly"/>
</CreateProperty>
</Target>
<Target Name="AfterCompile" Condition=" '$(RunSmartAssembly)' != '' ">
<SmartAssembly.MSBuild.Tasks.Build ProjectFile="c:\temp\TestMSBuild\TestMSBuild.saproj"
OverwriteAssembly="True" />
</Target>
The first XML node adds a reference to SmartAssembly.MSBuild.Tasks.dll, which is installed into the GAC:
<UsingTask TaskName="SmartAssembly.MSBuild.Tasks.Build" AssemblyName="SmartAssembly.MSBuild.Tasks, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7f465a1c156d4d57" />The second XML node tells MSBuild to set the
RunSmartAssemblyproperty in theBeforeBuildevent, when the project is fully built in release mode:<Target Name="BeforeBuild" Condition=" '$(Configuration)' == 'Release' ">
<CreateProperty Value="true">
<Output TaskParameter="Value" PropertyName="RunSmartAssembly"/>
</CreateProperty>
</Target>
If the
RunSmartAssemblyproperty is set, the last XML node tells MSBuild to protect the assembly in theAfterCompileevent:<Target Name="AfterCompile" Condition=" '$(RunSmartAssembly)' != '' ">
<SmartAssembly.MSBuild.Tasks.Build ProjectFile="c:\temp\TestMSBuild\TestMSBuild.saproj"
OverwriteAssembly="True" />
</Target>
You must set the following properties:
|
Shows the filename of the SmartAssembly project. |
|
Set to True if you want to overwrite the original assembly with the obfuscated one. If this option is not set, or set to False, SmartAssembly uses the destination file name from the ProjectFile project. |
Other options are:
|
Specify an input file name, instead of the one from the ProjectFile project. |
|
Specify the output file name for the obfuscated assembly. This property is ignored if the OverwriteAssembly property is set to True. |
|
Use a specific version number for the assembly. This changes the version for the AssemblyName, not the file version. |
If you have multiple projects
- Ensure that your SA project file is stored in the $(SolutionDir)\Build\ folder. It must have the same name as the target assembly. For example, if your assembly is MyTestAssembly.dll then the SmartAssembly project must be named MyTestAssembly.saproj
- Create a new file called SmartAssembly.targets in the SmartAssembly installation folder
- Paste the following code in the new file:
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003"><UsingTask TaskName="SmartAssembly.MSBuild.Tasks.Build" AssemblyName="SmartAssembly.MSBuild.Tasks, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7f465a1c156d4d57" /><Target Name="BeforeBuild" Condition=" '$(Configuration)' == 'Release' "><CreateProperty Value="true"><Output TaskParameter="Value" PropertyName="RunSmartAssembly" /></CreateProperty></Target><Target Name="AfterCompile" Condition=" '$(RunSmartAssembly)' != '' "><Copy SourceFiles=".\obj\Release\$(TargetFileName)" DestinationFiles=".\obj\Release\$(TargetName).temp$(TargetExt)" /><SmartAssembly.MSBuild.Tasks.Build ProjectFile="$(SolutionDir)Build\$(TargetName).saproj" OverwriteAssembly="True" /></Target></Project> - Edit your C# or VB.NET project with an XML editor (or notepad). Add the following line:
<Import Project="$(PathToSmartAssembly)\SmartAssembly.targets" />
Was this article helpful?
SmartAssembly
- Using Smartassembly to obfuscate a windows service
- Obfuscation not renaming identically-named methods in different classes
- Serialization exceptions occurring in obfuscated assemblies
- SmartAssembly skipping obfuscation of some classes in your assembly
- SmartAssembly is not merging or embedding all assembly dependencies
- Can I customize the path to the MDB database?
- System.InvalidOperationException when attempting to connect to local SmartAssembly database
- Protecting website code using SmartAssembly
- Visual Studio Deployment Projects including unprotected builds
- SmartAssembly MSBUILD tasks failing because of difference in log4net assembly
- SmartAssembly Error Reporting: This application has submitted too many reports
- The assembly is being merged, but the dependent assembly isn't
- ERR 2002: Server did not recognize the value of HTTP Header SOAPAction
- The error report is not associated with a valid project ID - SmartAssembly
- Application built with an evaluation edition of SmartAssembly
- How end users can change their participation in Feature Usage Reporting
- Log file for SmartAssembly
- Moving SmartAssembly to another computer
- 'Using JET databases is not possible in 64-bit applications' error when using MSBuild or TFS
- SmartAssembly stack trace is invalid when Method Parent Obfuscation is enabled
- Upgrading SmartAssembly version 4.x to version 5
- Upgrading SmartAssembly Standard to Professional
- Problems building WPF applications with SmartAssembly 6.7
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SmartAssembly
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs

Using SmartAssembly for obfuscation