As I have understood from the previous
conversation about licencing which
involve unmanaged code,
I supppose the security policy will change also
The last should be change .
I suppose it is true because of lisencing. Not for other reasons ?
ADAdministrator Syncfusion Team April 22, 2005 03:19 PM
the moment you override Control.CreateParams, Control.WndProc or Control message handlers you need SecurityPermission.UnmanagedCode=true.
If you go beyond the standard sets of features supplied by Windows.Forms.Control you will need both FullTrust and UnmanagedCode permission. A lot of our controls override WndProc.
>As I have understood from the previous
>conversation about licencing which
>involve unmanaged code,
>I supppose the security policy will change also
>The last should be change .
>I suppose it is true because of lisencing. Not for other reasons ?
ADAdministrator Syncfusion Team April 23, 2005 01:56 AM
Yes, you are right , this is unavoidable.
By the way I got an error from assembly manager.
In my laptop the performance counters
by accident were disabled or corrupted
and assembly manager threw an exception
System.InvalidOperationException: Process performance counter is disabled, so the requested operation cannot be performed.
at System.Diagnostics.NtProcessManager.GetProcessInfos(PerformanceCounterLib library) at System.Diagnostics.NtProcessManager.GetProcessInfos(String machineName, Boolean isRemoteMachine) at System.Diagnostics.ProcessManager.GetProcessInfos(String machineName) at System.Diagnostics.Process.GetProcesses(String machineName) at SFAssemblyManager.SwapUtilityDlg.IsDevEnvRunning() at SFAssemblyManager.SwapUtilityDlg.Main(String args)