The third-party website here is Servebase, a company that provides payment solutions.
They return data to our URL hosted at say, test.net\mypage.aspx
The form field simply has the ekey I want, and I read it - I need a way to access this from my C# app - a stand alone app.
Hence, I write it to a file with a unique id - see attached.
Once this is done, the control is back to my C# app - I need to retrive this file and read the EKEY value in it. I dont know the filename as its dynamically generated for ease of use. If I give the same filename, it never gets updated for every request.
The third-party website here is Servebase, a company that provides payment solutions.
They return data to our URL hosted at say, test.net\mypage.aspx
Honestly, I don't think it works that way - in other words, they don't return the data to your URL. More likely you make a call to their service inside your web page, the data gets returned and you write out the file with the unique name. It is important to make this distinction in order to understand what is going on. Please post the code that makes the call to their service (if you don't want to post it publically, then send it to me in a private message).
Originally Posted by CM2013
The form field simply has the ekey I want, and I read it - I need a way to access this from my C# app - a stand alone app.
Hence, I write it to a file with a unique id - see attached.
As I mentioned before, you are going to run into problems storing the files. There are file locking issues to content with, security issues and so forth. This approach really isn't too scalable or robust.
Originally Posted by CM2013
Once this is done, the control is back to my C# app - I need to retrive this file and read the EKEY value in it. I dont know the filename as its dynamically generated for ease of use. If I give the same filename, it never gets updated for every request.
Rather than having the C# app call into your web page (where the web page makes the call to Servebase to retrieve the key), you write the file and then access the file from your c# app, why not have the web page just return the data directly (without writing the file)?
So if I show you how to create a WCF service, that you call with the C# app, have you pass in the URL, and it returns an eKey all within the same call, will that work for you?
Last couple of questions. If a URL is passed (say URL_1) and the eKey (e.g. eKey1) is returned, does the same URL (i.e. URL_1) ever get passed again? If so, would the eKey (e.g. eKey1) from the first call still be valid? Or would a new eKey be returned? Understanding this helps determine if caching should be used.
So if I show you how to create a WCF service, that you call with the C# app, have you pass in the URL, and it returns an eKey all within the same call, will that work for you?
Last couple of questions. If a URL is passed (say URL_1) and the eKey (e.g. eKey1) is returned, does the same URL (i.e. URL_1) ever get passed again? If so, would the eKey (e.g. eKey1) from the first call still be valid? Or would a new eKey be returned? Understanding this helps determine if caching should be used.
You are right - Iam actually calling their URL which could be handled by a webservice on their end.
I would figure out writing a webservice as myself - please do not spend your time on it.
Right now,am looking at iframes which is what is compliant with Servebase. We are supposed data thro' iFrame to an URL so it inturn does sending the ekey etc.
* The Best Reasons to Target Windows 8
Learn some of the best reasons why you should seriously consider bringing your Android mobile development expertise to bear on the Windows 8 platform.