Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • I have same issue, but this time, it for System.Xaml. How do I resolved this? CREATE ASSEMBLY for assembly 'System.Xaml' failed because assembly 'System.Xaml' failed verification. Check if the referenced assemblies are up-to-date and trusted (for external_access or unsafe) to execute in the database. CLR Verifier error messages if any will follow this message [ : System.Windows.Markup.ValueSerializer::CanConvertToString][mdToken=0x6000002][offset 0x00000000] Code size is zero. Commented Jun 9, 2014 at 3:20
  • not sure about that one. sounds like it could be the same issue. is there any way to verify the version of .net your System.Xaml was built under? if it is different, this could cause the problem. Commented Jun 10, 2014 at 4:25
  • 1
    While this works, the explanation is not entirely correct. Please see my answer for details (which were too much to put into a comment). Commented Sep 1, 2015 at 14:49
  • Or in your SQL viewer such as 'SQL Management Studio' go to 'Help'->'About' to get the .net framework version. Commented Apr 21, 2016 at 16:07
  • @annoying_squid That is not actually correct. The version of the .NET Framework used within SQLCLR is not necessarily the same as what is used by the related tools (SSMS being one of those tools). The Help -> About... in SSMS is the .NET Framework version for SSMS, not SQL Server itself (although they can be the same). Commented Dec 13, 2016 at 6:00