Web.config Intellisense ASP.NET 2.0

本文介绍了Web.config Intellisense ASP.NET 2.0的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我安装了几天的Visual Studio.NET 2005 Professional版本 前。我已经使用Beta几个星期了，一个直接的问题是 ，我似乎在web.config文件中没有完整的intellisense。 我得到intellisense，但它只显示三个非常基本的选择： <！ - <！[CDATA [ < ;? 是否有其他人遇到此问题？ 任何人都知道如何在网络上获得完整的智能感知.config文件为 做广告？ 谢谢， S. Justin Gengo，MCP 网站开发人员/程序员 www.aboutfortunate 出于混乱而来的订单。 Nietzsche

I installed the release of Visual Studio.NET 2005 Professional a few days ago. I''ve been using the Beta for a few weeks and one immediate problem is that I don''t seem to have full intellisense in the web.config file. I get intellisense, but it''s only displaying three very basic choices: <!-- <![CDATA[ <? Is anyone else having this problem? Anyone know how to get full intellisense in the web.config file as advertised? Thanks, S. Justin Gengo, MCP Web Developer / Programmer www.aboutfortunate "Out of chaos comes order." Nietzsche

推荐答案

Juan， 是的，这就是我在测试中获得的。现在，我只收到我在上一篇文章中提到的三个 选项。 这有点烦人。如果我找到了解决方案，我会发布它，以防任何人 其他有同样的问题。 - 此致， S. Justin Gengo，MCP 网站开发人员/程序员 www.aboutfortunate 混乱无序。 Nietzsche " Juan T. Llibre" <无*********** @ nowhere>在留言中写道 news：u7 ************** @ TK2MSFTNGP12.phx.gbl ... Juan, Yes, that''s what I was getting in the beta. Now, I only get the three choices I mentioned in my previous post. It''s slightly annoying. If I figure out the fix I''ll post it in case anyone else has the same problem. -- Sincerely, S. Justin Gengo, MCP Web Developer / Programmer www.aboutfortunate "Out of chaos comes order." Nietzsche "Juan T. Llibre" <no***********@nowhere> wrote in message news:u7**************@TK2MSFTNGP12.phx.gbl... 那是奇怪的，Justin。 所有我需要做的就是获得Intellisense for web.config在< configuration>< / configuration>内的任何地方写一个小于字符。标签和Intellisense正好弹出。 请参阅附带的小图。 Juan T. Llibre，ASP.NET MVP ASP.NET常见问题解答： asp.do/faq/ Foros de ASP.NET en Espa？ol： asp.do/foros / ====================================== S。 Justin Gengo <贾斯汀@ [no_spam_please] aboutfortunate>在消息新闻中写道：OS ************** @ TK2MSFTNGP10.phx.gbl ... That''s odd, Justin. All I need to do to get Intellisense for web.config is write a "less-than" character anywhere inside the <configuration></configuration> tags and Intellisense pops right up. See the attached small graphic. Juan T. Llibre, ASP.NET MVP ASP.NET FAQ : asp.do/faq/ Foros de ASP.NET en Espa?ol : asp.do/foros/ ====================================== "S. Justin Gengo" <justin@[no_spam_please]aboutfortunate> wrote in message news:OS**************@TK2MSFTNGP10.phx.gbl... 我安装了Visual Studio.NET的发布版2005专业几天之前。我已经使用Beta几个星期，一个直接的问题 我似乎在web.config文件中没有完整的intellisense。 我得到了intellisense，但它只显示了三个非常基本的选择：<！ - <！[CDATA [<？ 其他人是否有这个问题？ 任何人都知道如何在web.config文件中获得完整的intellisense广告？ 谢谢， S. Justin Gengo，MCP Web开发人员/程序员 www.aboutfortunate 出于混乱，订单。尼采 I installed the release of Visual Studio.NET 2005 Professional a few days ago. I''ve been using the Beta for a few weeks and one immediate problem is that I don''t seem to have full intellisense in the web.config file. I get intellisense, but it''s only displaying three very basic choices: <!-- <![CDATA[ <? Is anyone else having this problem? Anyone know how to get full intellisense in the web.config file as advertised? Thanks, S. Justin Gengo, MCP Web Developer / Programmer www.aboutfortunate "Out of chaos comes order." Nietzsche

S. Justin Gengo写道： S. Justin Gengo wrote: Juan， 是的，这就是我在测试版中获得的。现在，我只收到我在上一篇文章中提到的三个选项。 这有点烦人。如果我弄清楚我会发布它以防万一其他人有同样的问题。 Juan, Yes, that''s what I was getting in the beta. Now, I only get the three choices I mentioned in my previous post. It''s slightly annoying. If I figure out the fix I''ll post it in case anyone else has the same problem.

你可以创建一个新的web.config并将你的 Beta 2文件的内容复制到新文件（使用像WinMerge这样的合并工具），或者你 尝试从配置节点中删除xmlns属性作为一个 的快速修复： < configuration xmlns =" schemas.microsoft/ .NetConfiguration / v2.0"> 应该是 < configuration> 干杯， - http：//www.joergjooss .de mailto：ne ******** @ joergjooss.de

You can either create a new web.config and copy the contents of your Beta 2 file over to new file (use a merge tool like WinMerge), or you try to remove the xmlns attribute from the configuration node as a quick fix: <configuration xmlns="schemas.microsoft/.NetConfiguration/v2.0"> should be <configuration> Cheers, -- www.joergjooss.de mailto:ne********@joergjooss.de

棒极了，Joerg！ 我刚刚确认了这种行为，将我的* good * web.config中的< configuration> 标记替换为： < configuration xmlns =" http：//schemas.mi crosoft/.NetConfiguration/v2.0"> 立刻，Justin descibed开始相同的症状， 即我得到intellisense，但它只显示选择： <！ - <！[CDATA [ <？ 只需将其更改回< configuration> "修复"它。 它实际上并不是一个修复的东西。但更换错误配置，对吗？ Juan T. Llibre，ASP.NET MVP ASP.NET FAQ： asp.do/faq/ Foros de ASP.NET en Espa？ol： asp.do/foros / ===================================== = " Joerg Jooss" <是ne ******** @ joergjooss.de>在消息中写道 news：xn **************** @ msnews.microsoft ... Great pointer, Joerg! I just confirmed the behavior, by replacing the <configuration> tag in my *good* web.config with : <configuration xmlns="schemas.microsoft/.NetConfiguration/v2.0"> And immediately, the same symptoms Justin descibed begin, i.e. I get intellisense, but it only displays the choices: <!-- <![CDATA[ <? Just changing it back to <configuration> "fixes" it. It''s not actually a "fix" but the replacement of a misconfiguration, right ? Juan T. Llibre, ASP.NET MVP ASP.NET FAQ : asp.do/faq/ Foros de ASP.NET en Espa?ol : asp.do/foros/ ====================================== "Joerg Jooss" <ne********@joergjooss.de> wrote in message news:xn****************@msnews.microsoft... S. Justin Gengo写道： S. Justin Gengo wrote: Juan， 是的，这就是我在测试版中获得的。现在，我只收到我在上一篇文章中提到的三个选项。 这有点烦人。如果我弄清楚我会发布它以防万一其他人有同样的问题。 Juan, Yes, that''s what I was getting in the beta. Now, I only get the three choices I mentioned in my previous post. It''s slightly annoying. If I figure out the fix I''ll post it in case anyone else has the same problem.

你可以创建一个新的web.config并复制内容您的Beta 2文件到新文件（使用像WinMerge这样的合并工具），或者您尝试从配置节点中删除xmlns属性作为快速修复： < configuration xmlns =" http：//schemas.microsoft/.NetConfiguration/v2.0"> 应该是 <配置> 干杯， www.joergjooss.de mailto：ne ******** @ joergjooss.de

You can either create a new web.config and copy the contents of your Beta 2 file over to new file (use a merge tool like WinMerge), or you try to remove the xmlns attribute from the configuration node as a quick fix: <configuration xmlns="schemas.microsoft/.NetConfiguration/v2.0"> should be <configuration> Cheers, -- www.joergjooss.de mailto:ne********@joergjooss.de