digital work flow system using c# code

Question

1.00/5 (1 vote)

See more:

hi i'm nada,

i've a problem in sending or assigning a task from client to another client on the same server, and i'm wondering if i need a mail sever or i can do it using c# code only.
thanks.

Posted 10-Feb-11 5:53am

nada ezz eldien

Add a Solution

Comments

jim lahey 10-Feb-11 11:58am

provide some more information please

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)

Wendelius · Answer 1 · 2011-02-10T07:16:00

Hi,

With so little information it's actually quite impossible to answer your question. However few things are quite certain:
- You would need a centralized, safe store for assigned tasks. This could be an Exchange server if using Outlook Tasks or a database server with custom tables such as SQL Server or even a custom service written in C# which stores the tasks on the server. It depends on your requirements.
- You would need a client side connectivity. If SQL Server is used you can use standard classes from System.Data.SqlClient namespace to communicate with SQL Server but if you use Exchange server you need for example Office Primary Interop assemblies to communicate with Outlook or some other mechanism to view and modify data on the Exchange Server and so on.

So I think that you should concentrate on the requirements. What servers you already have, how (and by whom) it's going to be administered, does some server product provide the required functionality already which you could just use or do you need something extra etc.