to fire the button event you need to send two fields

1) the button name & value
2) "__VIEWSTATE" and a valid value

to get a valid viewstate to post, your console app needs to do a get of the
page and parse the html for the viewstate value. it can then use this value
for the next post.

note: you can not save the veiwstate for future use, you must ask for a
current value before the post.

-- bruce (sqlwork.com)

I typed up a bit of an answer and planned on playing this one through and
then asked myself "what are you doing?" The reason is I thought through the
problem and could not see a logical reason why it HAD to be done this way.
The caps on HAD are very important. Let me illustrate.

First, let's look at classes. This could be a class library or a console
application; it really does not matter. But, here is a normal set of actions
on a class.

Class1 cls1 = new Class1();
cls1.InitialAction();
cls1.Save();

In windows forms or web forms, it is the same, only the input is coming from
user actions, so you have events that may hold the code for the actions (not
wise, as you should move business into its own classes, but it is doable in
.NET in both windows and web forms).

What you have asked is for it to work like this:

Class1 cls1 = new Class1();
Class2 cls2 = new Class2();

cls1.InitialAction();
cls2.SaveForClass1();

This is possible in a couple of situations

1. Class 1 Instantiates class 2
2. Class 2 is Instantiated with information from Class 1
3. Class 2 created class 1 (although this only works if
4. Class 2 is used as a link between data and business object (of which
class 1 is one)
5. There is a Class 3 that controls both Class 1 and Class 2

Many of the above are antipatterns. Although possible, they are not wise to
use. The web opens up additional possibilities, as it is stateless. In
theory, you can call any page (class) you desire with information from
another page (class). It is still an antipattern.

So, then I thought of reasons you might want to do this.

1. You have the same basic functionality in two pages if you do not.

Solution:
Move the save functionality into its own class and call from both location

2. You have the same bits on a form as well as same backend functionality

Solution:
Move both UI and code into a User Control. I would still considering moving
the actual business rules to a library anyway, but this is better than
posting to another page.

3. You want to show a confirmation

Solutions:

A) Forward after you save
B) Use Panel controls

*************************************************