In this post, I want to demonstrate how easy it is to create a class using Visual Studio Authoring Extensions. This is in response to some blog posts out there (like this one and this one) that describe this task as “difficult” outside of a 3rd party tool. It’s actually extremely easy!
Let’s take a look at how easy it is to create a class using VSAE.
<TypeDefinitions>
<EntityTypes>
<ClassTypes>
<ClassType ID="ToolAndDie.Class.Computer" Abstract="false" Accessibility="Public" Base="Windows!Microsoft.Windows.ComputerRole" Hosted="true" Singleton="false" />
</ClassTypes>
</EntityTypes>
</TypeDefinitions>
Yep – it’s really that easy to create a class. Now all you need to do is discover it, and it’s actually just as easy to do that, especially if you’re using the registry.
My suggestion is, if you are new to authoring management packs, just take the leap into VSAE. There is no benefit in using 3rd party tools, like MP Author by Silect. I say that because, you’re not really picking up a new skillset by using these types of UI tools – however, you do pickup a new skillset that can be useful in other areas of your job by learning the language (XML).
There is a learning curve to everything – make the wise choice for your career.
Seems like a lot of typing using your method. When can I start to author using google glass? Just kidding. Nice summary, keep up the good work.
Why is there not a like button!?!
There is! And someone liked it!
Hi Jonathan.
Hope all is well. Curious to know if you ever worked on Windows Service Monitoring , similar to what was done with Scom2007 where we could add schedule to service monitor.
Thanks,
Fahim
Yes. It has not changed from SCOM 2007.