Re: Control.Invoke() equivalent with Thread object - C# Discussion Boards

Nicholas Butler29-Jul-08 23:36

29-Jul-08 23:36

Some methods in the framework take the name of a method as a string, e.g. ObjectDataSource and most of WPF. I don't like this as the compiler and IDE tools can't link the string and the method. So I want to generate the string from the token. I came up with this:

class TestClass
{
  public static void Test()
  {
    string s = GetName<string,int>( Method );
  }
 
  static int Method( string s ) { return 0; }
 
  static string GetName<T,TResult>( Func<T,TResult> method )
  {
    return method.Method.Name;
  }
 
  ...
  GetName overloads for Actions and Funcs
  ...
}

This is ok, but I don't like having to specify the generic types when calling GetName.

I don't think there's a way around this, because method groups don't participate in type inferencing.

So my question is: is there a better way?

Thanks

Nick

----------------------------------
Be excellent to each other Smile | :)

Re: Get method name as string

leppie30-Jul-08 0:22

leppie

30-Jul-08 0:22

Although not exactly what you are looking for, but at least a bit more generic:

class TestClass
{
  public static void Test()
  {
    string s = GetName( new Func<string,int>(Method));
  }

  static int Method(string s) { return 0; }

  static string GetName(Delegate method)
  {
    return method.Method.Name;
  }
}

I will try think of a better way Smile | :)

xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)

Re: Get method name as string

Nicholas Butler30-Jul-08 0:36

Nicholas Butler

30-Jul-08 0:36

Thanks leppie, that is better.

You can also just use a cast:

string s = GetName( ( Func<string,int> ) Method );

But this doesn't work:

string s = GetName( ( Delegate ) Method );

----------------------------------
Be excellent to each other Smile | :)

Re: Get method name as string

DaveyM6930-Jul-08 1:09

DaveyM69

30-Jul-08 1:09

Are you trying to get the method name from the method itself?
If so:

System.Reflection.MethodBase.GetCurrentMethod().Name

Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)

Re: Get method name as string

leppie30-Jul-08 2:27

leppie

30-Jul-08 2:27

Yes, but then he would have to call the method! Poke tongue | ;-P

xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)

Control.Invoke() equivalent with Thread object

ccufi29-Jul-08 23:36

ccufi

29-Jul-08 23:36

Hi there,

I am well aware of the usage of Control.Invoke() in a Form (System.Windows.Forms) to be able to access UI components in a thread-safe manner so that it is the thread that holds the window handle the one that executes it. I was wondering, if I don't have a reference to the Form but instead to the window thread (as a Thread object) is there a way to use that Thread object (or anything similar that can be extracted from the execution context) to do the same as Control.Invoke() ?

Background: I have a C# assembly (utils library) that calls into C++, but callbacks are returned in a separate thread, and I want the assembly to be application-independent but to return the callbacks (using events) in the same thread that the requests were made in.

Thanks in advance!

Carles

Re: Control.Invoke() equivalent with Thread object

Frank Horn30-Jul-08 0:36

Frank Horn

30-Jul-08 0:36

Say your thread calls MyCallbackObject.Callback().

Then you can test whether the object can synchronize the call and call it's Invoke() method if it does:

ISynchronizeInvoke synchronizeInvoke = MyCallbackObject As System.ComponentModel.ISynchronizeInvoke;
if (synchronizeInvoke == null)
{
   MyCallbackObject.Callback()
}
else
{
   synchronizeInvoke.Invoke(myDelegate);
}

where myDelegate is a delegate to a method wrapping MyCallbackObject.Callback().

Re: Control.Invoke() equivalent with Thread object

Alan N30-Jul-08 4:55

Alan N

30-Jul-08 4:55

Hello,
Useful classes are the System.ComponentModel AsyncOperationManager and AsyncOperation. I've pasted in some code that performs a directory search in a background thread. When complete the background thread raises on event on the thread that called BeginSearch.

This calling thread does not need to consider the source of the event and may use the information received in the EventArgs directly in any control.

Alan.

/* DirectorySearch.cs
 *
 * Purpose : Directory data collection on a background thread
 *
 * Revision History
 * Based on Microsoft.Samples.DirectorySearcher but simplified and
 * modified to use ThreadPool, AsyncOperationManager
 */
