Health analyzer rule registration requires that the {0} assembly be registered in the global assembly cache.

When developing custom health rules, you might bump into this error:

Health analyzer rule registration requires that the {0} assembly be registered in the global assembly cache.

Odd, because when you check the GAC you see that your .dll gets registered correctly.

The only solution step I’ve found so far is the following:

  1. Retract your solution fully, either by using Visual Studio, the Central Administration or PowerShell
  2. Change the site URL of your project to another, valid URL (it has to differ from the last deployment)
    change site url project
  3. Deploy

This process can be quite cumbersome to do every time you wish to redeploy. There’s a workaround though, you can always use CKSDev‘s Quick Deploy commands which don’t seem to be affected by this weird behaviour.

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s