Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m planning to have a desktop app interact with some .ASP or .ASPX pages on a server.
I’ve only done a little bit with .asp pages and I’m thinking I’d just Post or Get a URL with some variables:
MySite.com/Functions.asp?FunctionName=?Paramater1=somevalue?Parameter2=…
I’m wondering if there is any better way to go about this?
Am I missing something? Is there perhaps a better way to go about this?
Windows Communication Foundation or Web Services may be a better idea if you don’t require the overhead of the web page that ASP or ASPX requires. Those would be my suggestions for a better way to go about doing some of this. This is assuming you don’t have the pages built already and are at the early stages of designing this.
WCF is better if you just want to have services communicated back and forth, which can takes out some of what HTTP sets up and handles but could be better if you want to minimize the data passed around I’d think. WCF is part of the .Net 3.0 framework, so it may not be something to be installed necessarily as it may already be there by default in some cases. For example, this is what replaced .Net Remoting which would have been an older way to pass objects between machines in other ways using non-standard ports and may be a bit more work in terms of infrastructure. Web services are better if you don’t need all that there is to a web page and are OK with having messages go back and forth in SOAP or POX or some other format that doesn’t have to be HTML. Instead of an ASPX you’d have an ASMX and some code behind but in theory having a well-built set of services should help if you ever have to add on a web front-end or tie into someone else’s systems.