Discuss using the System.Net namespace and associated Uri class in the .NET Framework to write code that leverages managed sockets, HTTP web requests, FTP, SMTP, P2P, etc.
This Forum Has Been Retired
This forum has been retired. It is locked, but is still available for review in the Archived Forums folder. Any future posts on this topic should be put in the Windows Communication Foundation, Serialization, and Networking forum.
Forum Tips and Valid Topics
Is this the right forum?
This forum is monitored on a regular basis by the Network Class Library (NCL) team. It is dedicated to questions about the System.Net namespace and the System.Uri class. If your question falls into this category, then you have come to the right place.
To ensure a timely response, we can only actively monitor questions that fall within the category above. Non-related questions will be locked or moved to the most appropriate forum.
General Forum Tips
Here are a few suggestions (in this order of relevance) that will help you to get the best answer to your question as quickly as possible:
Search for your question on the forums or in Visual Studio's help system first
-- it's likely someone may have already answered your question, and you
won't have to waste time waiting for it to be answered again
- Post in the correct forum
(see below) -- since the experts in various subject matters tend to
stick to the set of forums that focus on those topics, a question about
the C# yield keyword posted in the Common Language Runtime forum will
likely take a lot longer to be answered than the same question in the
C# Language forum.
- Give details about your problem
-- rather than "When I call Process.Start I get an exception, please
help", provide the exception type, message, and call stack. Many times
it helps if you attach a snippet of the network trace/sniff of the
error that shows the error. For getting network sniffs use Network
Monitor and for network traces use the built in System.Net tracing
according to this blog.
If possible, provide a succinct code snippet that demonstrates the problem. This lets us reproduce the problem on our end and allows us to come up with an answer where just a general question may not have had enough details. Having this information means we can answer your question more quickly, without having to ask you for these details and wait for your response. If you have a big code sample please trim it down to the relevant parts that will help us understand the problem better.
- Try to pinpoint the location of your error –
This will help us get to the root of the issue quickly. Saying
something like “My application cannot read from server” is less likely
to find a quick solution as compared to “My application gets a 505 not
found even though file is present since the trace shows that
FtpWebRequest does not handle a 505 error for an xyz command”
- Make sure your title summarizes the specific problem you have
-- since we try to answer the maximum number of questions we can with
our time, we often skim through question subjects to quickly find the
ones that we know the answers to. A question with a title of "Urgent!
Help needed!" is not as likely to get answered as a question with a
title of "How to define a sealed class using CodeDOM". A more
specific, detailed title is far more likely to get a response than
a general one.
you've received a correct answer to your question, either from a
Microsoft employee, an MVP, or the community in general, please mark
the post as answered.
You can do this with the "Mark as correct answer" button that appears
on the entry containing your answer. This step is important, since it
lets the Visual Studio search engine know that there is an answer in
that thread for others who may also have your problem. It also lets
people scanning the forums know that they can find an answer to that
question by reading the thread.
- Report bugs through Microsoft Connect, instead of on the forums
-- this site allows us to see the bugs in our bug
tracking database and get them assigned to the correct person. It also
allows you to follow the problem through to its resolution, and is a
much better way for us to handle issues you find than a bug report
posted on the forums.
- Use the report button -- as moderators we try to keep spam and inflammatory comments out of the forums. However if you do catch something that we missed, don't hesitate to use the report button so that we can keep the forums on-topic and a friendly place to go for help with your .NET questions!
When trying to figure out which forum is right for your question, here are some good candidates:
Network Class Library (System.Net) - for managed networking issues like HTTP, SMTP, Uri, FTP, Sockets etc.
Windows Communication Foundation (WCF) - for managed networking issues relating to WCF and SOA
.NET Framework Networking - for managed networking issues not relating to System.Net or WCF.
Common Language Runtime - for questions related to the runtime engine itself
.NET Development General - a general catchall for questions related to the BCL libraries, questions regarding the design of your code, etc.
Visual C# Language - for questions about the C# programming language, not the CLR or managed libraries
Visual Basic Language - same as above, but for VB
Visual C++ Language - same as above, but for C++ (both native and C++/CLI)
Windows Forms General - for questions about creating applications using the System.Windows.Forms libraries
ASP.NET Forums - for questions about writing web applications using ASP.NET
Development Forums - list of forums
Of course there are dozens of other forums available if your question doesn't fit into one of those categories. You can ask here where you should post if you have not yet found the right place.
- Search for your question on the forums or in Visual Studio's help system first -- it's likely someone may have already answered your question, and you won't have to waste time waiting for it to be answered again
- 36074Shakir 2011年3月21日 11:46
- 92132hollow82 2012年12月10日 11:51
- 154516smetah 2012年12月17日 21:26
- 109949Mathieu_D 2011年2月10日 11:12
- 81764Kiran Saravade 2012年12月11日 6:03
- 41625David Robbsan 2012年12月17日 8:43
- 191750GlennPatton 2012年12月14日 13:11
- 11435Rinku Baruah 2012年12月18日 8:38
- 101956triple_vee 2012年12月6日 0:01
- 41852Selva.123 2012年12月10日 11:50
- 11486LightAlkmst 2012年12月16日 17:30
httpWebRequest.GetResponse(): The underlying connection was closed: The connection was closed unexpectedly.mmmt 2012年12月14日 3:49
- 41796CountryStyle 2012年12月11日 2:54
- 31636martin_mine 2012年12月9日 21:43
- 41842hon123456 2012年12月12日 9:47
- 41788papacharlie1989 2012年12月11日 1:29
Socket problem: TcpClient.GetStream with ReceiveTimeout throws Exception and connected state become falseCinnio 2010年8月24日 16:05
- 51647SusantaKumar 2012年12月6日 5:43
C#.NET console application -sending mail.. when i am trying to send mail, i am getting error "Failed Sending mail" , can some one help me, below is my code... ThanksSusantaKumar 2012年12月4日 6:13
- 61549NathanT85 2012年12月6日 15:15