The .net assemblies need to be packaged along with the source code before performing the .net analysis.
The package should be done as follows:
- Open DMT.
- Add new package
- Select Automated extraction of required .net assemblies
- Defining a package on C:\Windows\assembly does not extract the system assemblies. Use the below instructions instead.
- Choose C:\Windows\Microsoft.NET\Framework\v4.0.30319. Choosing between 32 & 64 bits is mostly a non issue. What matters is the interface, and the interface is the same in both cases. But it is important to choose a folder where you will have only one version of system libraries. If you don't, then for some projects a version might be selected, for other projects, another version, which may lead to ambiguities later.
- So, if you know none of the project requires a version more recent than xxx, just select C:\Windows\Microsoft.NET\Framework\v"xxx"
- If you don't know (or don't care), just select: C:\Windows\Microsoft.NET\Framework\v"latest available" Which will most of the time be: C:\Windows\Microsoft.NET\Framework\v4.0.30319
- Package it
Check the required dll of other version need to be remediated, follow the below page which also explains how to remediate the alerts: Delivery Manager Tool - Information - Project Remediation - Remediate packaging alerts
Find an example below which explains how to remediate if you have missing assemblies, or if you have missing source files.
In the below screen shot we have 18 alerts related to missing assemblies and source files.
We have the missing assemblies mentioned below under the package content
Since the missing assemblies if of .Net framework version 4, so we need to package the .Net assmeblies of framework 4.
In DMT we have to select the automated extraction of required .Net assemblies.
After packaging we can see that in the .NET assemblies package, in the package configuration tab, there is the list of all the alerts detected, and in the package content tab the list of assemblies that found to remediate these alerts.
Then, after packaging we see that there are no more alerts related to missing assemblies in the DMT.
Now, in the below screen shot you could see there is a third party assembly which is missing.
We need to create another package and provide the path of the third party assembly.
After packaging the third party assembly the package is fine with no more DMT alerts, please find the screen shot below.