ASP.NET - 与其他网站的交互
我想知道是否可以使用我自己的网站与其他网站进行交互。
场景如下：
假设我有一个 Lockerz 帐户，您可以在该帐户中执行日常任务来赚取积分。每月一次，您可以兑换这些积分以获得 iPod、MacBook 或其他物品等奖品。我知道这听起来很荒谬，但请继续听我说。
要获得本网站的会员资格，必须得到会员的邀请。因此，我会获取您的电子邮件地址，然后登录我的帐户，然后从那里向您发送邀请。
我想做的是创建一个网站，用户在文本框中输入电子邮件并按下提交按钮。从那里，程序在幕后将我的登录信息和用户的电子邮件地址发送到 lockerz 并发送邀请。一切都无需离开我的网站。
我使用 ASP.NET 和 VB 代码隐藏已经有一段时间了，所以我了解其中的基础知识。我只是想知道我想做的事情是否可能。如果是这样，有人可以将我重定向到某种教程或指南，让我了解这方面的基本知识。
谢谢
I was wondering if it is even possible to interact with other websites using my own.
Here is the scenario:
Lets say I have a Lockerz account, which is a place where you do daily tasks to earn points. Once a month you can redeem those points to get prizes such as an ipod, macbook, or other items. I know that sounds rediculous, but stay with me.
For someone to gain membership to this website they must be invited by a member. So I get your email address then log in to my account, then send you an invite from there.
What I want to do is create a website where a user enters their email into a textbox and presses a submit button. From there the program, behind the scenes, sends my login information, and the users email address to lockerz and sends the invite. All without ever leaving my site.
I have worked with ASP.NET with VB codebehind for a while now, so I understand the basics of that. I am just wondering if what i want to do is even possible. If so, can someone redirect me to a tutorial or guide of some kind that will give me a basic knowledge on this.
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您必须在 HTTP 级别进行工作，发送 POST 和 GET 请求。
幸运的是，.NET 有 WebRequest 和 WebClient 类可以帮助您。
You'll have to work down at the HTTP level, sending POST and GET requests.
Fortunately, .NET has the WebRequest and WebClient classes to help you.
WebClient 可能是您最好的起点...但我想再等等。
像这样的网站往往会采用一些相当严格的欺诈保护措施。当多个帐户使用一个 IP 或以其他方式以可预测的模式执行操作时，禁止、阻止或至少忽略操作。
WebClient 也不会加载 JavaScript，因此您可能无法访问页面的所需部分。
无论哪种方式，您都不需要在网络服务器上执行此操作 - 我首先将初始连接代码在本地编写为一个简单的脚本。这将使测试速度更快。
WebClient would probably be your best starting point... But I would hang on a second.
Websites like this tend to employ some pretty intense fraud-protection. Banning, blocking or at least ignoring actions when multiple accounts use one IP, or otherwise do things in a predictable pattern.
WebClient isn't going to load up the JavaScript either so you might you can't access required parts of the page.
Either way, you don't need to do this on your webserver - I'd start off by writing it initial connect code locally as a simple script. It'll make testing it a lot faster.