Re: System.Timers.Timer doesn't stop with Stop() - C# Discussion Boards

Abhishek Sur21-Jul-09 2:55

Abhishek Sur

21-Jul-09 2:55

I think the code block where new ElapsedEventHandler is added is called more than once.

It means when even is raised, more than once the myMethod will be called, and hence the timer will be incremented.

Abhishek Sur

My Latest Articles
Working with Excel using MDAC

Basics on LINQ and Lambda Expressions

Create .NET Templates

SimpleData21-Jul-09 2:58

21-Jul-09 2:58

So can I add more than one ElapsedEventHandler to my timer right?

If I

myTimer.Elapsed += new ElapsedEventHandler(Method1);
myTimer.Elapsed += new ElapsedEventHandler(Method2);

then when myTimer ticks both Method1 and Method2 runs, right?

If I

myTimer.Elapsed += new ElapsedEventHandler(Method);
myTimer.Elapsed += new ElapsedEventHandler(Method);

then when myTimer ticks Method will run twice, right?

stancrm21-Jul-09 3:18

21-Jul-09 3:18

right

DoctorMick21-Jul-09 3:18

DoctorMick

21-Jul-09 3:18

Right, right and right again.

SimpleData21-Jul-09 3:19

21-Jul-09 3:19

Thank you, then problem solved Big Grin | :-D

PIEBALDconsult21-Jul-09 4:13

PIEBALDconsult

21-Jul-09 4:13

Yes, but I doubt you want to do that; did you do that accidently?

SimpleData21-Jul-09 4:14

21-Jul-09 4:14

Yes.

Abhishek Sur21-Jul-09 21:37

Abhishek Sur

21-Jul-09 21:37

So on every block I think it is better to do

myTimer.Elapsed -= new ElapsedEventHandler(Method);
myTimer.Elapsed += new ElapsedEventHandler(Method);

By this way even if this block is running more than one, everytime it will remove the eventhandler and then add it. Provided, if you are unsure that this block will run more than once.

Thumbs Up | :thumbsup:

Abhishek Sur

My Latest Articles
Working with Excel using MDAC

Basics on LINQ and Lambda Expressions

Create .NET Templates

SimpleData21-Jul-09 23:28

21-Jul-09 23:28

Thank you, that is a nice way of doing it too.

But I solved it with adding a global int called Session with default value 0. And everytime I get this adding ElapsedEventHandler if this session is greater than 1 I don't add it.

Abhishek Sur22-Jul-09 21:47

Abhishek Sur

22-Jul-09 21:47

yes .. this is a possible way...
nice to hear that you solved it.

Cheers. Thumbs Up | :thumbsup:

Abhishek Sur

My Latest Articles
Working with Excel using MDAC

Basics on LINQ and Lambda Expressions

Create .NET Templates

PIEBALDconsult21-Jul-09 4:11

PIEBALDconsult

21-Jul-09 4:11

Ummm... what? I didn't understand what you were trying to say.

What are you trying to accomplish and what problem are you having?

SimpleData21-Jul-09 4:13

21-Jul-09 4:13

I had a timer which I stopped and started some time later. But when I started it for the second time it was doing what it was doing when ticked twice. It turned out that I was adding new eventhandler twice Smile | :)

Luc Pattyn21-Jul-09 4:17

Luc Pattyn

21-Jul-09 4:17

So in the end this article[^] is about you?

Smile | :)

Luc Pattyn [Forum Guidelines] [My Articles]

The quality and detail of your question reflects on the effectiveness of the help you are likely to get.
Show formatted code inside PRE tags, and give clear symptoms when describing a problem.

SimpleData21-Jul-09 4:19

Debugging unmanaged DLL called from managed C#

21-Jul-09 4:19

Seems that way.

Chesnokov Yuriy21-Jul-09 2:09

21-Jul-09 2:09

I've got simple console C# project that calls unmanaged DLL with Interop. I need to step into native DLL function either from C# or debug native DLL and break in C++ debugger.

I set up Enable unmanaged code debugging in C# console.
The DLL function is called correctly, e.g. it prints the message to console.

But as I run DLL with F5 and it invokes C# console, the break points do not work.
Nor can I step into DLL unmanaged code from C# console

Чесноков

stancrm21-Jul-09 3:23

21-Jul-09 3:23

Have you tried this one ?

http://social.msdn.microsoft.com/Forums/en-US/vsx/thread/91232ee3-a70c-43e4-b9f2-f8ff860c60ca/[^]

Chesnokov Yuriy21-Jul-09 3:42

21-Jul-09 3:42

that one worked, 'Enable just my code debugging'. Great!!!

Чесноков

Chesnokov Yuriy21-Jul-09 4:04

21-Jul-09 4:04

however you still can not run native DLL which is invoked in C# and stop at bps in DLL project Frown | :(

Чесноков

Chesnokov Yuriy22-Jul-09 20:37

Acess violation exception before Main?!?

22-Jul-09 20:37

I've got all setup as described and was debugging native DLL normally, while on the other project run it just stopped stepping into the native DLL?

What happened as I did not touched the settings they were before???

Чесноков

Olivier Gautherot21-Jul-09 2:08

21-Jul-09 2:08

Hi, I have a small application that is exhibiting an AccessViolationException before it even enters Main(). I found this out after the pilot in our production environment started failing from time to time - it would enter some infinite loop somewhere at the end of Main() after all useful code has been executed. I found the access violation when running the app in the debugger.

The tricky bit is that it does not happen in controlled source code (the failure occurs before I reach Main()) so the actual issue is difficult to determine. I would suspect some kind of stack overflow but do to know how to troubleshoot this in Visual Studio. The app is in C#. Any suggestion to get started?

Olivier Gautherot21-Jul-09 2:58

21-Jul-09 2:58

Maybe one more detail: it is a console app and is complaining about a Windows Form (in an attempt to issue a SendMessage()).

However, I do not have explicit instantiations of a Windows Form... Weird...

stancrm21-Jul-09 3:01

21-Jul-09 3:01

How about in project properties -> output type ?
It must be "Console Application".

Olivier Gautherot21-Jul-09 3:04

21-Jul-09 3:04

It is. .NET target is also set to 2.0 for the production environment.

stancrm21-Jul-09 2:59

21-Jul-09 2:59

Have you tried to reinstall .NET Framework and run it as administrator ?

Olivier Gautherot21-Jul-09 3:03