none
Signed files RRS feed

  • Question

  • Our product includes Microsoft.VC80.ATL, Microsoft.VC80.CRT and Microsoft.VC80.MFC; these files are unsigned.

    When certifying for Vista there was an email address and waver provided for files such as these.


    What is the procudure for Server 2008 certification?


    Thanks,

    Charlie
    Tuesday, October 23, 2007 2:51 PM

Answers

  •  

    Hi Charlie,

     

    You, the ISV, should document these 3rd party files, when submitting your submission package to the Testing Authority. Otherwise these will be considered a failure until documentation is received and reviewed, delaying the process of Certification. It is better to document the 3rd party files from the start to avoid this.

     

    We will include this information in documentation to help avoid delays and misunderstandings.

     

    No waiver needed here.

     

    Hope this helps,

     

     

    Wednesday, October 24, 2007 4:28 AM

All replies

  •  

    Hi Charlie,

     

    You, the ISV, should document these 3rd party files, when submitting your submission package to the Testing Authority. Otherwise these will be considered a failure until documentation is received and reviewed, delaying the process of Certification. It is better to document the 3rd party files from the start to avoid this.

     

    We will include this information in documentation to help avoid delays and misunderstandings.

     

    No waiver needed here.

     

    Hope this helps,

     

     

    Wednesday, October 24, 2007 4:28 AM
  • We have files like AjaxControlToolkit.dll, Interop.WindowsInstaller.dll, log4net.dll and zedgraph.dll. Is the policy that if we document these files and report that they aren't ours we can get our software certified? How do you know that these 3rd parites can be trusted?

    Monday, November 26, 2007 3:00 PM