We're updating the issue view to help you get more done.Learn more

Also import PDB-files in addition to dll files in the installer-assembly area

When users install our modules and run into an error, they have trouble reporting what exactly the error is, because the stack in the events-module is not really helpful.

BUT there is a solution: if we deploy the built PDB files from visual studio together with the .DLL files, then the error messages include exact line numbers. This is very helpful in fixing issues.

PDB files have no security implication, they are like JS-map files and only help the error-system inform the user about the code-line where something happened.

Because of this, it's important that we can also include the PDB files in the installation. Unfortunately as of now, the installer blocks this extension - telling the user it's unsafe.

We should add pdb-files to the list of allowed files in the assembly installer to aid in better user error-feedback.

The fix is to replace this

/// -----------------------------------------------------------------------------
/// <summary>
/// Gets a list of allowable file extensions (in addition to the Host's List)
/// </summary>
/// <value>A String</value>
public override string AllowableFiles
{
get

{ return "dll"; }

}

with this

/// -----------------------------------------------------------------------------
/// <summary>
/// Gets a list of allowable file extensions (in addition to the Host's List)
/// </summary>
/// <value>A String</value>
public override string AllowableFiles
{
get

{ return "dll, pdb"; }

}

on lines 104 to 115 in the AssemblyInstaller.cs - linked here: https://github.com/dnnsoftware/Dnn.Platform/blob/115ae75da6b152f77ad36312eb76327cdc55edd7/DNN%20Platform/Library/Services/Installer/Installers/AssemblyInstaller.cs#L104-L115

Status