blocks|key|364147|text|编译友元程序集(不包含InternalsVisibleTo属性的程序集)时，需要使用/out:+compiler开关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364148|编译器需要知道正在编译的程序集的名称，以便确定结果程序集是否应被视为友好程序集。|364149|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You need to use the /out: compiler switch when compiling the friend assembly (the assembly that
does not contain the InternalsVisibleTo attribute). 

The compiler needs to know the name of the assembly being compiled in order to determine if the resulting assembly should be considered a friend assembly.

blocks|key|3156275|text|您是否绝对确定在属性中指定了正确的公钥？请注意，您需要指定完整的公钥，而不仅仅是公钥标记。它看起来像这样：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3156276|[assembly:+InternalsVisibleTo("MyFriendAssembly,
PublicKey=0024000004800000940000000602000000240000525341310004000001000100F73
F4DDC11F0CA6209BC63EFCBBAC3DACB04B612E04FA07F01D919FB5A1579D20283DC12901C8B66
A08FB8A9CB6A5E81989007B3AA43CD7442BED6D21F4D33FB590A46420FB75265C889D536A9519
674440C3C2FB06C5924360243CACD4B641BE574C31A434CE845323395842FAAF106B234C2C140
6E2F553073FF557D2DB6C5")]|code-block|syntax|javascript|3156277|大概是320个十六进制数字。不确定为什么需要指定完整的公钥-可能只使用在其他程序集引用中使用的公钥标记，这样会更容易让人伪造友元程序集的身份。|3156278|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Are you absolutely sure you have the correct public key specified in the attribute?
Note that you need to specify the full public key, not just the public key token. It looks something like:

<pre><code>[assembly: InternalsVisibleTo("MyFriendAssembly,
PublicKey=0024000004800000940000000602000000240000525341310004000001000100F73
F4DDC11F0CA6209BC63EFCBBAC3DACB04B612E04FA07F01D919FB5A1579D20283DC12901C8B66
A08FB8A9CB6A5E81989007B3AA43CD7442BED6D21F4D33FB590A46420FB75265C889D536A9519
674440C3C2FB06C5924360243CACD4B641BE574C31A434CE845323395842FAAF106B234C2C140
6E2F553073FF557D2DB6C5")]
</code></pre>

It's 320 or so hex digits. Not sure why you need to specify the full public key - possibly with just the public key token that is used in other assembly references it would be easier for someone to spoof the friend assembly's identity.

blocks|key|3369159|text|值得注意的是，如果"friend“(测试)程序集是用C%2B%2B/CLI而不是C#/VB.NET编写的，则需要使用以下代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3369160|#using+"AssemblyUnderTest.dll"+as_friend|code-block|syntax|javascript|3369161|而不是项目引用或通常的#using语句。由于某些原因，无法在项目参考UI中执行此操作。|offset|length|style|CODE|3369162|entityMap^0|0|0|B|6|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

It is worth noting that if the &quot;friend&quot; (tests) assembly is written in C++/CLI rather than C#/VB.NET, you need to use the following:
<pre><code>#using &quot;AssemblyUnderTest.dll&quot; as_friend
</code></pre>
instead of a project reference or the usual <code>#using</code> statement. For some reason, there is no way to do this in the project reference UI.

blocks|key|364164|text|您可以使用将为您生成InternalsVisibleTo语法的AssemblyHelper+tool。这是the+link+to+the+latest+version。只需注意，它只适用于强名称程序集。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|364165|entityMap|0|LINK|mutability|MUTABLE|url|http://vkreynin.wordpress.com/2007/12/09/testing-internals-members-with-internalsvisibleto-attribute/|1|http://vkreynin.wordpress.com/2010/05/09/assemblyhelpers-now-works-net-4-assemblies/^0|V|J|0|1H|U|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

You can use <a href="http://vkreynin.wordpress.com/2007/12/09/testing-internals-members-with-internalsvisibleto-attribute/" rel="nofollow noreferrer">AssemblyHelper tool</a> that will generate InternalsVisibleTo syntax for you. Here's <a href="http://vkreynin.wordpress.com/2010/05/09/assemblyhelpers-now-works-net-4-assemblies/" rel="nofollow noreferrer">the link to the latest version</a>. Just note that it only works for strongly-named assemblies.

blocks|key|363715|text|如果您的程序集未签名，但仍然收到相同的错误，请检查AssemblyInfo.cs文件中的以下两行之一：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|363716|[assembly:+AssemblyKeyFile("")]
[assembly:+AssemblyKeyName("")]|code-block|syntax|javascript|363717|如果存在这两行中的一行(或两行)，则属性选项卡仍将程序集显示为无符号，但InternalsVisibleTo属性将具有这些行的程序集视为强有符号的。只需删除(或注释掉)这些行，它就可以很好地为您工作。|363718|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If your assemblies aren't signed, but you are still getting the same error, check your AssemblyInfo.cs file for either of the following lines:

<pre><code>[assembly: AssemblyKeyFile("")]
[assembly: AssemblyKeyName("")]
</code></pre>

The properties tab will still show your assembly as unsigned if either (or both) of these lines are present, but the InternalsVisibleTo attribute treats an assembly with these lines as strongly signed. Simply delete (or comment out) these lines, and it should work fine for you.

blocks|key|364179|text|下面是我用来快速生成此属性的宏。这有点老生常谈，但它是有效的。在我的机器上。当最新的签名二进制文件为/bin/debug格式时。等模棱两可等等。不管怎样，你可以看到它是如何获得密钥的，所以这会给你一个提示。在您的时间允许的情况下修复/改进。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|364180|Sub+GetInternalsVisibleToForCurrentProject()
++++Dim+temp+=+"[assembly:++global::System.Runtime.CompilerServices."+%2B+_
+++++++++++++++"InternalsVisibleTo(""{0},+publickey={1}"")]"
++++Dim+projs+As+System.Array
++++Dim+proj+As+Project
++++projs+=+DTE.ActiveSolutionProjects()
++++If+projs.Length+<+1+Then
++++++++Return
++++End+If

++++proj+=+CType(projs.GetValue(0),+EnvDTE.Project)
++++Dim+path,+dir,+filename+As+String
++++path+=+proj.FullName
++++dir+=+System.IO.Path.GetDirectoryName(path)
++++filename+=+System.IO.Path.GetFileNameWithoutExtension(path)
++++filename+=+System.IO.Path.ChangeExtension(filename,+"dll")
++++dir+%2B=+"\bin\debug\"
++++filename+=+System.IO.Path.Combine(dir,+filename)
++++If+Not+System.IO.File.Exists(filename)+Then
++++++++MsgBox("Cannot+load+file+"+%2B+filename)
++++++++Return
++++End+If
++++Dim+assy+As+System.Reflection.Assembly
++++assy+=+System.Reflection.Assembly.Load(filename)
++++Dim+pk+As+Byte()+=+assy.GetName().GetPublicKey()
++++Dim+hex+As+String+=+BitConverter.ToString(pk).Replace("-",+"")
++++System.Windows.Forms.Clipboard.SetText(String.Format(temp,+assy.GetName().Name,+hex))
++++MsgBox("InternalsVisibleTo+attribute+copied+to+the+clipboard.")
End+Sub|code-block|syntax|javascript|364181|entityMap^0|1E|A|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Here's a macro I use to quickly generate this attribute. Its a bit hacky, but it works. On my machine. When the latest signed binary is in <code>/bin/debug</code>. Etc equivocation etc. Anyhow, you can see how it gets the key, so that'll give you a hint. Fix/improve as your time permits.

<pre class="lang-vb prettyprint-override"><code>Sub GetInternalsVisibleToForCurrentProject()
 Dim temp = "[assembly: global::System.Runtime.CompilerServices." + _
 "InternalsVisibleTo(""{0}, publickey={1}"")]"
 Dim projs As System.Array
 Dim proj As Project
 projs = DTE.ActiveSolutionProjects()
 If projs.Length &lt; 1 Then
 Return
 End If

 proj = CType(projs.GetValue(0), EnvDTE.Project)
 Dim path, dir, filename As String
 path = proj.FullName
 dir = System.IO.Path.GetDirectoryName(path)
 filename = System.IO.Path.GetFileNameWithoutExtension(path)
 filename = System.IO.Path.ChangeExtension(filename, "dll")
 dir += "\bin\debug\"
 filename = System.IO.Path.Combine(dir, filename)
 If Not System.IO.File.Exists(filename) Then
 MsgBox("Cannot load file " + filename)
 Return
 End If
 Dim assy As System.Reflection.Assembly
 assy = System.Reflection.Assembly.Load(filename)
 Dim pk As Byte() = assy.GetName().GetPublicKey()
 Dim hex As String = BitConverter.ToString(pk).Replace("-", "")
 System.Windows.Forms.Clipboard.SetText(String.Format(temp, assy.GetName().Name, hex))
 MsgBox("InternalsVisibleTo attribute copied to the clipboard.")
End Sub
</code></pre>

blocks|key|367112|text|顺便说一句，如果您想轻松地获得公钥，而不必使用sn并找出它的选项，可以下载方便的程序here。它不仅确定公钥，还创建"assembly:+InternalsVisibleTo...“准备好复制到剪贴板并粘贴到代码中的行。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|367113|entityMap|0|LINK|mutability|MUTABLE|url|http://www.davidarno.org/2008/01/15/c-and-friend-assemblies-made-easy/^0|16|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

As a side note, if you want to easily get the public key without having to use sn and figure out its options you can download the handy program <a href="http://www.davidarno.org/2008/01/15/c-and-friend-assemblies-made-easy/" rel="nofollow">here</a>. It not only determines the public key but also creates the "assembly: InternalsVisibleTo..." line ready to be copied to the clipboard and pasted into your code.

blocks|key|3156361|text|我刚刚用InternalsVisibleTo属性解决了一个类似的问题。一切似乎都很正常，我不明白为什么我瞄准的内部类仍然无法访问。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3156362|将键的大小写从大写更改为小写解决了此问题。|3156363|entityMap^0|4|I|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

I just resolved a similar problem with the <code>InternalsVisibleTo</code> Attribute. Everything seemed right and I couldn't figure out why the internal class I was aiming still wasn't accessible.

Changing the case of the key from upper to lower case fixed the problem.

blocks|key|3369259|text|另一个可能的“陷阱”：您在InternalsVisibleToAttribute中指定的友元程序集的名称必须与您的友元程序集的名称完全匹配，如友元程序集的项目属性中所示(在选项卡中)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3369260|在我的例子中，我有一个项目Thingamajig和一个配套项目ThingamajigAutoTests+(为了保护有罪的人而更改了名称)，这两个项目都产生了未签名的程序集。我在Thingamajig\AssemblyInfo.cs文件中适当地添加了属性[assembly:+InternalsVisibleTo(+"ThingamajigAutoTests"+)]，并如上所述注释掉了AssemblyKeyFile和AssemblyKeyName属性。Thingamajig项目构建得很好，但其内部成员顽固地拒绝出现在autotest项目中。|3369261|费尽心机之后，我重新检查了ThingamajigAutoTests项目的属性，发现程序集名称被指定为"ThingamajigAutoTests.dll“。Bingo+-我在InternalsVisibleTo属性中的程序集名称中添加了".dll“扩展名，然后就准备就绪了。|3369262|有时候是最微不足道的事情...|3369263|entityMap^0|D|R|0|D|B|V|K|3I|1K|5C|F|5S|F|6A|B|0|D|K|2E|I|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|18|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|M|$]]

Another possible "gotcha": The name of the friend assembly that you specify in the <code>InternalsVisibleToAttribute</code> must exactly match the name of your friend assembly as shown in the friend's project properties (in the Application tab).

In my case, I had a project <code>Thingamajig</code> and a companion project <code>ThingamajigAutoTests</code> (names changed to protect the guilty) that both produced unsigned assemblies. I duly added the attribute <code>[assembly: InternalsVisibleTo( "ThingamajigAutoTests" )]</code> to the Thingamajig\AssemblyInfo.cs file, and commented out the <code>AssemblyKeyFile</code> and <code>AssemblyKeyName</code> attributes as noted above. The <code>Thingamajig</code> project built just fine, but its internal members stubbornly refused to show up in the autotest project.

After much head scratching, I rechecked the <code>ThingamajigAutoTests</code> project properties, and discovered that the assembly name was specified as "ThingamajigAutoTests.dll". Bingo - I added the ".dll" extension to the assembly name in the <code>InternalsVisibleTo</code> attribute, and the pieces fell into place.

Sometimes it's the littlest things...

blocks|key|367128|text|除了以上所有情况，当一切似乎都是正确的，但朋友程序集顽固地拒绝看到任何内部，重新加载解决方案或重新启动Visual+Studio可以解决这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|367129|entityMap^0|12|Q|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

In addition to all of the above, when everything seems to be correct, but the friend assembly stubbornly refuses to see any internals, reloading the solution or restarting Visual Studio can solve the problem.

blocks|key|3156528|text|使用PublicKey之前的回答是有效的：(Visual+Studio2015:需要在一行上，否则它会报告程序集引用无效或无法引用。PublicKeyToken不起作用)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3156529|[assembly:+InternalsVisibleTo("NameSpace.MyFriendAssembly,+PublicKey=0024000004800000940000000602000000240000525341310004000001000100F73F4DDC11F0CA6209BC63EFCBBAC3DACB04B612E04FA07F01D919FB5A1579D20283DC12901C8B66A08FB8A9CB6A5E81989007B3AA43CD7442BED6D21F4D33FB590A46420FB75265C889D536A9519674440C3C2FB06C5924360243CACD4B641BE574C31A434CE845323395842FAAF106B234C2C1406E2F553073FF557D2DB6C5")]|code-block|syntax|javascript|3156530|感谢@Joe|3156531|要获取好友程序集的公钥，请执行以下操作：|3156532|sn+-Tp+path\to\assembly\MyFriendAssembly.dll|3156533|在Developper命令提示符中(启动>程序>+Visual+Studio2015>+Visual+Studio+Tools+>+Developer+command+prompt+for+VS2015)。感谢@Ian+G。|3156534|因为它是一个新的测试库，所以还没有签名。|3156535|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|W|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Previous answers with PublicKey worked: (Visual Studio 2015: NEED to be on one line, otherwise it complains that the assembly reference is invalid or cannot referenced. PublicKeyToken didn't worked)

<pre><code>[assembly: InternalsVisibleTo("NameSpace.MyFriendAssembly, PublicKey=0024000004800000940000000602000000240000525341310004000001000100F73F4DDC11F0CA6209BC63EFCBBAC3DACB04B612E04FA07F01D919FB5A1579D20283DC12901C8B66A08FB8A9CB6A5E81989007B3AA43CD7442BED6D21F4D33FB590A46420FB75265C889D536A9519674440C3C2FB06C5924360243CACD4B641BE574C31A434CE845323395842FAAF106B234C2C1406E2F553073FF557D2DB6C5")]
</code></pre>

Thanks to @Joe

To get the public key of the friend assembly:

<pre><code>sn -Tp path\to\assembly\MyFriendAssembly.dll
</code></pre>

Inside a Developper command prompt (Startup > Programs > Visual Studio 2015 > Visual Studio Tools > Developer Command Prompt for VS2015).
Thanks to @Ian G.

Although, the final touch that made it work for me after the above was to sign my friend library project the same way the project of the library to share is signed. Since it was a new Test library, it wasn't signed yet.

blocks|key|3369567|text|您需要为程序集生成新的完整公钥，然后指定程序集的属性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3369568|[assembly:+InternalsVisibleTo("assemblyname,
PublicKey="Full+Public+Key")]|code-block|syntax|javascript|3369569|按照下面的MSDN步骤从visual+studio中为程序集生成新的完整公钥。|offset|length|3369570|将“获取程序集公钥”项添加到“工具”菜单的|3369571|在Visual+Studio中，单击“工具”菜单上的“外部工具”。|style|BOLD|3369572|在“外部工具”对话框中，单击“添加”，然后在“标题”框中输入“获取程序集公钥”。|3369573|浏览至sn.exe，填写命令框。它通常安装在以下位置:Microsoft：\Program+Files+(X86)\+SDKs\Windows\v7.0a\Bin\x64\sn.exe.|3369574|在参数框中，键入以下内容(区分大小写)：-Tp+$(TargetPath)。选中“使用输出窗口”复选框。|3369575|单击OK。新命令将添加到“工具”菜单中。|3369576|每当需要正在开发的程序集的公钥标记时，单击“工具”菜单上的“获取程序集公钥”命令，该公钥标记就会出现在“输出”窗口中。|3369577|entityMap|0|LINK|mutability|MUTABLE|url|https://msdn.microsoft.com/en-us/library/office/ee539398(v=office.14).aspx^0|0|0|5|4|0|0|0|0|X|0|0|H|0|1M|Y|0|K|H|0|2|2|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1A|8|@]|9|@$I|1B|J|1C|1|1D]]|A|$]]|$1|K|3|L|5|6|7|1E|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1F|8|@$I|1G|J|1H|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1I|8|@$I|1J|J|1K|O|P]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1L|8|@$I|1M|J|1N|O|P]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1O|8|@$I|1P|J|1Q|O|P]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1R|8|@$I|1S|J|1T|O|P]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1U|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]]]

You are required to generate an new full public key for the assembly and then specify the attribute to assembly.

<pre><code>[assembly: InternalsVisibleTo("assemblyname,
PublicKey="Full Public Key")]
</code></pre>

Follow the below <a href="https://msdn.microsoft.com/en-us/library/office/ee539398(v=office.14).aspx" rel="nofollow">MSDN</a> steps to generate new full public key for the assembly from visual studio.



To add a Get Assembly Public Key item to the Tools menu

In Visual Studio, click External Tools on the Tools menu.

In the External Tools dialog box, click Add and enter Get Assembly Public Key in the Title box.

Fill the Command box by browsing to sn.exe. It is typically installed at the following location: C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0a\Bin\x64\sn.exe.

In the Arguments box, type the following (case sensitive): -Tp $(TargetPath).
Select the Use Output window check box.

Click OK. The new command is added to the Tools menu.

Whenever you need the Public Key Token of the assembly you are developing, click the Get Assembly Public Key command on the Tools menu, and the public key token appears in the Output window.

blocks|key|363876|text|在我使用VS.Net+2015的情况下，我需要对两个程序集进行签名(如果至少需要对一个程序集进行签名，或者您希望引用您的程序集的公钥)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|363877|我的项目根本没有使用签名。因此，我开始向我的测试库添加一个sign+key，并在我的项目基库中使用InternalsVisibleTo属性。但是VS.Net总是解释说它不能访问friend方法。|363878|当我开始给基库签名时(它可以是同一个签名密钥，也可以是另一个签名密钥--只要你给基库签名)，VS.Net马上就能按预期工作了。|363879|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In my case using VS.Net 2015, I needed to sign BOTH assemblies (if at least 1 assembly shall be signed or you want to reference on the public key of your assembly).

My project didn't use signing at all. So I started adding a sign key to my test library and useing the InternalsVisibleTo-Attribute at my project's base library. But VS.Net always explained it couldn't access the friend methods.

When I started to sign the base library (it can be the same or another sign key - as long as you do sign the base library), VS.Net was immediately able to work as expected.

blocks|key|367261|text|仅当您希望将未签名的程序集保留为未签名的程序集(并且出于以下几个原因不想对其签名)时才适用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|367262|还有一点:如果您将基库从VS.Net编译到本地目录，它可能会按预期工作。|367263|但是:一旦将基库编译到网络驱动器中，就会应用安全策略，并且程序集无法成功加载。这再次导致在检查PublicKey匹配时VS.NET或编译器失败。|367264|最后，可以使用未签名的程序集：https://msdn.microsoft.com/en-us/library/bb384966.aspx您必须确保两个程序集都没有签名，并且程序集属性必须没有PublicKey信息：|offset|length|367265|<Assembly:+InternalsVisibleTo("friend_unsigned_B")>|style|CODE|367266|entityMap|0|LINK|mutability|MUTABLE|url|https://msdn.microsoft.com/en-us/library/bb384966.aspx^0|0|0|0|F|1I|0|0|0|1F|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$H|Z|I|10|1|11]]|A|$]]|$1|J|3|K|5|6|7|12|8|@$H|13|I|14|L|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

Applies only if you like to keep unsigned assemblies as unsigned assembly (and don't want to sign it for several reasons):

There is still another point: if you compile your base library from VS.Net to a local directory, it may work as expected.

BUT: As soon as you compile your base library to a network drive, security policies apply and the assembly can't be successfully loaded. This again causes VS.NET or the compiler to fail when checking for the PublicKey match.

FINALLY, it's possible to use unsigned assemblies:
<a href="https://msdn.microsoft.com/en-us/library/bb384966.aspx" rel="nofollow">https://msdn.microsoft.com/en-us/library/bb384966.aspx</a>
You must ensure that BOTH assemblies are NOT SIGNED
And the Assembly attribute must be without PublicKey information: 

<code>&lt;Assembly: InternalsVisibleTo("friend_unsigned_B")&gt;</code>

blocks|key|367273|text|另一种可能性可能很难追踪，这取决于您的代码是如何编写的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|367274|367275|您正在从另一个程序集中调用在X中定义的内部方法Y|ordered-list-item|367276|方法签名使用在Z|367277|中定义的内部类型然后您必须在X和Z|367278|中添加InternalsVisibleTo|367279|例如：|367280|//+In+X
internal+static+class+XType
{
++++internal+static+ZType+GetZ()+{+...+}
}

//+In+Y:
object+someUntypedValue+=+XType.GetZ();

//+In+Z:
internal+class+ZType+{+...+}|code-block|syntax|javascript|367281|如果你像上面写的那样，在Y中没有直接引用ZType，在添加了Y作为X的朋友之后，你可能会感到困惑，为什么你的代码仍然不能编译。|367282|在这种情况下，编译错误肯定会更有帮助。|367283|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|11|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|13|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|15|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

Another possibility that may be tricky to track down, depending on how your code is written.

<ol>
<li>You're invoking an internal method defined in X from another assembly Y</li>
<li>The method signature uses internal types defined in Z</li>
<li>You then have to add [InternalsVisibleTo] in X AND in Z</li>
</ol>

For example:

<pre><code>// In X
internal static class XType
{
 internal static ZType GetZ() { ... }
}

// In Y:
object someUntypedValue = XType.GetZ();

// In Z:
internal class ZType { ... }
</code></pre>

If you have it written like above, where you're not referring to ZType directly in Y, after having added Y as a friend of X, you may be mystified why your code still doesn't compile.

The compilation error could definitely be more helpful in this case.

blocks|key|363928|text|我写这篇文章是出于沮丧。确保授予访问权限的程序集的名称与预期一致。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|363929|我重命名了我的项目，但这不会自动更新程序集名称。右键单击您的项目，然后单击Properties。在应用程序下，确保程序集名称和默认命名空间是您所期望的。|offset|length|style|BOLD|363930|entityMap^0|0|1L|5|1R|6|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

I'm writing this out of frustration. Make sure the assembly you are granting access to is named as you expect.

I renamed my project but this does not automatically update the Assembly Name. Right click your project and click Properties. Under Application, ensure that the Assembly Name and Default Namespace are what you expect.

blocks|key|3369700|text|如果您有多个引用的程序集-检查是否所有必需的程序集都具有InternalsVisibleTo属性。有时这并不明显，并且没有消息表明您必须将此属性添加到另一个程序集中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3369701|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you have more than 1 referenced assembly - check that all necessary assemblies have InternalsVisibleTo attribute. Sometimes it's not obviously, and no message that you have to add this attribute into else one assembly.

blocks|key|3369724|text|我也有同样的问题。所有的解决方案都不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3369725|最终发现该问题是由于类X显式实现内部接口Y造成的。|3369726|方法X.InterfaceMethod是不可用的，尽管我不知道为什么。|3369727|解决方案是在测试库中强制转换(X作为YourInterface).InterfaceMethod，然后就可以正常工作了。|3369728|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I had the same problem. None of the solutions worked.

Eventually discovered the issue was due to class X explicitly implementing interface Y, which is internal.

the method X.InterfaceMethod was unavailable, though I have no idea why.

The solution was to cast (X as YourInterface).InterfaceMethod in the test library, and then things worked.

blocks|key|3369745|text|1-对测试项目进行签名:+Visual+Studio中的转到测试项目的属性窗口，和对程序集进行签名，方法是选中Signing选项卡中具有相同短语的复选框。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3369746|2-为测试项目创建一个PublicKey：+Open+Visual+Studio命令提示符(例如VS+2017的开发人员命令提示符)。转到测试项目的.dll文件所在的文件夹。通过sn.exe创建公钥：|3369747|sn+-Tp+TestProject.dll|3369748|请注意，参数是-Tp，而不是-tp。|3369749|3-将PublicKey引入待测项目：进入待测项目中的AssemblyInfo.cs文件，添加包含上一步创建的PublicKey的这一行：|3369750|组件:+InternalsVisibleTo("TestProjectAssemblyName，PublicKey=2066212d128683a85f31645c60719617ba512c0bfdba6791612ed56350368f6cc40a17b4942ff16cda9e760684658fa3f357c137a1005b04cb002400000480000094000000060200000024000052534131000400000100010065fe67a14eb30ffcdd99880e9d725f04e5c720dffc561b23e2953c34db8b7c5d4643f476408ad1b1e28d6bde7d64279b0f51bf0e60be2d383a6c497bf27307447506b746bd2075")|3369751|不要忘记将上面的PublicKey替换为您的the。|3369752|4-将私有方法设为内部:在要测试的项目中，将方法的访问修饰符更改为内部。|3369753|内部静态空DoSomething(){...}|3369754|entityMap^0|0|S|U|A|15|4|1J|7|0|0|L|1X|4|0|0|0|0|J|0|O|N|1C|9|0|0|0|10|0|0|N|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1B|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1C|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1L|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1M|8|@$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|T|3|U|5|6|7|1P|8|@$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]]|W|$]]

