Summary

for RuBoard

Testing secured assemblies shares many aspects with testing any .NET Framework assemblies. For example, performance may be a concern for all assemblies you need to test. However, there are some extra steps to perform when testing secured assemblies. These steps are as follows :

1. Determine what is being protected.

2. Determine how resource protection is implemented.

3. Test any applied custom permissions.

4. Test the methods and properties that should be protected.

If all four of these steps are performed successfully, you have gone a long way to ensure your secured assembly is safe to use.

for RuBoard