|
See my reply to Dave K.
/ravi
|
|
|
|
|
The only acceptable method is to write a service that monitors the process list and relaunches the application you're trying to keep open. Preventing the launch of Task Manager is not an acceptable solution in any legitimate environment.
The events in your application will not help you at all. Task Manager can kill a process just by stopping it's execution and freeing the memory it uses. Your app will never know what hit it.
|
|
|
|
|
Dave Kreskowiak wrote: Your app will never know what hit it.
Not really. The app receives a FormClosing event with CloseReason = CloseReason.TaskManagerClosing. Cancelling the close will cause TaskManager to display "The app you're trying to close is not responding.", allowing you to cancel the kill or "force" a kill. Because we're able to handle the event, we can start a new instance.
Dave Kreskowiak wrote: The only acceptable method is to write a service
I don't think a service can be safely used to start a desktop app since a service can start before a desktop exists.
/ravi
|
|
|
|
|
so u mean that it is enough to just specify new instance of my app, when the form _closed?
|
|
|
|
|
No, it's not. You have your applications state to worry about. What happens if the app is restarted?
And Ravi's suggestion does not work 100% of the time and is also dependant on the version of the .NET Framework you wrote the app against. Not every version supports telling you that TaskManager is responsible for closing your app. The FormClosing event and CloseReason enumeration didn't show up until .NET 2.0.
|
|
|
|
|
See my directly emailed reply.
/ravi
|
|
|
|
|
Ravi Bhavnani wrote: Not really. The app receives a FormClosing event with CloseReason = CloseReason.TaskManagerClosing. Cancelling the close will cause TaskManager to display "The app you're trying to close is not responding.", allowing you to cancel the kill or "force" a kill. Because we're able to handle the event, we can start a new instance.
I tried it some time ago and my but it didn't happen. My app was just killed.
|
|
|
|
|
Ravi Bhavnani wrote: Dave Kreskowiak wrote:
Your app will never know what hit it.
Not really.
I said it CAN close an app that abuptly. I know TM tries to close an app nicely at first, then if that doesn't succeed, it wips out the shotgun and takes aim.
Ravi Bhavnani wrote: I don't think a service can be safely used to start a desktop app since a service can start before a desktop exists.
If done properly, yes, it can. That includes checking to see if someone is actually logged on, who that person is, and if they have permissions to use the app.
|
|
|
|
|
Dave Kreskowiak wrote: If done properly, yes, it can. That includes checking to see if someone is actually logged on,
That's a good point.
Dave Kreskowiak wrote: I know TM tries to close an app nicely at first,
What I was suggesting is the app could allow itself to be closed and simply restart another instance when shutdown by the TM. Because the app gracefully shuts down, it can "pick up where it left off".
/ravi
|
|
|
|
|
I think you all being too mean. Sometimes there may be a valid reason for his requirements. In large network environments its common to want to administer applications that cannot be closed by the user.
And besides if he has bad intentions the fact that he needs to know this kind of thing goes to show he wont be creating some revolutionary super virus lol
You can try hiding the applciation from view and from the task bar, that may stop users knowing its there.
But your best bet is prob to look into creating a service, but i have not done one before so ask google or someone of the same intelligence level.
Thou i would image network administrators would be able to do something with permissions. Im not one thou so who knows
|
|
|
|
|
In a giant enterprise, you tell your staff "don't close any programs or you will be fired" and then they don't. If they do, you fire them. Network admins wouldn't use this type of garble to waste their time. They would, you know, utilize content filtering and network sniffering. Not try to go through this bullshit, which is a waste of time.
|
|
|
|
|
SALAM SIR;
how can made clinic project in c#.net?HOW CAN EASY LEANING VISUAL STUDIO .NET 2003 OR 2005?
THANKS SIR
mohammedali
|
|
|
|
|
Start with a basic programming book.
|
|
|
|
|
|
Where is the rest of the post?
The word "politics" describes the process so well: "Poli" in Latin meaning "many" and "tics" meaning "bloodsucking creatures."
जय हिंद
|
|
|
|
|
mohammedali2006 wrote: how can made clinic project in c#.net?
Programming.
mohammedali2006 wrote: HOW CAN EASY LEANING VISUAL STUDIO .NET 2003 OR 2005?
Programming.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Reposting the same question will not get you a different answer. You cannot ask a question that broad and expect a usable answer in the forums. You've given no details about the app you're writing (you ARE desgining and writing this, aren't you??), nothing about the problems you've encountering, and no specific questions to answer.
NO, NOONE IS GOING TO WALK YOU THROUGH THIS OVER AN INSTANT MESSENGER SESSION!
|
|
|
|
|
1. Keeps on asking for entire projects to just be handed over to him because he thinks he's so special.
2. Asks for them AGAIN AND AGAIN.
3. We mock him and yet he keeps asking.
mohammedali2006 -- GET OUT OF PROGRAMMING NOW! Stop pestering us! You are an idiot!
"Well, we're getting "F"'d at work. WPF, WCF, and WWF... WTF?" --John Simmons
|
|
|
|
|
He's never responded to any replies either - even if they are just flaming him. If he was at all serious, surely he would have at least made an attempt at a defense?
DaveBTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)
|
|
|
|
|
I think he's just a desperate fool hoping someone will fall for his clever trap and we hand him an entire project.
"Well, we're getting "F"'d at work. WPF, WCF, and WWF... WTF?" --John Simmons
|
|
|
|
|
You are either a troll, or a complete moron. Please go away.
|
|
|
|
|
Hi everyone,
I just recently started programming in C# (my first language, also) and I'm still pretty green.
I was wondering how, or if it's possible, to initiate a process in a parent form when a boolean variable in it's child form is set to "true".
I see events such as "text changed" but I need something in the parent that can catch a variable change on the child as soon as it occurs and take action right away. Any suggestions?
Thanks!
|
|
|
|
|
|
Not really what I need, but thank you.
|
|
|
|
|
I dont think you can take another approach. If you want to do something, when another form changes you need to listen for that change.
I dont know what your exact requirements are but perhaps you could use static functions in another class. Or just call the function by accessing the child forms parent form.
something like (though i have not tested):
FormOfTypeParent parentForm = (FormOfTypeParent)this.ParentForm;
parentForm.MyFunction();
FormOfTypeParent = the form type that is your parent form i.e. MainForm, Form1 etc.
calling this when a variable changes, make the variable a property i.e.
private bool changingThing = false;
public bool ChangingThing{
get{return changingThing;}
set{changingThing = value;ProcessChange();}
}
private void ProcessChange()
{
if(changingThing)
{
FormOfTypeParent parentForm = (FormOfTypeParent)this.ParentForm;
parentForm.MyFunction();
}
}
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
