Ok, found the culprit - this happens if the library is in GAC. Once you remove the error doesn't happen anymore. On top of that the same error also happens in VS 2008 SP1.
This is not a good workaround though, as when deploying to Sharepoint the library gets installed into GAC and we're back to the same problem.
No comments:
Post a Comment