We Keep Coding

C# How to start .bat File with the normal Behaviour of Windows

I created this simple .bat File:
mstsc C:\Temp\example.rdp
DEL C:\Temp\example.rdp
The normal behaviour of the .bat file is to open the rdp dialog and wait til I close the RDP connection. After that the .rdp file will be deleted.
This works perfect for me.
Now I want to open the .bat file from my C# WPF project with a click on a button.
Process p = new Process();
p.StartInfo.FileName = #"cmd.exe";
p.StartInfo.WorkingDirectory = #"C:\Temp";
p.StartInfo.Arguments = "/k " + "example.bat";
p.Start();
I tried all different arguments but the result is always the same the .bat file won't wait for the mstsc command to finish.
Do you have an idea to get this work?
Edit:
I want the .bat file because i want to delete the .rdp file although my program isn't running and i don't want to close all rdp connections when i close the program.

Why are you not directly running mstsc?
Process.Start("mstsc", "dir-to-blah.rdp").WaitForExit();
File.Delete("dir-to-blah.rdp");

try using the "start" command.
start is documented here: https://ss64.com/nt/start.html
you should be able to do something like
Process p = new Process();
p.StartInfo.FileName = #"cmd.exe";
p.StartInfo.WorkingDirectory = #"C:\Temp";
p.StartInfo.Arguments = "start /w" + "/k " + "example.bat";
p.Start();
(as usual, my code is completely untested - leaving the final solution up to the OP)

Why doesn't my argument pass to CMD in Windows Forms app?

This is my first Windows forms app.
I'm trying to pick a folder and list all files in that folder to a txt file.
This just instantly close the console window without passing the arguments.
If I put it in a bat file it works like it should.
Any ideas?
myPath = fbd.SelectedPath;
Process p = new Process();
ProcessStartInfo psi = new ProcessStartInfo("cmd.exe");
psi.Arguments = "/K for /r " + myPath + " %%g in (*) do echo %%~ng >> " + myPath + "test.txt";
p.StartInfo = psi;
p.Start();

Put the whole /k or /c command in quotes [*]. Use quotes around the file paths in case they contain spaces. And don't double the percent in the %g loop variable. That's only required in batch files. For example:
"/k \"for /r \"" + myPath + "\" %g in (*) do echo %~ng >> \"" + myPath + "\\test.txt\"\""
[*] Quoting the entire command isn't necessary in this case because the first character of the command isn't a quote. However, it's a good practice in general since cmd strips off the first and last quote if a command starts with a quote. This breaks a command such as "C:\\some path\\command.exe" "C:\\another path\\file.ext", which cmd would execute as C:\some path\command.exe" "C:\another path\file.ext.

why you are not directly running your .bat file ?
save whatever you want your application to do on a .bat file place it in the "bin" folder of your application, then add a namespace using system.diagonostics ; and generate and event like form load or button click and then write the following code process.start("name of your .bat file")

Unzip files in C# (using winzip command line)

I'm trying to create program to unzip files. I need to use winzip command line. I try to send in argument command to cmd, but it didn't work, because cmd didn't know my command. When I pasted manually command, it works.
var process = new ProcessStartInfo("cmd.exe");
var command = "/c WZUNZIP -spassword" + "\""+ "C:\my path\file.zip" + "\"" + " " + "\"" + "C:\my path" + "\"";
process.UseShellExecute = false;
process.Arguments = command;
Process.Start(process);
I tried to create .bat file and execute this file in my program, but like before it didn't work, when I executed it in my program and when start manually it works.
start cmd.exe /c WZUNZIP -spassword "C:\my path\file.zip" "C:\my path"
var process = new ProcessStartInfo("cmd.exe", pathToBatch);
Process.Start(process);
Mayby u know, the best way to execute .bat file in C#.
I need to use winzip, because only it provides encoding for my files. I tried to use DotNetZip and during uziping program threw exception that it can't be unziped, because library can't operate this files.