using System;
using System.ComponentModel;
using System.Threading;
using System.IO;

namespace SpecTest {
  class DirectorySearchCP {
    private AsyncOperation operation;
    private String startDir;
    private DirectoryInfo[] dirlist;
    public event EventHandler<DirListEventArgs> SearchComplete;

    // Create the search thread, which will initiate the search.
    public void BeginSearch(String startDir) {
      this.startDir = startDir;
      operation = AsyncOperationManager.CreateOperation(null);
      ThreadPool.QueueUserWorkItem(new WaitCallback(ThreadProcedure), null);
    }
    
    private void SearchDirectory() {
      DirectoryInfo s = new DirectoryInfo(startDir);
      dirlist = s.GetDirectories("*.*", SearchOption.TopDirectoryOnly);
    }

    // This method runs in a background thread to collect directory information.
    private void ThreadProcedure(Object stateInfo) {
      try {
        SearchDirectory();
      } finally {
        // Raise an event to notify the user that the search has terminated. 
        // This event is raised on the thread that called BeginSearch
        operation.PostOperationCompleted(new SendOrPostCallback(OnSearchComplete), dirlist);
      }
    }

    private void OnSearchComplete(Object state) {
      EventHandler<DirListEventArgs> handler = SearchComplete;
      if (handler != null) {
        DirListEventArgs args = new DirListEventArgs();
        args.dirlist = (DirectoryInfo[])state;
        handler(this, args);
      }
    }
  }

  public class DirListEventArgs : System.EventArgs {
    public DirectoryInfo[] dirlist;
  }
}

How to run application from network folder

AndrusM29-Jul-08 23:12

AndrusM

29-Jul-08 23:12

Managed code .NET 3.5 C# WinForms application runs OK from Vista when in local drive.

When application is copied to mapped network drive or started from \\othercmp\c\myapp\myapp.exe folder , it does not start: Vista shows

MyApp has stopped working
Windows is checking for a solution to the problem..

How to fix ?

Andrus

Re: How to run application from network folder

Simon P Stevens29-Jul-08 23:47

Simon P Stevens

29-Jul-08 23:47

It's because of the trust level assigned to the app.

.net exe files run off of a network share are assigned a low trust level. (As opposed to full trust when run locally). If you want your app to automatically just work from a network share you need to design it so it doesn't require full trust. This means you can't do anything like writing to the local file system, using the registry, and a whole bunch of other stuff. (There are often alternatives, like you could use isolated storage for settings instead of the registry).

Or, you can adjust the security to either explicitly trust a specific strong name signed assembly, no matter where is it run from[^] or explicitly allow full trust for apps run from a given network location[^]

Simon

Re: How to run application from network folder

AndrusM30-Jul-08 0:25

AndrusM

30-Jul-08 0:25

If you want your app to automatically just work from a network share you need to design it so it doesn't require full trust

I need that in MDI child form Escape key closes form, Ctrl+F1 cycles and
Ctrl+F10 toggles maximizing. For this I use code below in form base class which requires full trust.
How to implement those features without full trust ?

Andrus.

[SecurityPermission(SecurityAction.LinkDemand, Flags = SecurityPermissionFlag.UnmanagedCode)]
protected override bool ProcessCmdKey(ref Message msg, Keys keyData)
        {
            switch (keyData)
            {
                case Keys.Escape:
                    if (this != FormManager.MainForm)
                    {
                        Close();
                        return true;
                    }
                    break;

                case Keys.Control | Keys.F1:
                    for (int i = 0; i < FormManager.MainForm.MdiChildren.Length; i++)
                    {
                        if (FormManager.MainForm.MdiChildren[i] == this)
                        {

                            if (i < FormManager.MainForm.MdiChildren.Length - 1)
                                FormManager.MainForm.MdiChildren[i + 1].Focus();
                            else
                                FormManager.MainForm.MdiChildren[0].Focus();

                            return true;
                        }
                    }
                    return true;

                case Keys.Control | Keys.F10:
                    if (WindowState == FormWindowState.Maximized)
                        WindowState = FormWindowState.Normal;
                    else
                        WindowState = FormWindowState.Maximized;
                    return true;

            }
            return base.ProcessCmdKey(ref msg, keyData);
        }
    }

