When you use error reporting, feature usage reporting, and/or the lower levels of obfuscation*, SmartAssembly needs to store information about your builds in a database in order for those features to work.
In earlier versions of SmartAssembly, it would store the information in a .mdb database by default. However, since SmartAssembly 6.11 runs as AnyCPU and mdb connections are not possible with 32-bit processes, SmartAssembly now needs to store the information in a SQL Server database.
If a SQL Server database is not configured and you have error reporting, feature usage reporting, and/or the lower levels of obfuscation enabled, then you may encounter the following build error:
To resolve this, please go to Tools>Options>Reports database options and specify a SQL Server database for SmartAssembly to use.
--
* The lower levels of obfuscation refers to any of the following options:
Types/Methods Name mangling:
- I want to obfuscate using only ASCII characters.
- I want to obfuscate using only Unicode unprintable characters.
Fields Name Mangling:
- I want to use a one-to-one renaming scheme.
In earlier versions of SmartAssembly, it would store the information in a .mdb database by default. However, since SmartAssembly 6.11 runs as AnyCPU and mdb connections are not possible with 32-bit processes, SmartAssembly now needs to store the information in a SQL Server database.
If a SQL Server database is not configured and you have error reporting, feature usage reporting, and/or the lower levels of obfuscation enabled, then you may encounter the following build error:
To resolve this, please go to Tools>Options>Reports database options and specify a SQL Server database for SmartAssembly to use.
--
* The lower levels of obfuscation refers to any of the following options:
Types/Methods Name mangling:
- I want to obfuscate using only ASCII characters.
- I want to obfuscate using only Unicode unprintable characters.
Fields Name Mangling:
- I want to use a one-to-one renaming scheme.