In the manifest, you're able to specify DLL's that should be installed with an extension. This tells the installer what they are, and that they should be found in the installation package.
It's currently optional to include a version number for the DLL, which is okay since it introduces flexibility for multiple use cases. An example of both scenarios is below.
<component type="Assembly">
<assemblies>
<assembly>
<path>bin</path>
<name>EntityFramework.dll</name>
<sourceFileName>bin\EntityFramework.dll</sourceFileName>
</assembly>
<assembly>
<path>bin</path>
<name>ImageResizer.dll</name>
<sourceFileName>bin\ImageResizer.dll</sourceFileName>
<version>4.0.0</version>
</assembly>
</assemblies>
</component>
The EVS scan should create a warning message for each DLL that does not include a version number. It's not an error message, but it's definitely something for a website owner to be aware of before installing an extension.
In the manifest, you're able to specify DLL's that should be installed with an extension. This tells the installer what they are, and that they should be found in the installation package.
It's currently optional to include a version number for the DLL, which is okay since it introduces flexibility for multiple use cases. An example of both scenarios is below.
The EVS scan should create a warning message for each DLL that does not include a version number. It's not an error message, but it's definitely something for a website owner to be aware of before installing an extension.