Andrus

Re: How to run application from network folder

Simon P Stevens30-Jul-08 1:16

Simon P Stevens

30-Jul-08 1:16

Handle the forms keypress or keydown events instead of overriding the ProcessCmdKey method. Use code in their to max/min/cycle your forms based on the key pressed.

Simon

Re: How to run application from network folder

AndrusM30-Jul-08 1:22

AndrusM

30-Jul-08 1:22

http://www.codeproject.com/KB/database/DatabaseAcessWithAdoNet1.aspx[^]

states that DataGridView and other controls do not raise those events.

How I can use those events when DataGridView is active?

Andrus

Re: How to run application from network folder

Simon P Stevens30-Jul-08 1:34

Simon P Stevens

30-Jul-08 1:34

Ahh...interesting.

Have you tried the _forms_ previewkeydown event? (You have to set keypreview to true)

Simon

Re: How to run application from network folder

AndrusM30-Jul-08 7:25

AndrusM

30-Jul-08 7:25

http://blogs.msdn.com/jfoscoding/archive/2005/01/24/359334.aspx[^]

States that MDI Parent form ProcessCmdKey is called before PreviewKeyDown.

Probably Main form ProcessCmdKey consides those keys as special keys and processec them, it will not pass them to PreviewKeyDown.

Andrus

Re: How to run application from network folder

Simon P Stevens30-Jul-08 21:30

Simon P Stevens

30-Jul-08 21:30

Sorry then, I'm out of ideas. There should be a way though. Detecting a key press barely seems like something that should require full trust.

Simon

Re: How to run application from network folder

AndrusM30-Jul-08 22:38

AndrusM

30-Jul-08 22:38

No, there are no ways.

Detecting those keypresses in winForms requires application to run in full trust mode.

Andrus

Re: How to run application from network folder

AndrusM30-Jul-08 1:35

AndrusM

30-Jul-08 1:35

I ran with adminstrator rights in Vista

CasPol.exe -m -ag 1.2 -url file://z:/myapp/* FullTrust

C:\...crosoft.NET\Framework\v2.0.50727>g 1.2 -url file://z:/myapp/* FullTrust
Microsoft (R) .NET Framework CasPol 2.0.50727.1434
Copyright (c) Microsoft Corporation.  All rights reserved.

The operation you are performing will alter security policy.
Are you sure you want to perform this operation? (yes/no)
y
Added union code group with "-url" membership condition to the Machine level.
Success

However

z:\myapp\myapp.exe

still shows immediately

Myapp as stopped working

Andrus

Re: How to run application from network folder

Simon P Stevens30-Jul-08 1:41

Simon P Stevens

30-Jul-08 1:41

Sorry, I've no idea about this. Try catching and logging exceptions at the top level to see what's going wrong.

Simon

Re: How to run application from network folder

AndrusM30-Jul-08 7:27

AndrusM

30-Jul-08 7:27

Exception which occurs in does not show .NET Winforms unhandled exception dialog.
So this exception cannot be catched in .NET code.

Andrus

Re: How to run application from network folder

mav.northwind30-Jul-08 19:03

mav.northwind

30-Jul-08 19:03

