SmartAssembly - 6.5
Using custom attributes - SmartAssembly
You can use custom attributes to specifically exclude parts of your code from obfuscation, pruning, sealing and error reporting.
Defining attributes
To define the attributes, either:
- in Visual Studio, add a reference to the SmartAssembly.Attributes.dll (located in the %ProgramFiles%\SmartAssembly 6\Attributes folder) in your project.
- add the source code file to your project (SmartAssembly.Attributes.cs for a C# project, or SmartAssembly.Attributes.vb for a VB.NET project). Both of these files are located in the Smartassembly\attributes folder. If you choose this option, you can change the namespace to match your own, simplifying the use of these attributes.
Attributes for Obfuscation
|
Excludes the member from obfuscation. Can be added to assembly, class, delegate, enum, field, interface, method, module, and struct. |
|
Excludes the type definition, as well as all the type's members from obfuscation. Can be added to any type (class, enum, interface, and struct). |
|
Excludes the type definition from pruning. Can be added to any type (class, enum, interface, and struct). |
|
Excludes the type definition, as well as all type's members, from pruning. Can be added to any type (class, enum, interface, and struct). |
|
Does not seal the type. This overrides the option to automatically seal all possible classes. Can be added to any type (class, enum, interface, and struct). |
|
This overrides the control flow obfuscation level set in the SmartAssembly project. When you add this attribute to your assembly, you can set an alternative obfuscation level for 'flagged methods' (methods with the attribute) in the SmartAssembly user interface. Can be added to any class, method, and struct. |
DoNotObfuscateControlFlow |
Does not apply Control Flow Obfuscation. Can be added to any class, method, and struct. |
|
When SmartAssembly obfuscates some members, they may become internal. This can stop other applications from post-processing the obfuscated code. Apply the StayPublicAttribute to ensure that the member remains public after obfuscation. Can be added to any class, enum, and interface. |
Attributes for Automatic error reporting
|
Reports any unhandled exception, which occurs in this method. This is useful for DLLs because it saves you catching exceptions yourself and passing the exceptions to SmartAssembly. Can be added to any method. |
|
When added to any type (class, enum, interface, or struct), prevents that type's fields from being included in error reports. When added to a field, prevents that field from being included in error reports. |
|
Prevents variables from being included in error reports. Can be added to any method. |
(deprecated from SmartAssembly 6.2 onwards) |
Prevents fields from being included in error reports. Can be added to any type (class, enum, interface, and struct). |
C# code sample
[DoNotSealType()]
public class MyClass
{
[DoNotPrune()]
[DoNotObfuscate()]
public void CalledOnlyByReflection()
{
}
[DoNotPrune()]
public string MyPropertyCalledByReflection
{
get
{
return "hello world";
}
}
public void DoSomething([DoNotPrune()] string myString)
{
}
[ReportException()]
[ObfuscateControlFlow()]
public void DoSomethingDangerous()
{
}
public MyClass()
{
}
[DoNotPrune()]
public MyClass(string[] args)
{
//Called only by Reflection
}
}
[DoNotPruneType()]
[DoNotObfuscateType()]
public class OtherClass
{
}
VB.NET code sample
<DoNotSealType()> _
Public Class Class1
<DoNotPrune(), DoNotObfuscate()> _
Public Sub CalledOnlyByReflection()
End Sub
<DoNotPrune()> _
Public ReadOnly Property
MyPropertyCalledByReflection()
Get
Return "hello world"
End Get
End Property
Public Sub DoSomething(<DoNotPrune()> ByVal MyString As String)
End Sub
<ReportException()> _
<ObfuscateControlFlow()> _
Public Sub DoSomethingDangerous()
End Sub
Public Sub New()
End Sub
<DoNotPrune()> _
Public Sub New(ByVal args As String())
REM Called only by Reflection
End Sub
End Class
<DoNotPruneType(), DoNotObfuscateType()> _
Public Class OtherClass
End Class
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