Open default client window along with attachment in C#

Question

0.00/5 (No votes)

See more:

I have tried below code:

C#

var proc = new System.Diagnostics.Process();

  proc.StartInfo.FileName = string.Format("\"{0}\"", Process.GetProcessesByName("OUTLOOK")[0].Modules[0].FileName);

  proc.StartInfo.Arguments = string.Format(" /c ipm.no
te /m {0} /a \"{1}\"", "someone@somewhere.com", @"C:/Users/gokul/Desktop/ACT .zip");

  proc.Start();

What I have tried:

But this code always returned outlook window.

But I need default email client window which is from our device, Like MAIL, Google chrome , OUTLOOK

Please share me your answers,

Posted 24-Aug-16 5:03am

Member 11590270

Updated 24-Aug-16 5:17am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2016-08-24T05:17:00

Um... this is tagged as Javascript as well as C# - which implies you are writing this as a web app running in the client browser.

Which means that won't work, not at all - or at least it won't work in production, even if you do get it to work in development.
Process.Start is C# - which always runs on the Server, never on the Client. Which means that the application - whatever it is - always opens on the Server, where the user can't see it, not on the Client where he could. It appears to be working (at least in part) in development because the Client and the Server are the same machine. This isn't the case in production where the two machines can be literally thousands of mile apart.

You cannot cause any application to run on a client using server code except in very, very specialised circumstances which ado not occur in 99.999% of cases. Specifically, the client must be running IE (not Edge, or Chrome, or Firefox, or Opera, or ...); he must permit the download of an ActiveX control (disabled by default); he must permit an ActiveX control to run (disabled by default); and you must write an ActiveX control to do it.
This doesn't happen.