John Timney (MVP) wrote:
you could probably run process.start against the mstsc.exe program (remote
connection manager) to shell an instance of Remote Conenction Manager to
create your connection using a .rdp file as your command line argument.
Cool, thanks alot thats exactly what I needed.
Having tried this however a problem has emerged;
When i run the application from a networked location i get a
SecurityExcepti on :(
What can i do about this?
Thanks!
Andrew
Below is the top of the stack trace
System.Security .SecurityExcept ion: Request failed.
at
System.Security .CodeAccessSecu rityEngine.Thro wSecurityExcept ion(Assembly
asm, PermissionSet granted, PermissionSet refused, RuntimeMethodHa ndle
rmh, SecurityAction action, Object demand, IPermission permThatFailed)
at
System.Security .CodeAccessSecu rityEngine.Thro wSecurityExcept ion(Object
assemblyOrStrin g, PermissionSet granted, PermissionSet refused,
RuntimeMethodHa ndle rmh, SecurityAction action, Object demand,
IPermission permThatFailed)
at
System.Security .CodeAccessSecu rityEngine.Chec kSetHelper(Perm issionSet
grants, PermissionSet refused, PermissionSet demands,
RuntimeMethodHa ndle rmh, Object assemblyOrStrin g, SecurityAction
action, Boolean throwException)
at
System.Security .CodeAccessSecu rityEngine.Chec kSetHelper(Comp ressedStack
cs, PermissionSet grants, PermissionSet refused, PermissionSet demands,
RuntimeMethodHa ndle rmh, Assembly asm, SecurityAction action)
at Form1.menuItemC licked_RDC(Obje ct sender, EventArgs e)
The action that failed was: LinkDemand
The type of the first permission that failed was:
System.Security .PermissionSet
The Zone of the assembly that failed was: Intranet