http://www.systemcentercentral.com/BlogDetails/tabid/143/indexId/77909/CommentRSS/1/Default.aspx en-us Copyright 2009 System Center Central All Rights Reserved. Thu, 17 May 2012 06:53:24 GMT Unfortunately the XSD verification failed error is pretty useless since one can't see the actual xml behind it. And I don't know what caused the error either, could be anything.
Maybe you ran it with a wrong parameter or something.]]> Thu, 19 Jan 2012 21:19:40 GMT http://www.systemcentercentral.com/BlogDetails/tabid/143/indexId/77909/Default.aspx#comment-1570
BTW, I ran into a couple of odd issues - not sure if it was a PowerShell bug or something with the script, but after I ran the script with a number (100+) rules to create, it threw an exception

"Exception calling "AcceptChanges" with "0" argument(s): "XSD verification failed for management pack. [Line: 9410, Position: 13]"".

I added a $MP.Verify() and an export-managementpack line to the script and looked at the XML - verification passed and I did not see anything odd in the XML. Then I closed the powershell window, opened a new one and it ran OK. There were two rules out of 450+ that it totally refused to do, even with my little 'song and dance'... Either way, creating two rules manually is a LOT better than creating 479 rules manually... :) So thank you again.]]> Thu, 19 Jan 2012 18:04:57 GMT http://www.systemcentercentral.com/BlogDetails/tabid/143/indexId/77909/Default.aspx#comment-1569
Added a check in the AddReference functions. In case you target a class from the MP in which you write to, it would try to add a reference for it which won't work.

It checks now if the ReferenceMP name is the Target MP name. If it is, it just exits out of the subfunction.]]> Wed, 08 Sep 2010 13:52:04 GMT http://www.systemcentercentral.com/BlogDetails/tabid/143/indexId/77909/Default.aspx#comment-909