1- Sign the test project: In Visual Studio go to the properties window of the test project and Sign the assembly by checking the checkbox with the same phrase in the Signing tab.

2- Create a PublicKey for the test project: Open Visual Studio Command Prompt (e.g. Developer Command Prompt for VS 2017). Go to the folder where the .dll file of the test project exists. Create a Public Key via sn.exe:

sn -Tp TestProject.dll

Note that the argument is -Tp, but not -tp.

3- Introduce the PublicKey to the project to be tested: Go to the AssemblyInfo.cs file in the project to be tested and add this line with the PublicKey created in the previous step:

[assembly: InternalsVisibleTo("TestProjectAssemblyName, PublicKey=2066212d128683a85f31645c60719617ba512c0bfdba6791612ed56350368f6cc40a17b4942ff16cda9e760684658fa3f357c137a1005b04cb002400000480000094000000060200000024000052534131000400000100010065fe67a14eb30ffcdd99880e9d725f04e5c720dffc561b23e2953c34db8b7c5d4643f476408ad1b1e28d6bde7d64279b0f51bf0e60be2d383a6c497bf27307447506b746bd2075")]

Don't forget to replace the above PublicKey with yours.

4- Make the private method internal: In the project to be tested change the access modifier of the method to internal.

internal static void DoSomething(){...}

