By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,887 Members | 1,154 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,887 IT Pros & Developers. It's quick & easy.

Request.Querystring and System.Net.Webrequest

P: n/a
Is there a known issue about System.Net.Webrequest interfering with
Request.Querystring? My web application pulls a record ID from a URL,
then uses that record ID to pull information a database. I then use
that pulled information to get information from a webservice with
System.Net.Webrequest and System.Net.Webresponse.

Each one works independently, but when I try to use them both in the
same site (not even in the same class--the Request.Querystring is in the
codebehind, and the System.Net.Webrequest is in a standalone class as
part of a shared function), the Request.Querystring returns null every time.

Any ideas or suggestions (or alternative ways to access a
webservice--this is my first attempt)

..NET 2.0
IIS 6.0
Visual Web Developer Express Edition

Thanks,

Dave
Feb 7 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Well whatever the problem was, it's gone now.

Dave Cowart wrote:
Is there a known issue about System.Net.Webrequest interfering with
Request.Querystring? My web application pulls a record ID from a URL,
then uses that record ID to pull information a database. I then use
that pulled information to get information from a webservice with
System.Net.Webrequest and System.Net.Webresponse.

Each one works independently, but when I try to use them both in the
same site (not even in the same class--the Request.Querystring is in the
codebehind, and the System.Net.Webrequest is in a standalone class as
part of a shared function), the Request.Querystring returns null every
time.

Any ideas or suggestions (or alternative ways to access a
webservice--this is my first attempt)

.NET 2.0
IIS 6.0
Visual Web Developer Express Edition

Thanks,

Dave

Feb 7 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.