Reporter | Chris Long (Squeeself) |
---|---|
Created | Jan 4, 2012 3:20:11 AM |
Updated | Jan 4, 2012 3:20:11 AM |
Priority | Normal |
Type | Bug |
Fix versions | No Fix versions |
State | Submitted |
Assignee | Unassigned |
Subsystem | Language - XAML |
Affected versions | 6.1 |
Fixed in build | No Fixed in build |
Resharper 6.1 reports an incorrect error when referencing an assembly in XAML where the assembly's name differs from the assembly's original identity. Example:
Original Assembly: WPFToolkit.Extended.dll
In order to disambiguate different versions for different platforms, the filename of the dll was changed to be WPFToolkit.Extended.net35.dll
The assembly was referenced into the project.
Resharper then complains that it cannot resolve symbol 'Microsoft' even though the assembly does contain it. However, if I instead change the assembly reference to read:
which is the original Identity of the assembly, Resharper stops complaining. However, this will NOT compile, since the assembly of that name does not exist in project (or on disk).
Resharper 6.0 did NOT report errors on this code, so this is a new bug in 6.1.
Original Assembly: WPFToolkit.Extended.dll
In order to disambiguate different versions for different platforms, the filename of the dll was changed to be WPFToolkit.Extended.net35.dll
The assembly was referenced into the project.
Bugged XAML
<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:ExtControls="clr-namespace:Microsoft.Windows.Controls;assembly=WPFToolkit.Extended.net35" </ResourceDictionary>
Resharper then complains that it cannot resolve symbol 'Microsoft' even though the assembly does contain it. However, if I instead change the assembly reference to read:
Bugged XAML
xmlns:ExtControls="clr-namespace:Microsoft.Windows.Controls;assembly=WPFToolkit.Extended"
which is the original Identity of the assembly, Resharper stops complaining. However, this will NOT compile, since the assembly of that name does not exist in project (or on disk).
Resharper 6.0 did NOT report errors on this code, so this is a new bug in 6.1.