
06-30-2008, 06:19 AM
|
 |
Regular 'Geeker
Offline
Location: St. Auggie, FL
|
|
Join Date: Jul 2007
Posts: 322
Reputation: 147  
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
|
Re: Development: Let's Compare our ProvXML's!
http://msdn.microsoft.com/en-us/library/ms889522.aspx
Quote:
Microsoft recommends that you use a three-digit number in the name of your .provxml files in ROM, such as mxip_opr_100, mxip_opr_200, mxip_opr_300, so that there is an adequate number of ordinals to identify successive versions of the file.
|
I usually do a mxipupdate_geoff_100.provxml, mxipupdate_geoff_101.provxml, etc
|