Does anybody has complete documrntation for determining how can we do source validation for any given application. 
A step by step  procedure to follow while validating a source

4 Comments   [ + ] Show Comments


  • could you please be more precise , not sure what you mean?
  • I need the Standards steps to follow to do the Source Validation for an Application to justify whether it is a Legacy application or Vendor Application or a mixer of steup.exe and .msi or a source with drivers. And what method we follow to package the application it may be Repackager or Transform(to MST)
  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
  • There really isn't any kind of standards to validate, and no way to justify something - it either is or is not an MSI, a Legacy app or something with drivers.

    Are you talking about how to justify something getting packaged or removing/replacing it in the production environment? That would be a Rationalization project. The output of that project would determine what is packaged.

    The methodology of packaging would be determined by the source files.
  • Kran, Are you a repackager ?
Please log in to comment

Community Chosen Answer


There is no step by step procedure for it. Every application is different so the approach to validate the installation will be different for each application. You would need to have basic concepts for application packaging and experience in packaging to do it.


~Piyush Nasa

~My Blog:

Answered 10/17/2013 by: piyushnasa
Red Belt

  • Yeah thats right, I am a beginner in learning App Packaging so wanting for the standard docs which help me through.
    I have some basic idea and packaged some small applications.
    Piyush help me and do the need ful
Please log in to comment


Answered 10/18/2013 by: pjgeutjens
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity