SmartAssembly - 6.7
Setting up a custom web server for reporting - SmartAssembly
This feature is available in SmartAssembly Professional only.
You can set up a custom web server for error reporting and feature usage reports. This changes SmartAssembly, so that reports are sent to a web service running on your own server, rather than the default one operated by Red Gate.
Most users of SmartAssembly do not need a custom web server. However, if you build applications for internal use in your company, and your company has a firewall that would prevent communication with the Red Gate-hosted web service, you will need to use a custom web server.
Note that the custom web server is distinct from the SQL server. The custom web server hosts the web service to which reports are sent before they are downloaded to your SQL server or .mdb file:
The role of the web service for error reports:
|
|
The role of the web service for feature usage reports:
|
To set up a custom web server:
- Download the zip archive containing the custom web service files.
- Create a directory for SmartAssembly on your web server.
For example, http://www.myWebServer.com/saWebServices/. - Copy the three .asmx files (Login.asmx, Reporting.asmx, and UploadReportLogin.asmx) and the Web.config file from the zip archive to the directory you just created.
- Copy ClientAccessPolicy.xml into the root directory of your web server.
- Open the /bin/ directory within the .zip archive.
- Copy SmartAssembly.WebService.dll and log4net.dll into the /bin/ directory of your web server.
If the /bin/ directory does not already exist, create it in the root directory of your web server.
- Verify that the first part of the setup is correct by calling the web service from your browser: http://www.myWebServer.com/saWebServices/UploadReportLogin.asmx.
Confirm that you are displaying the standard web service welcome page.
- Create a folder on the web server, which is not publicly accessible. This folder is where reports are stored when they are uploaded. The web service must have write access to the folder and its sub-folders. In the example below, the physical path for the reports folder is c:\MyCustomWebServer\. Edit the server's web.config file to add this location:
<configuration>
...
<appSettings>
<add key="ReportsFolder" value="c:\MyCustomWebServer\" />
</appSettings>
...
</configuration>
- In SmartAssembly, click Options. Under Custom web server, select I want to use my own web server. Enter the URL of the directory which contains the web service.

- Test your new web service.
Troubleshooting the custom web service
The custom web service logs any errors that occur by default. The error logs are stored on your web server in the directory where the SmartAssembly web service was installed.
The logs are created using log4net. For information about how to configure logging, see Configuration in the log4net manual.
Disabling error logging
If required, you can disable error logging in the custom web service. To do this:
- On the web server, navigate to the directory where the SmartAssembly web service was installed.
- Open Web.config in an XML editor.
- Change
<level value="ALL">to<level value="OFF">.
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