Bei der Gruppe, für die Sie eine Mitteilung verfassen, handelt es sich um eine Usenet-Gruppe. Wenn Sie in dieser Gruppe Nachrichten posten, ist Ihre E-Mail-Adresse für jeden im Internet sichtbar
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?
> 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 : http://asp.net.do/faq/ > Foros de ASP.NET en Español : http://asp.net.do/foros/ > ====================================== > "S. Justin Gengo" <justin@[no_spam_please]aboutfortunate.com> wrote in > message news:OSxhzys4FHA.3276@TK2MSFTNGP10.phx.gbl... >>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
> 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.
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:
>> 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.
> 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:
I didn't realize the config section shouldn't have the xmlns in it. Well, I shouldn't say "shouldn't have". But I wonder why they put that in by default when it eliminates intellisense? That would have been easy to fix I for a release version I would think...
>>> 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.
>> 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:
>>> 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.
>> 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:
> I wonder why they put that in by default when it eliminates intellisense?
It's not a default.
I have a feeling your web.config was created with Beta 1 or Beta 2, and you didn't recollect that it wasn't created from scratch.
With the release version, when you create a web.config in an application which doesn't have one, what VS includes is this :
<?xml version="1.0"?> <!-- Note: As an alternative to hand editing this file you can use the web admin tool to configure settings for your application. Use the Website->Asp.Net Configuration option in Visual Studio. A full list of settings and comments can be found in machine.config.comments usually located in \Windows\Microsoft.Net\Framework\v2.x\Config --> <configuration>
> I didn't realize the config section shouldn't have the xmlns in it. Well, I shouldn't > say "shouldn't have". But I wonder why they put that in by default when it eliminates > intellisense? That would have been easy to fix I for a release version I would think...
> -- > Sincerely,
> S. Justin Gengo, MCP > Web Developer / Programmer
>>>> 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.
>>> 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:
No, this was a brand new website I built for testing. I used the New ASP.NET Website selection to create it and this is how the web.config was by default.
> re: >> I wonder why they put that in by default when it eliminates intellisense?
> It's not a default.
> I have a feeling your web.config was created with Beta 1 or Beta 2, > and you didn't recollect that it wasn't created from scratch.
> With the release version, when you create a web.config in an > application which doesn't have one, what VS includes is this :
> <?xml version="1.0"?> > <!-- > Note: As an alternative to hand editing this file you can use the > web admin tool to configure settings for your application. Use > the Website->Asp.Net Configuration option in Visual Studio. > A full list of settings and comments can be found in > machine.config.comments usually located in > \Windows\Microsoft.Net\Framework\v2.x\Config > --> > <configuration>
>> I didn't realize the config section shouldn't have the xmlns in it. Well, >> I shouldn't say "shouldn't have". But I wonder why they put that in by >> default when it eliminates intellisense? That would have been easy to fix >> I for a release version I would think...
>> -- >> Sincerely,
>> S. Justin Gengo, MCP >> Web Developer / Programmer
>>>>> 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.
>>>> 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:
> I didn't realize the config section shouldn't have the xmlns in it. > Well, I shouldn't say "shouldn't have". But I wonder why they put > that in by default when it eliminates intellisense? That would have > been easy to fix I for a release version I would think...
I just re-tested creating 3 new websites in each of 3 different languages ( VB.NET, C# and J# ) and in none of the web.configs was the xmlns=" attribute included.
We may have different versions of the release version.
;-)
These are the things which sometimes make me scratch my head.
What is the version number shown when you open "Help" and then click on "About Microsoft Visual Studio" ?
> No, this was a brand new website I built for testing. I used the New ASP.NET Website > selection to create it and this is how the web.config was by default.
> -- > Sincerely,
> S. Justin Gengo, MCP > Web Developer / Programmer
> "Out of chaos comes order." > Nietzsche > "Juan T. Llibre" <nomailrepl...@nowhere.com> wrote in message > news:%23j0Kxpt4FHA.1476@TK2MSFTNGP10.phx.gbl... >> re: >>> I wonder why they put that in by default when it eliminates intellisense?
>> It's not a default.
>> I have a feeling your web.config was created with Beta 1 or Beta 2, >> and you didn't recollect that it wasn't created from scratch.
>> With the release version, when you create a web.config in an >> application which doesn't have one, what VS includes is this :
>> <?xml version="1.0"?> >> <!-- >> Note: As an alternative to hand editing this file you can use the >> web admin tool to configure settings for your application. Use >> the Website->Asp.Net Configuration option in Visual Studio. >> A full list of settings and comments can be found in >> machine.config.comments usually located in >> \Windows\Microsoft.Net\Framework\v2.x\Config >> --> >> <configuration>
>>> I didn't realize the config section shouldn't have the xmlns in it. Well, I shouldn't >>> say "shouldn't have". But I wonder why they put that in by default when it eliminates >>> intellisense? That would have been easy to fix I for a release version I would >>> think...
>>> -- >>> Sincerely,
>>> S. Justin Gengo, MCP >>> Web Developer / Programmer
>>> "Out of chaos comes order." >>> Nietzsche >>> "Juan T. Llibre" <nomailrepl...@nowhere.com> wrote in message >>> news:%23Sgqiat4FHA.2616@TK2MSFTNGP12.phx.gbl... >>>> Great pointer, Joerg!
>>>> I just confirmed the behavior, by replacing the <configuration> >>>> tag in my *good* web.config with :
>>>>>> 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.
>>>>> 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:
> I just re-tested creating 3 new websites in each of 3 different languages > ( VB.NET, C# and J# ) and in none of the web.configs was the > xmlns=" attribute included.
> We may have different versions of the release version.
> ;-)
> These are the things which sometimes make me scratch my head.
> What is the version number shown when you open "Help" > and then click on "About Microsoft Visual Studio" ?
>> No, this was a brand new website I built for testing. I used the New >> ASP.NET Website selection to create it and this is how the web.config was >> by default.
>> -- >> Sincerely,
>> S. Justin Gengo, MCP >> Web Developer / Programmer
>> "Out of chaos comes order." >> Nietzsche >> "Juan T. Llibre" <nomailrepl...@nowhere.com> wrote in message >> news:%23j0Kxpt4FHA.1476@TK2MSFTNGP10.phx.gbl... >>> re: >>>> I wonder why they put that in by default when it eliminates >>>> intellisense?
>>> It's not a default.
>>> I have a feeling your web.config was created with Beta 1 or Beta 2, >>> and you didn't recollect that it wasn't created from scratch.
>>> With the release version, when you create a web.config in an >>> application which doesn't have one, what VS includes is this :
>>> <?xml version="1.0"?> >>> <!-- >>> Note: As an alternative to hand editing this file you can use the >>> web admin tool to configure settings for your application. Use >>> the Website->Asp.Net Configuration option in Visual Studio. >>> A full list of settings and comments can be found in >>> machine.config.comments usually located in >>> \Windows\Microsoft.Net\Framework\v2.x\Config >>> --> >>> <configuration>
>>>> I didn't realize the config section shouldn't have the xmlns in it. >>>> Well, I shouldn't say "shouldn't have". But I wonder why they put that >>>> in by default when it eliminates intellisense? That would have been >>>> easy to fix I for a release version I would think...
>>>> -- >>>> Sincerely,
>>>> S. Justin Gengo, MCP >>>> Web Developer / Programmer
>>>> "Out of chaos comes order." >>>> Nietzsche >>>> "Juan T. Llibre" <nomailrepl...@nowhere.com> wrote in message >>>> news:%23Sgqiat4FHA.2616@TK2MSFTNGP12.phx.gbl... >>>>> Great pointer, Joerg!
>>>>> I just confirmed the behavior, by replacing the <configuration> >>>>> tag in my *good* web.config with :
>>>>>>> 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.
>>>>>> 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:
>> I didn't realize the config section shouldn't have the xmlns in it. >> Well, I shouldn't say "shouldn't have". But I wonder why they put >> that in by default when it eliminates intellisense? That would have >> been easy to fix I for a release version I would think...
Nope I haven't mixed things up. (I thought so too at first.) But I have identified and can recreate the problem every time now.
Here are the steps:
Create a new website with a web.config file. It's created without the xmlns attribute.
I'm using source safe, and while I don't think it matters my tests have been with the project added to source control. So, I first check out the web.config file and then from the menu I run Website - ASP.NET Configuration.
Just opening the website configuration page adds the xmlns attribute to the configuration file.
> Nope I haven't mixed things up. (I thought so too at first.) But I have > identified and can recreate the problem every time now.
> Here are the steps:
> Create a new website with a web.config file. It's created without the > xmlns attribute.
> I'm using source safe, and while I don't think it matters my tests have > been with the project added to source control. So, I first check out the > web.config file and then from the menu I run Website - ASP.NET > Configuration.
> Just opening the website configuration page adds the xmlns attribute to > the configuration file.
> -- > Sincerely,
> S. Justin Gengo, MCP > Web Developer / Programmer
>> Nope I haven't mixed things up. (I thought so too at first.) But I have >> identified and can recreate the problem every time now.
>> Here are the steps:
>> Create a new website with a web.config file. It's created without the >> xmlns attribute.
>> I'm using source safe, and while I don't think it matters my tests have >> been with the project added to source control. So, I first check out the >> web.config file and then from the menu I run Website - ASP.NET >> Configuration.
>> Just opening the website configuration page adds the xmlns attribute to >> the configuration file.
>> -- >> Sincerely,
>> S. Justin Gengo, MCP >> Web Developer / Programmer
Juan, you always give great answers to everything. Joerg, thanks for helping to point me in the correct direction to recreate this problem. And Greg, thanks for identifying that the problem occurrs regardless of source safe. That saved me a few minutes of project creation.
> "Out of chaos comes order." > Nietzsche > "Greg Burns" <bluebu...@newsgroups.nospam> wrote in message > news:OHERgav4FHA.3292@tk2msftngp13.phx.gbl... >>I don't have sourcesafe on my home machine, and I am seeing the same >>thing. The ASP.NET Configuration tool seems to be doing it.
>>> Nope I haven't mixed things up. (I thought so too at first.) But I have >>> identified and can recreate the problem every time now.
>>> Here are the steps:
>>> Create a new website with a web.config file. It's created without the >>> xmlns attribute.
>>> I'm using source safe, and while I don't think it matters my tests have >>> been with the project added to source control. So, I first check out the >>> web.config file and then from the menu I run Website - ASP.NET >>> Configuration.
>>> Just opening the website configuration page adds the xmlns attribute to >>> the configuration file.
>>> -- >>> Sincerely,
>>> S. Justin Gengo, MCP >>> Web Developer / Programmer
> Juan, you always give great answers to everything. Joerg, thanks for helping to point me > in the correct direction to recreate this problem. And Greg, thanks for identifying that > the problem occurrs regardless of source safe. That saved me a few minutes of project > creation.
> -- > Sincerely,
> S. Justin Gengo, MCP > Web Developer / Programmer
> "Out of chaos comes order." > Nietzsche > "S. Justin Gengo" <justin@[no_spam_please]aboutfortunate.com> wrote in message > news:%23m2Vgiv4FHA.156@TK2MSFTNGP15.phx.gbl... >> After searching the bug reports I saw a bug that was related to this but no report for >> this particular bug.
>> I've reported it now.
>> -- >> Sincerely,
>> S. Justin Gengo, MCP >> Web Developer / Programmer
>> "Out of chaos comes order." >> Nietzsche >> "Greg Burns" <bluebu...@newsgroups.nospam> wrote in message >> news:OHERgav4FHA.3292@tk2msftngp13.phx.gbl... >>>I don't have sourcesafe on my home machine, and I am seeing the same thing. The ASP.NET >>>Configuration tool seems to be doing it.
>>>> Nope I haven't mixed things up. (I thought so too at first.) But I have identified >>>> and can recreate the problem every time now.
>>>> Here are the steps:
>>>> Create a new website with a web.config file. It's created without the xmlns >>>> attribute.
>>>> I'm using source safe, and while I don't think it matters my tests have been with the >>>> project added to source control. So, I first check out the web.config file and then >>>> from the menu I run Website - ASP.NET Configuration.
>>>> Just opening the website configuration page adds the xmlns attribute to the >>>> configuration file.
>>>> -- >>>> Sincerely,
>>>> S. Justin Gengo, MCP >>>> Web Developer / Programmer
>>>> "Out of chaos comes order." >>>> Nietzsche >>>> "Joerg Jooss" <news-re...@joergjooss.de> wrote in message >>>> news:xn0e9fc371d17ol006@msnews.microsoft.com... >>>>> Juan T. Llibre wrote:
>>>>>> re: >>>>>> > In Beta 2 (and maybe earlier versions) the xmlns attribute was >>>>>> > being used. It has been removed in VS 2005 RTM.
>>>>>> Yes, that's my recollection, too, but Justin seems to be saying >>>>>> that this attribute is being added with the release version.
> Nope I haven't mixed things up. (I thought so too at first.) But I > have identified and can recreate the problem every time now.
> Here are the steps:
> Create a new website with a web.config file. It's created without the > xmlns attribute.
> I'm using source safe, and while I don't think it matters my tests > have been with the project added to source control. So, I first check > out the web.config file and then from the menu I run Website - > ASP.NET Configuration.
> Just opening the website configuration page adds the xmlns attribute > to the configuration file.
OK, that's exactly the one piece of software I haven't used so far :-/
It was filed by Josh Flanagan on Oct. 29 ( just a few days before... )
I voted for it and validated it. I suggest those interested in resolution do the same.
We won't get resolution soon, but maybe by SP1 ... ;-)
In the meantime, don't use the website configuration tool but, if you do, make sure you change the <configuration xmlns=" line back to <configuration>.
> "Out of chaos comes order." > Nietzsche > "Greg Burns" <bluebu...@newsgroups.nospam> wrote in message > news:OHERgav4FHA.3292@tk2msftngp13.phx.gbl... >>I don't have sourcesafe on my home machine, and I am seeing the same thing. The ASP.NET >>Configuration tool seems to be doing it.
>>> Nope I haven't mixed things up. (I thought so too at first.) But I have identified and >>> can recreate the problem every time now.
>>> Here are the steps:
>>> Create a new website with a web.config file. It's created without the xmlns attribute.
>>> I'm using source safe, and while I don't think it matters my tests have been with the >>> project added to source control. So, I first check out the web.config file and then >>> from the menu I run Website - ASP.NET Configuration.
>>> Just opening the website configuration page adds the xmlns attribute to the >>> configuration file.
>>> -- >>> Sincerely,
>>> S. Justin Gengo, MCP >>> Web Developer / Programmer
> It was filed by Josh Flanagan on Oct. 29 > ( just a few days before... )
> I voted for it and validated it. > I suggest those interested in resolution do the same.
> We won't get resolution soon, but maybe by SP1 ... ;-)
> In the meantime, don't use the website configuration tool but, if you do, > make sure you change the <configuration xmlns=" line back to > <configuration>.
> Juan T. Llibre, ASP.NET MVP > ASP.NET FAQ : http://asp.net.do/faq/ > Foros de ASP.NET en Español : http://asp.net.do/foros/ > ====================================== > "S. Justin Gengo" <justin@[no_spam_please]aboutfortunate.com> wrote in > message news:%23m2Vgiv4FHA.156@TK2MSFTNGP15.phx.gbl... >> After searching the bug reports I saw a bug that was related to this but >> no report for this particular bug.
>> I've reported it now.
>> -- >> Sincerely,
>> S. Justin Gengo, MCP >> Web Developer / Programmer
>> "Out of chaos comes order." >> Nietzsche >> "Greg Burns" <bluebu...@newsgroups.nospam> wrote in message >> news:OHERgav4FHA.3292@tk2msftngp13.phx.gbl... >>>I don't have sourcesafe on my home machine, and I am seeing the same >>>thing. The ASP.NET Configuration tool seems to be doing it.
>>>> Nope I haven't mixed things up. (I thought so too at first.) But I have >>>> identified and can recreate the problem every time now.
>>>> Here are the steps:
>>>> Create a new website with a web.config file. It's created without the >>>> xmlns attribute.
>>>> I'm using source safe, and while I don't think it matters my tests have >>>> been with the project added to source control. So, I first check out >>>> the web.config file and then from the menu I run Website - ASP.NET >>>> Configuration.
>>>> Just opening the website configuration page adds the xmlns attribute to >>>> the configuration file.
>>>> -- >>>> Sincerely,
>>>> S. Justin Gengo, MCP >>>> Web Developer / Programmer
>>>> "Out of chaos comes order." >>>> Nietzsche >>>> "Joerg Jooss" <news-re...@joergjooss.de> wrote in message >>>> news:xn0e9fc371d17ol006@msnews.microsoft.com... >>>>> Juan T. Llibre wrote:
>>>>>> re: >>>>>> > In Beta 2 (and maybe earlier versions) the xmlns attribute was >>>>>> > being used. It has been removed in VS 2005 RTM.
>>>>>> Yes, that's my recollection, too, but Justin seems to be saying >>>>>> that this attribute is being added with the release version.
Yep, that's a definite bugger. It tripped me up in a code camp presentation last weekend when I wanted to ease the amount of typing I did in the .config file.
Intellisense is a god send for those of us who type with 4 fingers...
I have had similar issues with this to and I also have removed the xmlns tag, but when you use the web admin tool it get placed back in. Maybe I need to reinstall, I never installed the beta.
>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: > <!-- > <
|
