I'm trying something interesting..... I need to interface with another vendors .NET web service. however they are not ready yet and cannot wait ... meanwhile they have a VB6 windows app .... from which I want them to be able to interface with my .NET web app in the interim.
Now the issue is how to pass data over to my web app. Typically their VB6 app spits out an extract file ..single row variable length....
From the VB6 app I am thinking of them launching my app like
doe 123 Street Road'
..then i can read from Request.QueryString("filespec") ....and do what I need to do. Now granted sometimes filespec might be far too long in length to fit in the URL limit, .. I suppose .. so I need to know the limit.
In that case I am thinking of creating a batch file to FTP the whole extract file itself ... and then lauching my site with the name of the uploaded file automatically after that.
what do you think of these 2 approaches? I think there is a limit on the querystring but i can't remember.... is the 2nd method better overall while I wait for true web service to pass the file as XML to the web service?
The show must go on according to my boss!
Now the issue is how to pass data over to my web app. Typically their VB6 app spits out an extract file ..single row variable length....
From the VB6 app I am thinking of them launching my app like
doe 123 Street Road'
..then i can read from Request.QueryString("filespec") ....and do what I need to do. Now granted sometimes filespec might be far too long in length to fit in the URL limit, .. I suppose .. so I need to know the limit.
In that case I am thinking of creating a batch file to FTP the whole extract file itself ... and then lauching my site with the name of the uploaded file automatically after that.
what do you think of these 2 approaches? I think there is a limit on the querystring but i can't remember.... is the 2nd method better overall while I wait for true web service to pass the file as XML to the web service?
The show must go on according to my boss!