Using SmartAssembly with MSBuild
2017-06-09 11:14
316 查看
SmartAssembly 6
SmartAssembly 6 documentation
Building your assembly
Using SmartAssembly with MSBuild
Skip to end of metadataLast edited May 20, 2013
Go to start of metadata
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 Working with project settings).
Open your application's .csproj or .vsprojfile 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=5.0.0.0
ProjectFileattribute to the path to your *.saproj file:
<SmartAssembly.MSBuild.Tasks.Build ProjectFile="c:\path\to\project.saproj"/>
If required, add any of the following optional attributes to the same element:
OverwriteAssembly | 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. |
Input | 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. |
Output | 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. |
MarkAsReleased | (Deprecated) 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. |
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.
相关文章推荐
- Using Inline Assembly With gcc
- Delphi2005学习笔记2——Using Platform Invoke with Delphi 2005
- SQL Server 2005: Using OVER() with Aggregate Functions
- 在freemarker中使用jsp标签 Using FreeMarker with servlets
- [译文]Using Cookies with PHP
- The ins and outs of using Java with Domino
- 汉化破解:{smartassembly}使用指南
- Using Pythonbrew and Virtualenv(with pip) for creating sandboxed Python development environments.
- USING HIVE WITH ORC FROM APACHE SPARK
- Using An Item Template With An HTML Dropdown Menu Component In Angular 2 RC 3
- Interfacing DJGPP with Assembly-Language Procedures
- Issue 71 - pymssql - Undefined symbols on Mac, CentOS, Redhat with pre-compiled build - A fast MS SQL Server client library for Python directly using C API instead of ODBC. It is Python DB-API 2.0 compliant. Works on Linux, *BSD, Solaris, Mac OS X and Win
- How to configure XDB for using ftp and http protocols with ASM [ID 357714.1]
- org.mockito.exceptions.misusing.CannotStubVoidMethodWithReturnValue
- Using OpenCV Java with Eclipse(转)
- Rapid Web Applications with TurboGears: Using Python to Create Ajax-Powered Sites
- using-couchdb-with-java-and-domain
- Working with Data in ASP.NET 2.0 :: Using TemplateFields in the GridView Control
- Using BACKUP ARCHIVELOG with DELETE INPUT or DELETE ALL INPUT【每日一译】--20121115
- Pro Service-Oriented Smart Clients with .NET 2.0