Sign in
Microsoft.com
 
System Center Configuration Manager TechCenter
 
 
 
System Center Configuration Manager TechCenter > System Center Configuration Manager Forums > Configuration Manager SDK > Missing DDRPropertyFlagsEnum for "Full Replace" in SMSResGen
Ask a questionAsk a question
Search Forums:
 

QuestionMissing DDRPropertyFlagsEnum for "Full Replace" in SMSResGen

  • Tuesday, November 03, 2009 8:10 PMMatt Broadstock Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hello all, I am writing a VB.Net app to create DDRs for SMS/SCCM.  I am trying to follow good coding practices by using "Option Strict On" but the SMSResGen object is causing some issues. Basically, the "Full Replace / Low Confidence" bit isn't available when enumerating DDRPropertyFlagsEnum. I have an array that I would like to REPLACE with new info rather than appending to it.

    I could probably disable 'Option Strict On' and just pass the integer 17 instead of "SMSRSGENCTLLib.DDRPropertyFlagsEnum.ADDPROP_ARRAY Or MISSINGENUMPROP" but it seems a bit silly to have to do this.  I know that SMS/SCCM itself generates DDRs with this flag set so it is a bit disappointing that I cannot do it with SMSResGen without getting rid of 'Option Scrict On'.

    Any suggestions?

    References to what I am seeing:
    http://msdn.microsoft.com/en-us/library/cc145875.aspx
    http://myitforum.com/cs2/blogs/rzander/archive/2009/05/15/ddrpropertyflagsenum-update.aspx
     

All Replies

  • Tuesday, November 17, 2009 1:58 AMJim DempseyMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    The product itself uses the MP API rather than SMSResGen.  Have you looked at using the MP API?
     
  • Tuesday, November 17, 2009 8:30 PMMatt Broadstock Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Nope Jim, I sure haven't. I appreciate the heads up!

    Looks like there are a lot more potential issues to consider...at least with Native Mode SCCM. I may just move forward with the SMSResGen method for now and work on moving to the MP API on the side.

    Thanks again for pointing me towards another solution. I assume that using the MP API is the more preferred method for getting DDR-type info into the database then?