I am trying to use the InternalsVisibleTo 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 th...

I insert the line: [assembly: InternalsVisibleTo("MyTests")] inside my project under test( Properties/AssemblyInfo.cs) where MyTests is the name of the Unit Test project. But for some reason I s...

I am currently trying to write unit tests in my solution, but I want to put my unit tests in a different separate project. The problem is when I am generating some fake testing data I need to set p...

Is there a signed version of LinqPad that I could use in order to access internals of signed assemblies?

Before asp.net 5 I would add "internalsVisibleTo(some.namespace.name)" to AssemblyInfo.cs - But I no longer have assemblyInfo.cs in my WebApi project. How do I expose internals in a WebAPI project...

InternalsVisibleTo is not working for my managed C++ projects, but it is for my C# projects. Any help would be appreciated. Here is a simplified layout. Project A - C#, has an internal property I ...

A new version of the .Net framework and C# offer a new access modifier: private protected. In order to access such a member, the class must both reside in the same assembly and derive from the de...

I would like to define several friend assemblies. It is easy to do so when editing the AssemblyInfo file manually: [assembly:InternalsVisibleTo("Friend1a")] [assembly:InternalsVisibleTo("Friend1b...

I'm having an issue with cross-assembly / friend assembly type visibility. I have the following program (which I sign / strong-name). It tells Castle DynamicProxy (I'm using version 4.2.1 of the C...

It's possible to specify [assembly: InternalsVisibleTo("NameOfOtherAssembly")] in AssemblyInfo.cs. But is it possible to restrict this to specific internal functions? Is there e.g. an attribute t...

So, the issue is that I have a bunch of internal classes in my assembly that are used by the class I want to test. Since accessors have been removed from VS2012, I'm fine with using [InternalsVisib...

I am using Rhino Mocks as a mocking framework for unit testing. I have a class called Subject which is the class I want to test. It has a dependency on IStore. IStore is defined as follows: //in...

I could not find any clear statement on MSDN regarding this, there are some examples with strong names other are without, for me it seems like it should work even without but its not working. Than...

I have an assembly with functionality that I don't want exposed as public but still accessible to my other assemblies. This can be done using InternalsVisibleToAttribute by specifying each assembly...

I have a class with internal constructor and want to Resolve it from Unity (2.0). public class MyClass { internal MyClass(IService service) { } } then I'm doing _container.Resolve<MyClass&...

I am trying to expose some internals to my unit test project by using: [assembly: InternalsVisibleTo("MyTest")] But I am getting the error: Error 1 Friend assembly reference MyTest' is invali...

In our shop, we are using Cruise Control & MSBuild to automate the builds of the product as part of continuous integration. Part of the build is to sign the assemblies so they have strong name...

The situation is as follows: I want to release the full source to a class library I want to release binaries as well, signed by me, with a key file I don't want to publish I will provide batch fi...

[Of course, the question is not restricted to a specific "friend" implementation, feel free though to point out implementation specifics if relevant] Reading through the unanswered questions, I st...

Before I go on I did go through this InternalsVisibleTo attribute ain’t workin'! Hence the title Okay so I had a working version of my project that was using something like the following. [assembly...

I understand that the InternalVisibleTo attribute is used to expose types and methods with the internal access modifier to a specified assembly. I have only ever used this for exposing internal met...

In general, I design classes in such a manner as to not require access to privates for testing purposes. An InternalsVisibleTo can also assist. However, I'm currently dealing with a codebase that ...