{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}
Calling Convention : Select the default calling convention for your application (can be overridden by function). (/Gd, /Gr, ...
Calling managed '%s': Managed code may not be run under loader lock, including the DLL entrypoint and calls reached from ...
Calling Validate method of ExceptionValidationRule is not supported. Validation results for ExceptionValidationRule are set ...
Calls ExecuteNonQuery on an existing command. Wraps the execution in a try/finally block to return the connection object ...
calls into {1} which has a LinkDemand. By making this call, {1} is indirectly exposed to user code. Review the following ...
calls {1} but does not explicitly check whether the conversion succeeded. Either use the return value in a conditional statement ...
calls {1} but does not use the HRESULT or error code that the method returns. This could lead to unexpected behavior in error ...
calls {1} but does not use the new string instance that the method returns. Pass the instance as an argument to another method, ...
calls {1}, a method that is typically only called within an implementation of 'IDisposable.Dispose'. Refer to the IDisposable ...