Network Class Library (System.Net)

Duyurular

• Bağlantı

  This Forum Has Been Retired

  15 Aralık 2012 Cumartesi 01:39

  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.

  
  
• Bağlantı

  Forum Tips and Valid Topics

  28 Temmuz 2008 Pazartesi 21:05

  
  

  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:
  

  
  

  1.    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
     
     
  2.   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.
     
     
  3.   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.
     
     
  4.   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”
     
     
  5.   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. 
     
     
  6.   Once 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.
     
     
  7.   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.
     
     
  8.   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!

  
  
  Related Forums
  
  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.