View Complete Post
I have a winforms application.
From the main application i am starting another app using the following code:
When this app starts, i want to kill the main app. Close the open application.
how can i do it?
There is aprocess.kill but it is not taking any arguments. How can i kill the main app from the second app?
I have question on this backup\recovery.Let's assume there is a disaster at 6:14 pm and our recovery model is full and we take Full back up's at 12:00 am and differential's at 6 hrs interval and transactional one's for every 5 mins. So, in this case
to recover the db, we apply our FB(12:00)+Differential(6:00pm) + Transacational log 1(6:05)+transactional log(6:10) . We need to backup the tail to get the point in time restoration. Could any one tell when shall we backup the tail log?
is it before doing the restoration??
I have the database backup of one webapplication.
i have restored it and create a new webapplication using the restored database. now, i dont know how to access the site collections. Please guide me. Thanks in advance.
I have created a sequential workflow using visual studio. I also created a content type inherited from the workflow-task content type. Workflow creates a task-item in the task list. I want to update the workflow task using the silverlight client
object model. I find on the internet and WorkflowTask.AlterTask() method to update the workflow task item. But I didn't find the equivalent of WorkflowTask.AlterTask(). Can any one help me to update the workflow task from the silverlight client object model?
I also want to terminate the workflow instance using silverlight client object model, but i didn't find any way to terminate the workflow using client object model?
Same question as mentioned in following thread.. but Environment is SP 2010.
1. Is it possible to cancel or terminate workflow through SPD 2010?
2. Is it possible to execute custom code in SPD 2010?
[[[I already checked the 3rd party one which supports Custom code execution. (http://sharepointblog.virtosoftware.com/blogs/virtoteam/archive/2010/03/11/how-to-terminate-all-faulting-sharepoint-workflows.aspx)
Please dont propose this solution.]]]
Is there any other solution (free one)?
I've been searching for a while for a solution to accomplish above subject, I have a win app for handhelds in which the user can navigate through several windows forms form.showdialog() The question is how to close all windows and terminate the app when user press exit button.
process.getcurrentprocess().kill(); --> didn't workForeach (Form frm in Application.OpenForms) --> doesn't work in .net Compact Framework frm.Close();
I mean if I use form.show() to open the windows, it works with Application.Exit();, but I want to prevent the user navigate away from the current form thru the icon for open windows on the right lower corner of the handheld, unless he press the close button of the form, that's why I use form.showdialog(), the other approach could be to show only the current open form of the application if the user press the icon for the open windows on the right lower corner.
Ideas welcome, thx
.Net 3.5 My communication between the application server and various clients (on other machines) via Named Pipes is generally okay, but what if the client (the small app that is listening on the named pipe) is not up and running? The application
on the server has many responsibilities and having it wait forever to send info via the pipe to a particular client is not acceptible.
pipeIO = new
A week ago my system's hard drive suffered a rather tedious hard drive failure, which I was able to resolve but has created some other issues after the fact. The Hard drive developed a fault, and in order to restore my system, I was forced to use BartPE
as a live cd, and transfer the data from the "defective" drive to the new drive. for some reason the defect caused a fault which prevented most Imaging software from being able to image the drive over so I was forced to use XCOPY.
Yes, this actually worked, and as I am writing this post, it is my exact same system that I used last week, with the minor problem of having to reactivate windows when I finally was finished.
However, there apparently is a minor issue with the NTFS security descriptors. I am not surprised, since I was using the BartPE loaded windows system to transfer the files I expected a little "renaming" of security descriptors to occur in the process.
But when faced with the prospect of rebuilding the entire system from scratch, this was a reasonable cost. However, this tragically confused Sql Server.
As we know SQL Server Installs Several Groups into the User And Groups of the system: