Exception Hunter
Latest version: 3.0
Knowledge Base
Creating an assembly for an ASP .NET 2.0 web application (version 1)
Category: How do I?
Date: 27 Aug 2009
Product: Exception Hunter
ASP .NET applications do not produce assemblies (DLLs) as part of the build process since ASP .NET 2.0. How is it possible to create an assembly from my web application so that it can be analyzed by Exception Hunter?
By default, ASP .NET 2.0 compiles a web application at the first request and creates an assembly DLL in the Temporary ASP .NET files folder of the .NET Framework installation. The name and location of this cached file will vary, however, making it difficult to locate. It is possible to pre-compile an ASP .NET web application manually, using a stand-alone utility distributed with the .NET Framework. In order to convert an ASP .NET web application into a DLL assembly that can be loaded by Exception Hunter, use %systemroot%\microsoft.net\framework\v2.0.50727\aspnet_compiler.exe
aspnet_compiler -v /MyVirtualDir -p "c:\inetpub\wwwroot\MyApp" -d -c "c:\MyExceptionHunterAssemblies"
The command above will work regardless of the website that the web application is configured to run on, will completely rebuild the assembly, include the inline ASP .NET code, and output any assemblies into the 'MyExceptionHunterAssemblies' folder for a web application accessible via the /MyVirtualDir virtual directory in IIS which resides on the local hard disk in the 'c:\inetpub\wwwroot\MyApp' folder.
For more information on the usage of the ASP .NET Compiler, please see http://msdn2.microsoft.com/en-us/library/ms229863(VS.80).aspx
Document ID: KB200712000205 Keywords: Exception,Hunter,ASP,2.0,aspnet_compiler
Was this article helpful?
Exception Hunter
- Log files
- Type forwarding, .NET 4 and WPF support in Exception Hunter 3.0
- Viewing methods that throw a particular type of exception
- Creating an assembly for an ASP .NET 2.0 web application (version 1)
- Method analysis causing "application configuration is incorrect" errors
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
Exception Hunter
- Activating your products
- Activating your products
- Getting help offline
- Exception Hunter release notes - version 2.xx
- Exception Hunter release notes - version 3.xx
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 Exception Hunter