The diagnostic report generated by the .NET parse shows one of the following messages: 

• Missing or Erroneous References 
• (file load error) 
• (indirectly referenced) 
• Missing or Erroneous Types 

For WinForms localization, not only the data stored in the resources but also the code of the source assembly and other assemblies might be relevant. It is not always possible or desirable to include the full deployment of the application to the localization kit. 

As a result, localization relevant data might be missing in the localization process. For practical reasons Passolo cannot simply reject such project, but must try to provide the best localization experience possible. Most of the issues which occur during localization are based on missing data, which might be base forms, controls (third party libraries), properties used by controls, or values which cannot be processed. 

Software engineers and project managers should carefully analyze the information about missing references or types to make sure that adequate localization are created. 

Missing or Erroneous References

Under this section are listed assemblies which are referenced by the assembly to be localized. The referenced assemblies might contain user controls or other localization relevant data. Some of the assemblies are indirectly referenced (used by another missing assembly), or only referenced through data stored in resources. These assemblies can be identified by the (indirectly referenced) info. 

It is also possible that the assembly is in the scope of Passolo (project path, source path, ...), but cannot be loaded. These assemblies can be identified by the (file load error) info. There are many reasons why assembly cannot be loaded and development must be involved to fix such problems. Typical reasons are: 

• Security setting of .NET does not allow loading of the assemblies. Checking the file option and .NET security setting can solve this issue. 
• The assembly depends on other assemblies which are not present. 
• The assembly depends on a Microsoft .NET Framework which is not installed. 
• The assembly requires other files, configurations, or settings to run successfully.

Missing or Erroneous Types

Under this section all types are listed which are relevant for the localization but could not be loaded because the assemblies containing the types are not present or cannot be loaded. This information is particularly useful for developers to track issues or to fine tune the localization kit.

More information about the impact of missing types can be retrieved if code generation is enabled in the diagnostic report. SDL Passolo will then dump the content of InitializeComponent(), which is the code that must be analyzed for visual rendering. All code lines affected by the missing types are highlighted. 

The impact on missing types depends on the architecture of the application to be localized. Here are some of the impacts:

• Passolo cannot determine the base type of a WinForms. This can be critical if the base form already contains controls. Also Passolo has to guess if a WinForms or a user control is to be processed. 
• Passolo cannot determine controls used in a WinForms. This can be more or less critical depending on the dynamic behavior of the missing control type. In the designer Passolo tries to substitute the unknown controls by a simple panel. 
• Localization relevant cannot be processed if the underlying type cannot be determined. This is the less critical case.

Note 
In the settings dialog of the .NET parser you can specify how Passolo should deal with these issues (Issue Handling).

The .NET parser optionally generates a diagnostic report with issues detected during parsing.