Implications of strong naming assemblies RRS feed

  • Question

  • Hello,

    I am creating a unit test project using the VS tools. Obviously, I can only access public members from referenced managed assemblies.

    In the past I have resorted to strong naming my unit test project and then exposing the internals of referenced assemblies via InternalsVisibleTo.

    I am worried about this approach in this instance because this system is quite large and I don't want to go through an strong name every assembly in the chain (i.e. a strongly named assembly can only reference strong named assemblies). Some of these assemblies reference third party tools that I cannot reassemble myself.

    What are some other ways for me to address this?


    • Moved by Andrew.Wu Monday, July 11, 2011 3:08 AM (From:.NET Framework Setup)
    Sunday, July 10, 2011 9:53 PM

All replies

  • Hi CSharpNooblet,

    It appears that your question is more related with unit testing, so I'm going to help move your post to the Visual Studio Unit Testing forum for better support.

    Thanks for your understanding.

    Best Regards,

    Andrew Wu [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Monday, July 11, 2011 3:08 AM