While performing a Microsoft Platform Ready test for Windows Sever 2012 R2 we encounter a failed test, caused by missing Company Information in the DLL files of the Fluent Validation files. I have already taken actions like signing all DLL file with a document signing certificate.
I'm an expierienced software packager, without any knowledge about building DLL files or compiling sources. How can i apply a Company Name to the Fluent Validation DLL files? Is there a possibility to apply a Company Name to a new version?
Hopefully someone can tell me the easyest way to complete my job.
The Microsoft Platform Readiness Test tells me this:
Action: Add valid file information to owned binaries.
-Binaries not built by product group or company can be considered 3rd party.
-Binaries without proper file version information will fail this test case and require waiver.
-Interop files do not provide file information by design, and are excluded from this list.
===
05/27/2014 16:44:10 :: Binary list
C:\Program Files\Level-7 Connect\website\bin\de\FluentValidation.resources.dll does not have a valid "Company name" property.
Comments: Hi Jeremy, I think you're right. I will ask a developer to compile these DLL files for me. However, specifyng a Company Name in a DLL file is such a basic thing that i'm keep wondering why it isn't filled. Reading the requirements of a platform test it look likes very easy to have a Company and Product name in the properties of your DLL and EXE files. But it's a hard job to work around such a issue if it isn't filled in. What's the problem to fill the Company Name with something like Fluent to comply with Microsoft's Platform Requirements in the future? Thanks for your help!
I'm an expierienced software packager, without any knowledge about building DLL files or compiling sources. How can i apply a Company Name to the Fluent Validation DLL files? Is there a possibility to apply a Company Name to a new version?
Hopefully someone can tell me the easyest way to complete my job.
The Microsoft Platform Readiness Test tells me this:
Action: Add valid file information to owned binaries.
-Binaries not built by product group or company can be considered 3rd party.
-Binaries without proper file version information will fail this test case and require waiver.
-Interop files do not provide file information by design, and are excluded from this list.
===
05/27/2014 16:44:10 :: Binary list
C:\Program Files\Level-7 Connect\website\bin\de\FluentValidation.resources.dll does not have a valid "Company name" property.
Comments: Hi Jeremy, I think you're right. I will ask a developer to compile these DLL files for me. However, specifyng a Company Name in a DLL file is such a basic thing that i'm keep wondering why it isn't filled. Reading the requirements of a platform test it look likes very easy to have a Company and Product name in the properties of your DLL and EXE files. But it's a hard job to work around such a issue if it isn't filled in. What's the problem to fill the Company Name with something like Fluent to comply with Microsoft's Platform Requirements in the future? Thanks for your help!