Commented Unassigned: Fails to add references to assemblies with certain character sequences [3465]

Filenames with URL escaping sequences gets interpreted incorrectly.

Example: App%2a.dll get interpreted as App*.dll and fails.

Repro:

Create Nuget package with assembly called 'App%2a.dll'.
Packaging works fine.
Install the package to a project.
The reference is added to the project, but VS reports the file cannot be found. Yet it is visible in the packages folder.

Note: Similar behavior in MSBUILD was a regression in .NET 4.0.
https://connect.microsoft.com/VisualStudio/feedback/details/551765
Comments: Reported the CSC bug: https://connect.microsoft.com/VisualStudio/feedback/details/792525/csc-fails-to-open-a-referenced-assembly-if-the-filename-contains-certain-url-escaping-sequences