问题描述
我们有Windows 2003 Server上运行SQL Server 2005和.NET 3.5 [单独]。
我们有IIS 6
运行一个基本的ASP.NET应用程序有什么东西，我需要做的应用程序结束[IIS，框架，ASP.NET]使其与IPv6兼容？
We have Windows 2003 Servers running SQL Server 2005 and .NET 3.5 [separately].
We have a basic ASP.NET app running on IIS 6.
What, if anything, do I need to do on the application end [IIS,Framework,ASP.NET] to make it IPv6 compatible?
编辑：我们使用System.DirectoryServices中，System.DirectoryServices.DirectoryEntry和DirectorySearcher从（）对广告进行身份验证的用户。将这些电话有变？
We do use System.DirectoryServices, System.DirectoryServices.DirectoryEntry and DirectorySearcher() to authenticate users against AD. Would those calls have to change?
推荐答案
做的是搜索你的code向的，看看你是如何传递信息围绕这些领域：
The first thing to do would be search your code for any references to System.Net.IPAddress, and see how you're passing information around in those areas:
- 在你执行任何手动验证一个期望IP地址是IPv4的格式？
- 你有什么UI组件，在应用程序本身，或者您有任何配置工具/页，这是硬codeD到xxx.xxx.xxx.xxx格式？
- 在多少空间，你分配给存储IP地址的东西，如在数据库中记录表？ 15个字符是充足的IPv4地址，而IPv6地址可能相当大。
- 请您在您的用户界面任何地方的显示的IP地址？如果你这样做，你分配足够的屏幕房地产展示一个完整的IPv6地址？
- Are you performing any "manual" validation that expects IP addresses to be in the IPv4 format?
- Do you have any UI components, in the application itself or any configuration tools/pages you have for it, that are hard-coded to an xxx.xxx.xxx.xxx format?
- How much space do you allocate to store IP addresses in things such as logging tables in databases? 15 characters is ample for an IPv4 address, but an IPv6 address can be considerably bigger.
- Do you display IP addresses anywhere in your UI? If you do, do you allocate enough screen real-estate to show a full IPv6 address?
有其他问题回答，但他们更多的基础设施有关，serverfault将是他们一个更好的地方。
There are other questions to answer but they're more infrastructure related and serverfault would be a better place for them.
这篇关于制作一个asp.net应用与IPv6兼容的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！