Sign 'AlphaFS.dll' with a strong name key. 'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' calls into 'Process.GetCurrentProcess()' which has a LinkDemand. By making this call, 'Process.GetCurrentProcess()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' calls into 'Process.GetCurrentProcess()' which has a LinkDemand. By making this call, 'Process.GetCurrentProcess()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' 'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' calls into 'Process.Handle.get()' which has a LinkDemand. By making this call, 'Process.Handle.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' calls into 'Process.Handle.get()' which has a LinkDemand. By making this call, 'Process.Handle.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' 'Path.NormalizePath(string, GetFullPathOptions)' has 71 local variables, 47 of which were generated by the compiler. Refactor 'Path.NormalizePath(string, GetFullPathOptions)' so that it uses fewer than 64 local variables. Assemblies should have valid strong names Either the assembly has no strong name, an invalid one, or the strong name is valid only because of the computer configuration. The assembly should not be deployed in this state. The most common causes of this are: 1) The assembly's contents were modified after it was signed. 2) The signing process failed. 3) The assembly was delay-signed. 4) A registry key existed that allowed the check to pass (where it would not have otherwise). Sign {0} with a strong name key. http://msdn.microsoft.com/library/ms182127.aspx [none] CriticalError Avoid excessive locals Method implementations should not contain more than 64 local variables. In order for the run-time to enregister local variables most efficiently, there should be 64 or fewer of them. Enregistering based on flow analysis will not occur for locals in excess of 64, which may result in slower performance. {0} has {1} local variables, {2} of which were generated by the compiler. Refactor {0} so that it uses fewer than 64 local variables. http://msdn.microsoft.com/library/ms182263.aspx [none] Warning Do not indirectly expose methods with link demands Do not wrap a method protected by a LinkDemand with a method that does not perform a security check. A LinkDemand checks the permissions of the immediate caller rather than checking the permissions of all callers in the call stack. In this case, the permissions of the wrapper method will be checked. If the wrapper method does not, itself, check the permissions of callers higher in the call stack, malicious code might be able to execute the wrapped function even though it lacks permission to do so. {0} calls into {1} which has a LinkDemand. By making this call, {1} is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: {2} http://msdn.microsoft.com/library/ms182303.aspx [none] CriticalError Category Certainty Collapse All Check Id Error error(s) Expand All Help Line message(s) [Location not stored in Pdb] Project Resolution Rule Rule File Rule Description Source Status Target Warning warning(s) Code Analysis Report