2
Hello all!
Working in vb.net, with VS 2003.
I have 2 projects in a solution. Pretty much a client server setup. Project A controls when a message box open up on Project B. Click a button on A, and the message box will open on B. and the message box in this case is a small form. Pretty much all the control I have is the forms. Depending what button you press on A, that will react on project B by a certain form opening up. Some forms are just message boxes, other are forms a user can do somethng with. And then the forms close on there own with a timer, or by the user.
So I have been using filewatch process to make this work. Form A creates a file, with a diffrent extension on it. Based on what the extension is, will tell project B when form to show. Then the file will be deleted. This has worked pretty well until recently.
Now I have 13 of these file watch processes going on. And at one time, they were very reliable, but now, I can't get them to run all at once.
So how reliable are file watches, should I be able to get this to work, or should I try another way? And what is a better way? The form "Message boxes" are only displayed for about 5 to 7 seconds. The forms that can be used by a user are only open from 20 to 15 seconds.
If your interested, can give you some code. It's rather lengthy so I will let you be the judge of that. I'll post if some body needs to see it. I have tried .Net remoting, but I couldn't get it to work right, and at the time this seemed like a simple way to go. The only thing that bugs me about this, is the file watch process keeps going all the time. And I need the pro0gram to be fast. In the same sence, I need it to open a form on 10 to 20 diffrent pc on a small network almost at the same time. At least a within a second. And thefilewatch does that for me.
Any thoughts or suggestions would be greatly appreciated!
Thanks!
Rudy
