Sascha
Reputation: 601
Replacements for private accessors in Visual Studio 2012
I startet to migrate a Testproject from VS2010 to 2012. Now I see that the private accessors are not supported anymore.
I saw this , but is that the only way to fix that? I don't want to declare the private methods as internal... :-(
Upvotes: 2
Views: 6765
Answers (2)
Stefan
Reputation: 87
Hiding the usage of PrivateObject by a generic base class like shown by the posting Home-made Private Accessor for Visual Studio 2012+ might ease and simplify its usage.
Regards,
Stefan
Upvotes: 0
Nelson Menezes
Reputation: 109
I guess that in your case using using PrivateObjects will help you. To view how to use them, you can view this link: http://akurniaga.wordpress.com/tag/unit-test-privateobject-visual-studio/ . Hope this helps you.
Upvotes: 1
Related Questions
- Private accessor won't access private member
- Private Accessors in Visual Studio 2012
- Unit testing private members using *_Accessor
- Automatic way of generating accessor classes in C#
- Unit testing with and without private Accessor
- Visual Studio private accessors and checking in code
- C# - VS 2010 Unit Testing for private methods
- VS2010 SP1 unit tests targeting 3.5 framework fail if using private accessor
- Private Accessor for method is not found
- What is the best practice for unit testing private methods in .NET?