blocks|key|3156863|text|尽管使用AssemblyInfo文件并添加InternalsVisibleTo仍然有效，但现在(据我所知)首选方法是在项目的csproj文件中使用ItemGroup，如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3156864|++++<ItemGroup>
++++++++<InternalsVisibleTo+Include="My.Project.Tests"+/>
++++</ItemGroup>|code-block|syntax|javascript|3156865|如果需要PublicKey，也可以添加此属性。|3156866|entityMap^0|4|C|L|I|1Q|6|21|9|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

Although using an <code>AssemblyInfo</code> file and adding <code>InternalsVisibleTo</code> still works, the preferred approach now (as far as I can tell) is to use an <code>ItemGroup</code> in your Project's <code>csproj</code> file, like so:
<pre><code> &lt;ItemGroup&gt;
 &lt;InternalsVisibleTo Include=&quot;My.Project.Tests&quot; /&gt;
 &lt;/ItemGroup&gt;
</code></pre>
If a PublicKey is required, this attribute may also be added.

I am trying to use the <code>InternalsVisibleTo</code> assembly attribute to make my internal classes in a .NET class library visible to my unit test project. For some reason, I keep getting an error message that says:

<blockquote>
 'MyClassName' is inaccessible due to its protection level
</blockquote>

Both assemblies are signed and I have the correct key listed in the attribute declaration. Any ideas?

InternalsVisibleTo attribute isn't working

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在尝试使用InternalsVisibleTo程序集属性来使.NET类库中的内部类对我的单元测试项目可见。由于某些原因，我一直收到一条错误消息：由于其保护级别，无法访问 'MyClassName‘两个程序集都经过签名，并且我在属性声明中列出了正确的密钥。有什么想法吗？

问InternalsVisibleTo属性不起作用
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问InternalsVisibleTo属性不起作用EN