SmartAssembly - 6.6
Using SmartAssembly with MSBuild
You can integrate SmartAssembly in your build process.
You set up your project in SmartAssembly once, and you can then build your assembly in your normal MSBuild process. The settings you chose in the SmartAssembly project are applied without needing to run SmartAssembly separately.
Note that the SmartAssembly task should be the last stage of your build process. Because of the way SmartAssembly changes your assembly, running other tasks after SmartAssembly is not supported. (An exception to this is assembly-signing tools, if you choose not to sign your code with SmartAssembly).
To integrate SmartAssembly directly into the build process, follow these steps:
- Create your project in SmartAssembly (see Working with projects) and set the project options (see Setting project options).
- Open your application's .csproj or .vsproj file in an XML editor.
The .csproj or .vsproj file is actually a MSBuild XML file that you can edit to add SmartAssembly to the build tasks. For more information about the MSBuild XML schema, see the MSBuild documentation on MSDN.
- Add references to SmartAssembly to your C# or VB.NET project file, as follows.
Note that the
<UsingTask>element includes SmartAssembly's major version number. This page has been written for SmartAssembly 6.x. If you are using a different version of SmartAssembly, you will need to change the version number specified in the
<UsingTask>element. For example, if you use SmartAssembly 5.5, change the version to Version=220.127.116.11
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
<UsingTask TaskName="SmartAssembly.MSBuild.Tasks.Build" AssemblyName="SmartAssembly.MSBuild.Tasks, Version=18.104.22.168, Culture=neutral, PublicKeyToken=7f465a1c156d4d57" />
<Target Name="AfterBuild" Condition=" '$(Configuration)' == 'Release' ">
- Edit the following line (near the bottom of the XML which you just added to the project), setting the
ProjectFileattribute to the path to your *.saproj file:
- If required, add any of the following optional attributes to the same element:
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 .saproj project.
If you set this option to True, SmartAssembly ignores the OverwriteAssembly attribute, if set.
If this option is set, SmartAssembly will process the assembly specified as this attribute's value.
If this option is not set, SmartAssembly will process the assembly specified in the .saproj project is used.
This is useful if you want to build an assembly using exactly the same settings as those you chose for a different assembly.
If this option is set, SmartAssembly will use this attribute's value as the file name when saving the built assembly.
If this option is not set, SmartAssembly will use the file name in the .saproj file when saving the built assembly.
This attribute is ignored if the OverwriteAssembly property is set to True.
This option is useful if you want to save a test build to a different path from other builds.
This option was used in SmartAssembly 6.2 and earlier to preserve map files (see About map files).
SmartAssembly 6.5 stores map files permanently, so this option is ignored.
A diff showing the added lines in a .csproj file is shown below.
Build your assembly with MSBuild. SmartAssembly is run automatically, using the settings in your SmartAssembly project file.
If you use a .mdb file for your SmartAssembly database, ensure that Visual Studio is run as an administrator when running MSBuild.
Was this article helpful?
Thanks for your feedback!
- 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
- 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
- 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