The extern alias 'xxx' was not specified in a /reference option

问题:

I have two assemblies that unfortunately define the same type in the same namespace. I'm trying to use a an extern alias to work around the problem. In the Visual Studio IDE I have set the "Aliases" property of the reference to my alias. This is supposed to change the C# compiler command line to be something like this:

/reference:MyAlias=MyAssembly.dll 

But it doesn't actually do that. The Visual Studio IDE seems to just ignore the Aliases property setting on the reference. So when I go and add the line extern alias MyAlias; at the top of my C# code file I get the error that the alias was not specified in a /reference option to the compiler. I can't figure out what I am doing wrong. Any ideas?

回答1:

I have the same problem and I was able to reproduce the issue.

It turns out reference aliases are ignored on projects containing xaml files which has an xmlns definition to the output assembly like xmlns:local='clr-namespace:TestProject'.

If you think this is your case as well, please vote up my bug report at Microsoft Connect.

EDIT: There is a suggested workaround in the link above which requires editing the project file manually. In order for this to work, I had to give full path of the assembly. Add the following instructions to the end of your project file:

<Target Name="solveAliasProblem" > <ItemGroup>  <ReferencePath Remove="FullPath.dll"/>  <ReferencePath Include="FullPath.dll">     <Aliases>ourAlias</Aliases>  </ReferencePath> </ItemGroup> </Target> <PropertyGroup>     <CoreCompileDependsOn>solveAliasProblem;$(PrepareResourcesDependsOn)</CoreCompileDependsOn> </PropertyGroup> 

回答2:

An update: It is a bug. It will be fixed in .Net 4.5.

As seen on the Microsoft Connect bug report.

回答3:

Brian, I had the same problem as you and I figured out how to fix it.

I would do the same thing as you:

1. Use the properties window to change the alias for the assembly from 'global' to 'MyAlias'
2. At the top of the file where the aliased assembly is used, put extern alias MyAlias. This must be before any using statements.
3. Use the alias prefix to use the namespace you want, for example using MyAlias::MyNamespace.

And I would still get the error. After screwing around a bit, I figured out that the way to fix it is to set the referenced dll to a dll that is outside of the solution you are working in. Once I did that, the error message we were both seeing went away, and I was able to continue working on my project.

I hope that helps, happy coding!

回答4:

Working for me in VS2008 using these steps:

1. Use the properties window to change the alias for the assembly from 'global' to 'MyAlias'
2. At the top of the file where the aliased assembly is used, put extern alias MyAlias. This must be before any using statements.
3. Use the alias prefix to use the namespace you want, for example using MyAlias::MyNamespace.

回答5:

If you install .Net Framework 4.5 it will update your MSBuild to Microsoft (R) Build Engine version 4.0.30319.17929 which fixed this issue for my team.

Download .Net Framework 4.5:
http://www.microsoft.com/en-us/download/details.aspx?id=30653

回答6:

I had exact similar issue, looks like when you clean your solution and build the project, first time MSBuild ignores references and gives error (may be it does not have some assemblies built yet with the references specified), however on second try of the build, it works.

回答7:

I had the same problem and it was resolved by doing the following.

Go to properties window of the assembly with the conflict and change the Aliases property from 'global' to 'X' (X - your alias name)

Hope this helps.

回答8:

Set the project's target framework to .NET 4.5.1.

回答9:

myprojectHad the same issue, but the above solutions didn't work my project file looked like

    <Reference Include="AntiXSSLibrary" Condition="'$(TargetFrameworkVersion)' == 'v4.0' or '$(TargetFrameworkVersion)' == 'v4.5'">   <HintPath>..\Dependencies\Third-party\.net 4\AntiXSSLibrary.dll</HintPath>   <Aliases>antixss</Aliases> </Reference> <Reference Include="AntiXssLibrary">   <HintPath>..\..\lib\myproject\AntiXssLibrary.dll</HintPath>      </Reference> 

Adding the alias the actual project dll worked. So

    <Reference Include="AntiXSSLibrary" Condition="'$(TargetFrameworkVersion)' == 'v4.0' or '$(TargetFrameworkVersion)' == 'v4.5'">   <HintPath>..\Dependencies\Third-party\.net 4\AntiXSSLibrary.dll</HintPath>   <Aliases>antixss</Aliases> </Reference> <Reference Include="AntiXssLibrary">   <HintPath>..\..\lib\myproject\AntiXssLibrary.dll</HintPath>   <Aliases>antixss</Aliases> </Reference> 

回答10:

I had the same problem and I finally found that the .csproj file has target version of 4.5 while the dll which I faced the problem with is targeted to 4.5.2.

I changed my .csproj file target version to 4.5.2 and got successful build.

回答11:

I had the same problem, and I could solve it only when I changed the target version to 4.6.1. The versions 4, 4.5, 4.5.1, or 4.6 did not help.

文章来源: The extern alias 'xxx' was not specified in a /reference option