I do not believe you can have the files execute w/o something running on the other end.
MSDN has plenty of info.
I specialize in VB 6.0 (not .NET), so what I say will mostly apply to that.
The Winsock control is probably the best way to do this. the Inet will work too, but is more geared for getting documents off the WWW. Both only come with Profesional and Enteprise Editions. I haven't actually done this yet, but I will try to give a simple tutorial based on the subs.
On the server:
- Set the LocalPort and Protocal properties to what ever.
For each client: - Set the RemoteHost, RemoteHostIP, and the RemotePort properties to the client.
- Call Connect to connect to the remote computer; Wait for the Connect event.
- Call SendData to tell the client go.
- Wait for the SendComplete event.
- If there is a response in ur packet format, wait for that.
- Call Close
On each client:
- Set the LocalPort and Protocal properties to what ever.
- Set the RemoteHost, RemoteHostIP, and the RemotePort properties to the server.
- Call Listen, wait for the ConnectionRequest event, then call Accept to connect.
- Wait for the DataArrival event.
- Call GetData to get the data, then parse it (own code).
- If there is a response in ur packet format, call SendData to send the response.
- Run the file.
I don't think Shell() runs bats, but if you add Shell32.dll to your references, you can use the Shell object to run anything. (Verbs)