Hi!
There's a control panel for the configuration of .NET 2.0 if you have the SDK installed.
When you select "Runtime security policies" (I hope that's the correct name, I only have the German version here...) you get the option to evaluate a given assembly with respect to all the permissions this assembly is granted.
You could test your assembly to verify that the change in your security policy actually affects your application.

Regards,
mav

--
Black holes are the places where God divided by 0...

Re: How to run application from network folder

AndrusM30-Jul-08 23:02

AndrusM

30-Jul-08 23:02

.NET 2 SDK downlaod page says that this is obsolete and recommends to download Windows SDK for Windows Server 2008 and .NET Framework 3.5 from

http://www.microsoft.com/downloads/details.aspx?FamilyId=E6E1C3DF-A74F-4207-8586-711EBE331CDC&displaylang=en[^]

Whoe package is 1.3 GB to download which is too much.

Which options I must select to install security utility ?

Andrus

Re: How to run application from network folder

mav.northwind31-Jul-08 8:36

mav.northwind

31-Jul-08 8:36

Don't know, sorry.
Don't you have VS2005 installed? In that case, the .NET 2.0 SDK is already installed.

Regards,
mav

--
Black holes are the places where God divided by 0...

Re: How to run application from network folder

AndrusM31-Jul-08 9:13

AndrusM

31-Jul-08 9:13

I have Visual C# Express 2008 Installed.
I intalled "SDK Tools" from "Windows and .NET SDK" package but Control Panel does not show this utility.

Installer created 2 directories, v6.0a and v6.1 containing files with same names. I tried some executables in v6.1 directory but they appear to do other things.

 Directory of C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin

31.07.2008  12:06    <DIR>          .
31.07.2008  12:06    <DIR>          ..
07.11.2007  12:01            72_688 al.exe
06.11.2007  21:53               140 al.exe.config
16.01.2008  17:21            40_960 apatch.exe
07.11.2007  12:01           913_416 aspnet_merge.exe
07.11.2007  12:01            58_360 AxImp.exe
16.01.2008  17:21           510_976 capicom.dll
16.01.2008  17:21            20_992 Cert2Spc.exe
16.01.2008  17:21            74_752 CertMgr.Exe
16.01.2008  17:21            30_208 checkv4.exe
07.11.2007  12:01            66_040 clrver.exe
16.01.2008  17:21            23_552 Consume.exe
07.11.2007  12:01           185_336 cordbg.exe
07.11.2007  12:01            72_192 CorFlags.exe
16.01.2008  17:21            60_416 ctrpp.exe
19.06.2006  14:09               247 dasmhlp.cnt
19.06.2006  14:09            21_963 DASMHLP.HLP
22.01.2008  12:11            58_360 disco.exe
31.07.2008  12:03    <DIR>          en-us
07.11.2007  12:01           107_520 FUSLOGVW.exe
07.11.2007  12:01           106_496 gacutil.exe
06.11.2007  20:07               181 gacutil.exe.config
16.01.2008  17:21           132_608 genmanifest.exe
07.11.2007  12:01            31_744 guidgen.exe
07.11.2007  12:01           386_040 ildasm.exe
06.11.2007  20:07               181 ildasm.exe.config
11.12.2007  14:15             3_105 INSTLR1.ADM
11.12.2007  14:15             9_179 instlr11.adm
08.01.2008  17:19               596 isvtier5appsigningprivkey.dat
08.01.2008  17:19               148 isvtier5appsigningpubkey.dat
08.01.2008  17:19            21_234 isvtier5appsignsdk.cc
08.01.2008  17:19             4_916 isvtier5appsignsdk.xml
08.01.2008  17:19            56_994 isvtier5appsignsdk_client.xml
07.11.2007  12:01            46_064 lc.exe
07.11.2007  12:01            78_840 mage.exe
07.11.2007  12:01           463_864 mageui.exe
16.01.2008  17:21           123_904 make-shell.exe
16.01.2008  17:21            30_720 MakeCat.Exe
16.01.2008  17:21            57_856 makecert.exe
07.11.2007  12:01           111_608 Mdbg.exe
22.01.2008  12:11           376_832 MdbgCore.dll
22.01.2008  12:11           104_960 MdbgDis.dll
16.01.2008  17:21           170_496 MergeMod.Dll
07.11.2007  12:01            25_608 mgmtclassgen.exe
16.01.2008  17:21            88_576 Midl.Exe
16.01.2008  17:21           820_736 MidlC.Exe
07.11.2007  09:57           373_760 msdis160.dll
11.12.2007  14:15             2_184 msi.adm
16.01.2008  17:21            74_752 MsiCert.exe
16.01.2008  17:21           155_648 MsiDb.Exe
16.01.2008  17:21            73_728 MsiFiler.Exe
16.01.2008  17:21            98_816 MsiInfo.Exe
16.01.2008  17:21            65_536 MsiMerg.Exe
16.01.2008  17:21            68_096 MsiMsp.Exe
16.01.2008  17:21            73_728 MsiStuff.Exe
11.12.2007  14:15            16_516 MsiTool.Mak
31.07.2008  12:03    <DIR>          msitools
16.01.2008  17:21            68_096 MsiTran.Exe
16.01.2008  17:21         1_455_104 MsiVal2.Msi
16.01.2008  17:21           113_664 MsiZap.Exe
16.01.2008  17:21            71_680 mspatchc.dll
08.01.2008  17:19               276 msrootpub1.dat
08.01.2008  17:19               276 msrootpub2.dat
16.01.2008  17:21         2_243_072 Orca.Msi
16.01.2008  17:21           270_336 patchwiz.dll
16.01.2008  17:21            43_008 perflibmig.exe
07.11.2007  12:01            37_888 PermCalc.exe
31.07.2008  12:06    <DIR>          PermCalcCache
07.11.2007  12:01            79_360 PEVerify.exe
06.11.2007  20:07               181 PEVerify.exe.config
16.01.2008  17:21            28_160 pvk2pfx.exe
16.01.2008  17:21            58_368 ReBase.Exe
08.11.2007  01:26           201_752 RequiredPermissions.dll
07.11.2007  12:01            62_456 ResGen.exe
07.11.2007  12:01            50_176 SecUtil.exe
31.07.2008  12:00            20_936 SetEnv.Cmd
22.01.2008  12:11            54_264 sgen.exe
16.01.2008  17:21           112_128 signtool.exe
07.11.2007  12:01            95_728 sn.exe
06.11.2007  20:07               181 sn.exe.config
22.01.2008  12:11            46_080 SoapSuds.exe
03.05.2007  09:43               181 SoapSuds.exe.config
22.01.2008  12:11            22_024 SoapSudsCode.dll
16.01.2008  17:21            23_040 SpOrder.Dll
16.01.2008  17:21            27_648 SpOrder.Exe
07.11.2007  12:01           291_840 SqlMetal.exe
04.08.2007  12:43               156 SqlMetal.exe.config
11.12.2007  14:14            19_747 StartTools.htm
07.11.2007  12:01            41_984 StoreAdm.exe
21.06.2007  00:05            63_820 SvcConfigEditor.chm
17.10.2007  02:33         2_102_288 SvcConfigEditor.exe
21.09.2007  12:23            60_421 SvcTraceViewer.chm
22.01.2008  12:11           705_544 SvcTraceViewer.exe
22.01.2008  12:11           193_536 SvcUtil.exe
16.01.2008  17:21            93_184 tcpanalyzer.exe
08.01.2008  17:19               942 tcpanalyzer.exe.manifest
16.01.2008  17:21           226_816 tedutil.dll
07.11.2007  12:01            62_456 TlbExp.exe
07.11.2007  12:01            70_648 TlbImp.exe
16.01.2008  17:21           122_368 topoedit.exe
16.01.2008  17:21            21_504 Uuidgen.Exe
06.10.2007  03:18            54_264 WCA.exe
06.10.2007  03:19            62_456 WFC.exe
03.05.2007  09:43             1_777 WFC.exe.config
16.01.2008  17:21           329_728 WiLogUtl.exe
08.01.2008  17:19            27_344 windiff.chm
16.01.2008  17:21           187_904 WinDiff.Exe
07.11.2007  12:01           152_568 WinRes.exe
16.01.2008  17:21           860_160 wpfperf.msi
16.01.2008  17:21           238_592 wsatui.dll
22.01.2008  12:11            91_128 wsdl.exe
03.05.2007  09:43               181 wsdl.exe.config
16.01.2008  17:21           680_960 XAMLPad.exe
16.01.2008  17:21         4_655_616 xperf_x86.msi
22.01.2008  12:11            87_032 xsd.exe
07.11.2007  12:01           103_416 xsltc.exe
             112 File(s)     23_370_811 bytes
               5 Dir(s)   2_115_723_264 bytes free

Andrus

Re: How to run application from network folder

mav.northwind31-Jul-08 18:22

mav.northwind

31-Jul-08 18:22

I'm afraid I don't know if this control panel is part of VS 2008 Express. With VS 2005 it's located at

C:\Programme\Microsoft Visual Studio 8\SDK\v2.0\Bin\mscorcfg.msc

Hope this helps...

Regards,
mav

--
Black holes are the places where God divided by 0...

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.