Apologies for adding as an answer (I currrently don't have enough rep for posting comments), but hopefully this will help.
What is the reason that you need to use winzip command line? Could you use ionic zip instead (http://dotnetzip.codeplex.com/ - also obtainable via NuGet in Visual Studio). I've used it a few times to zip files up and I know it unzips just as well.
The benefit I can see of not using the winzip command line is that you don't get the command prompt window popping up onscreen while the unzip is in progress.
Otherwise, as Noodles has suggested, the quotes must go around the whole path, not just the folders containing the spaces.
Edit: There is a similar SO post here: unzip file in C# via Winzip and its cmd extension

If you want to execute any thing you can use the process class with ProcessStartInfo.Arguments.
You can see more at:
MSDN: Process Class
MSDN: ProccessStartInfo.Arguments Property
And my question is because I don't understand for what you want it,
why don't you use system.IO.Compression or SharpzipLib? You can look up more info and download it with nugget.

Quotes go aroundthe entire path incl drive letter "c:\some folder\some file.zip"
To unzip
Set objShell = CreateObject("Shell.Application")
Set Ag=Wscript.Arguments
set WshShell = WScript.CreateObject("WScript.Shell")
Set DestFldr=objShell.NameSpace(Ag(1))
Set SrcFldr=objShell.NameSpace(Ag(0))
Set FldrItems=SrcFldr.Items
DestFldr.CopyHere FldrItems, &H214
Msgbox "Finished"
and to zip
Set objShell = CreateObject("Shell.Application")
Set Ag=Wscript.Arguments
set WshShell = WScript.CreateObject("WScript.Shell")
Set SrcFldr=objShell.NameSpace(Ag(1))
Set DestFldr=objShell.NameSpace(Ag(0))
Set FldrItems=SrcFldr.Items
DestFldr.CopyHere FldrItems, &H214
Msgbox "Finished"
and create a blank zip.
Set Ag=Wscript.Arguments
Set fso = CreateObject("Scripting.FileSystemObject")
Set ts = fso.OpenTextFile(Ag(0), 8, vbtrue)
BlankZip = "PK" & Chr(5) & Chr(6)
For x = 0 to 17
BlankZip = BlankZip & Chr(0)
Next
ts.Write BlankZip

Here's what works for me:
System.Diagnostics.ProcessStartInfo procStartInfo = new System.Diagnostics.ProcessStartInfo("cmd", #"/c WZUNZIP.EXE -ye -o " + zipPath + " " + ExtractedFilesLocation);
procStartInfo.UseShellExecute = false;
System.Diagnostics.Process proc = new System.Diagnostics.Process();
proc.StartInfo = procStartInfo;
proc.Start();
proc.WaitForExit();

Unzip a file from network

I'am trying to unzip a file from netowrk in C# with this syntax:
string dezarhiverPath = ConfigurationSettings.AppSettings["PathWinZip"] + "\\WINZIP32.EXE";
ProcessStartInfo pro = new ProcessStartInfo();
pro.WindowStyle = ProcessWindowStyle.Hidden;
pro.FileName = dezarhiverPath;
pro.Arguments = " -e -j -o " + prmSource + " " + prmDestination;
Process x = Process.Start(pro);
x.WaitForExit();
If I use this sintax and my zip file is on local on my computer it works bbut when I move the path and i'am trying to unzip from a location on network doesn't work.Remain at line "x.WaitForExit()".If I try manualy to unzip it works.My user has rights to this location.I don't have error.
Can somebody help me to solve this problem?

Use external tool for unzipping like SharpZipLib because this way, you dont need to be depend of external tools like winzip.
Or even better : with .net 4.5 use System.IO.Compression.ZipFile, this is in assembly System.IO.Compression.FileSystem
For examples see MSDN site http://msdn.microsoft.com/en-us/library/ms404280(v=vs.110).aspx

Open a pdf file programmatically at a named destination

I would like to open a PDF file at named destination using WinForms (C#). Here is my code:
System.Diagnostics.Process myProcess = new System.Diagnostics.Process();
myProcess.StartInfo.FileName = "Acrobat.exe";
myProcess.StartInfo.Arguments = "/A \"nameddest=Test2=OpenActions\" C:\\example.pdf";
myProcess.Start();
It always opens the file at page 1 even having the destination Test2 at page # 10. It basically ignores the destination parameter. However if I use another parameter like the page number it works fine. For example:
myProcess.StartInfo.Arguments = "/A \"page=5=OpenActions\" C:\\example.pdf";
will always open the PDF document at page 5.
Thanks in advance for your help

I use the following code:
string strNamedDestination = "MyNamedDestination"; // Must be defined in PDF file.
string strFilePath = "MyFilePath.pdf";
string strParams = " /n /A \"pagemode=bookmarks&nameddest=" + strNamedDestination + "\" \"" + strFilePath + "\"";
Process.Start("AcroRd32.exe", strParams);
Note the "/n" inside the params. It makes Adobe to always open a new document. Otherwise, if the document was already opened, it doesn't move it to the right Named Destination. It depends on the behaviour you want for your application.

Regarding the Adobe documentation when opening a PDF document from a command shell, you can pass the parameters to the open command using the /A switch using the following syntax:
myProcess.StartInfo.Arguments = "/A \"nameddest=Test2=OpenActions\" C:\\example.pdf";
If I omit the OpenActions parameter everything works fine like:
myProcess.StartInfo.Arguments = "/A \"nameddest=Test2\" C:\\example.pdf";
I'm not sure why the OpenActions breaks opening the file but with omitting it works fine.

I have a csv with 5 columns.
Column1 contains PDF names and Column5 pagenumbers.
The executable displays the csv.
When I doubleclick on a line in the csv the following code is executed :
ListViewItem item = lvwItems.SelectedItems[0];
Process myProcess = new Process();
myProcess.StartInfo.FileName = "Acrobat.exe";
myProcess.StartInfo.Arguments = "/A page=" + item.SubItems[4].Text + " " + item.Text;
myProcess.Start();
This opens the selected PDF which name is in item.Text on the page which pagenumber is in item.SubItems[4].Text

Have you set up the destinations? You need to be have the standard or professional versions of Adobe Acrobat in order to do this:
http://kb2.adobe.com/cps/317/317300.html

Adobe Reader has a few bugs regarding opening to named destinations. Take a look at http://xenon.arcticus.com/open-pdf-named-destination-dde-c-c for some information and workarounds.