Upgrading SmartAssembly version 4.x to version 5

Date: 7/26/2010
Product: SmartAssembly

SmartAssembly, formerly known as {SmartAssembly}, was acquired by Red Gate Software Ltd. in the summer of 2009. The last release of {SmartAssembly} by its previous owner was version 4.2. Red Gate released SmartAssembly version 5.0 in June 2010.

In most cases, {SmartAssembly} version 4 project files will work fine with SmartAssembly version 5. This Knowledge Base article describes a small number of issues which upgrading users might want to be aware of.

{SmartAssembly} 4 serial key does not work with SmartAssembly 5

Problem: Customers who purchased {SmartAssembly} 4 are entitled to a free upgrade to SmartAssembly 5 but if you try to upgrade to SmartAssembly 5, your existing {SmartAssembly} 4 serial key will not work.

Cause: SmartAssembly's serial keys were integrated with the Red Gate licensing system from version 5.0. Old version 4 serial keys are not recognised by the Red gate licensing server.

Solution: Customers who are eligible for the free upgrade were sent an email in July 2010 with a new SmartAssembly 5 serial key. Please contact Red Gate support if you did not receive the email.

Error reports are sent to a different server

Problem: You cannot find error reports submitted by users. You do not use a custom web server.

Cause: From version 5, error reports are sent by default to a server operated by Red Gate. The old reports server will remain operational for a limited time so that you can still receive errors reported by versions of your application built with {SmartAssembly} version 4.3 and earlier. You cannot use that server to receive reports for applications built with SmartAssembly 5.0 and later.

Solution: To download error reports from versions of your application which were built against {SmartAssembly} version 4 you must use {SmartAssembly} version 4. SmartAssembly version 5.0 can only download reports from the Red Gate server (or a custom server).

Build fails using a strong name key

Problem: Your {SmartAssembly} version 4 project is signed with a strong name key. In SmartAssembly version 5, the project does not build.

Cause: SmartAssembly stores the strong name key internally in an encrypted form, encrypted against the SmartAssembly publisher's public key. Because the publisher's public key changed when Red Gate released SmartAssembly, strong name keys which were encrypted against the previous publisher's strong name key cannot be decrypted.

Solution: On the project settings page, under Strong Name, click Browse for a Key and choose the .pfx file again. This will reload the strong name key and encrypt it against Red Gate's public key.

Was this article helpful?

Search support