Thanks Planoie, from reading your other posts in these forums you seem very knowledgable and I was hoping you'd see my question - consider yourself trapped in my twisted world for a few hundred posts! LOL ;) Please endulge me a bit longer...
Anyway so what you are saying is that "Remoting" is not actually what I need, but to use a web service as the intermediary piece of the puzzle. From what I have read all roads seem to point to remoting but now as I think about it, remoting is not necessary, I don't think.
I did a test earlier and I can instantiate a webservice from the vb
app and call it's functions no problem - the question I have really, should the asp.net portion and the vb
.net portion be calling the same webservice object? How would I store the data in the WS object and trigger the vb
exe to know when something was received. Can I hook the vb
portion into some event from the web service? I am a little fuzzy on this part. Technically the vb
server portion is not looking to push any data out to the IE browser, the other way round, the ie browsers are pushing the data to the vb
exe via a web service - right? (I do however want to make a push server but that is another project entirely)
Any further insights into my middle piece of the puzzle is greatly appreciated - my eyes are bleeding and i have not slept (much).