SQL Packager
Latest version: 6.4
Knowledge Base
Creating executables that use the .NET 2.0 runtime (version 5)
Category: How do I?
Date: 05 Jun 2009
Product: SQL Packager
Versions: 4,5
Fix versions: SQL Packager 5.4 and up compile against .NET Framework 2.0.
SQL Packager executable output is compiled to target specific versions of the .NET Framework. You may want to change the versions that the Packager executables are targeted towards.
SQL Packager has been built on .NET Framework 1.1, so by default it will create executables that run on .NET 1.1. Note that this does not mean .NET 1.1 is required explicitly because the package executable will run error free on .NET Framework 2.0.
If .NET Framework 2.0-targeted assemblies are a requirement, it is possible to output a package executable as a C# project, then open the project with Visual Studio 2005 and use the conversion wizard to convert the project to .NET 2.0.
If you want each and every package output to run on .NET 2.0 without having to load and convert it, this is not possible. Although SQL Packager has a 'template' project that it uses to create the package output, the template cannot be converted to a Visual Studio 2005 project. Once this has been done, the resource files which are produced by SQL Packager will be in .NET 1.1 format and can't be understood by .NET 2.0.
Any modifications to a package involving changing the .NET runtime version can only be done against the packager output project and not the packager code template project.
Document ID: KB200707000077 Keywords: Packager, Framework, 2005, C#, project, code, template, convert
Was this article helpful?
SQL Packager
- Logging and log files
- Package executable cannot load zlib1.dll
- Creating executables that use the .NET 2.0 runtime (version 5)
- Creating a database for an earlier version of SQL Server
- SQL comparison and synchronization automation capabilities
- Reseed applying "incorrect" identity values
- "Value cannot be null" error creating data script
- DEFAULT_SCHEMA clause cannot be used with a Windows group
- Package created from script always creates database
- SQL Packager not keeping the READ_COMMITTED_SNAPSHOT SQL option ON
- Setting the Database Options for a New Database
- Package execution failing because the login already has an account under a different user name
- Invalid SQL when synchronizing an index to a scripts folder when data compression is specified
- Logging and log files
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
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
SQL Packager
- Activating your products
- Activating your products
- Getting help offline
- SQL Packager release notes - version 6.xx
all SQL products
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 SQL Packager