Rick van den Bosch - Blog

... on .NET, software architecture, software development and whatnot

Recent Posts

Tags

News

  • Live space

    Photo blog

    Follow me at twitter

    Rick  van den Bosch

    LinkedIn profile

    Add to Technorati Favorites

    Disclaimer
    The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

Community

Email Notifications

Blogs I read

Interesting links

Archives

Running code analysis on a custom stsadm command gives errors CA0052 and CA0055

When you want to implement a custom stsadm for SharePoint, all you realy have to do is implement the Microsoft.SharePoint.StsAdmin.ISPStsadmCommand interface. Because I develop on a machine with no SharePoint installed, I (only) copy the assemblies I need to develop locally. For the stsadm command I was working on recently (more on this in a future post) I only needed the Microsoft.SharePoint and Microsoft.Office.Server assemblies. Or at least I thought so...

After implementing the functionality I tried running code analysis, and I got two errors:

CA0052 : No targets were selected.
CA0055 : Could not load AssemblyName.

After trying several ways to fix this, I finally compiled the project on a machine with SharePoint installed. At that point, compiling and running code analysis both worked fine. Code analysis then gave a warning that pointed me to the solution of the problem:

CA2123 : Microsoft.Security : Add the following security attribute to 'ClassName.MethodName(string)' in order to match a LinkDemand on base method 'ISPStsadmCommand.GetHelpMessage(string)':  [SharePointPermission(SecurityAction.LinkDemand, ObjectModel = true)].

Apparently the attribute requires an extra reference. When I copied that assembly (Microsoft.SharePoint.Security) to my non-SharePoint development machine, all worked correctly. FYI: I did add the attribute code analysis suggested by the way.

Leave a Comment

(required) 

(required) 

(optional)

(required)