No definition for ClickEvent?

Question

In my code below, I am trying to simulate the Click event for my button Browse.

private void TextBox_MouseDown(object sender, RoutedEventArgs e)
{
    this.Browse.RaiseEvent(new RoutedEventArgs(ButtonBase.ClickEvent));
}

This is the error that I am getting:

'System.Windows.Forms.ButtonBase' does not contain a definition for 'ClickEvent'

How can I raise the click event?

It appears there are some who are questioning the purpose of this code. I got it here https://stackoverflow.com/a/733974/1477388 and am simply trying to make it work.

I don't believe Spender's comment was meant as an answer I think they are trying to ask you what is `ButtonBase.Click` ?? — MethodMan, Aug 13 '13 at 18:39
`HighCore` that's a strictly opinionated comment perhaps his requirements are for he / she to use WinForms — MethodMan, Aug 13 '13 at 18:40
@DJKRAZE I don't know if I can answer that, as per my edit, I have found this code at the link posted above and I am trying to make it work. — user1477388, Aug 13 '13 at 18:41
@HighCore has it. What's Winforms got to do with it? This should be ButtonBase in a WPF namespace. — spender, Aug 13 '13 at 18:41
@spender the error clearly states `'System.Windows.[[Forms]].ButtonBase' does not contain a definition for 'ClickEvent' — Federico Berasategui, Aug 13 '13 at 18:42

score 5 · Accepted Answer · answered Aug 13 '13 at 18:45

5

You're working with a WPF application

this.Browse.RaiseEvent(new RoutedEventArgs(ButtonBase.ClickEvent));

(routed events are part of WPF, not winforms), however you've referenced the wrong namespace

'System.Windows.Forms.ButtonBase' does not contain a definition for 'ClickEvent'

Go to the top of your class and remove the following

using System.Windows.Forms;

and replace it with

using System.Windows.Controls.Primitives

Blam.

answered Aug 13 '13 at 18:45

That seems to fix it; however, now I can't use `OpenFileDialog` – user1477388 Aug 13 '13 at 18:46
2

@user1477388 Use `Microsoft.Win32.OpenFileDialog`. Forget winforms, it's a really old technology no one cares about anymore. – Federico Berasategui Aug 13 '13 at 18:47
1

@HighCore: Your original version is more correct. Winforms compared to wpf is crap. – Aug 13 '13 at 18:49
Okay, okay, please don't kill my inbox with a winforms/wpf debate. Besides, WPF wins. So there's no point. – Aug 13 '13 at 18:51
@Will: Obviously WPF is better, just pointed out that WinForms is still quite relevant in some regards. – H.B. Aug 13 '13 at 18:53

score 2 · Answer 2 · edited May 23 '17 at 11:52

2

Clicks should not fire on MouseDown.
Put the TextBlock in a Button or use a Hyperlink.
That code looks fine otherwise, however you have a using for the wrong namespace (WinForms) instead of WPF. You want: System.Windows.Controls.Primitives

edited May 23 '17 at 11:52

Community

1
1

answered Aug 13 '13 at 18:40

H.B.

166,899
29
327
400

score 0 · Answer 3 · answered Aug 13 '13 at 18:41

0

Put the code that you want to be called at the Click event into a method
Call this method at the Click event
Call this method at the MouseDown event

answered Aug 13 '13 at 18:41

meilke

3,280
1
15
31

Actually, this solves the problem since I simply called Button_Click directly from my XAML code instead of calling another method to call it from the .cs code. I am still wondering why it won't find that event though. – user1477388 Aug 13 '13 at 18:44
1

I did that for the longest time, too. Unfortunately, you end up using null parameters etc. which is always ugly. Use a dedicated method that only takes parameters that are actually used. Easier on the eye. – meilke Aug 13 '13 at 18:52

No definition for ClickEvent?

3 Answers3