WebClient: Web.config Intellisense ASP.NET 2.0

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.com

"Out of chaos comes order."
NietzscheJuan,

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.com

"Out of chaos comes order."
Nietzsche
"Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
news:u7ByQ9s4FHA.1188@.TK2MSFTNGP12.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 : http://asp.net.do/faq/
> Foros de ASP.NET en Espaol : 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
>>
>> www.aboutfortunate.com
>>
>> "Out of chaos comes order."
>> Nietzsche
>>
>>
S. Justin Gengo wrote:

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

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="http://schemas.microsoft.com/.NetConfiguration/v2.0"
should be

<configuration
Cheers,
--
http://www.joergjooss.de
mailto:news-reply@.joergjooss.de
Great pointer, Joerg!

I just confirmed the behavior, by replacing the <configuration>
tag in my *good* web.config with :

<configuration xmlns="http://schemas.microsoft.com/.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 : http://asp.net.do/faq/
Foros de ASP.NET en Espaol : http://asp.net.do/foros/
======================================
"Joerg Jooss" <news-reply@.joergjooss.de> wrote in message
news:xn0e9f6ry15ryp7003@.msnews.microsoft.com...
> S. Justin Gengo wrote:
>> 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.
> 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="http://schemas.microsoft.com/.NetConfiguration/v2.0">
> should be
> <configuration>
> Cheers,
> --
> http://www.joergjooss.de
> mailto:news-reply@.joergjooss.de
Thanks guys!

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

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"Juan T. Llibre" <nomailreplies@.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 :
> <configuration
> xmlns="http://schemas.microsoft.com/.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 : http://asp.net.do/faq/
> Foros de ASP.NET en Espaol : http://asp.net.do/foros/
> ======================================
> "Joerg Jooss" <news-reply@.joergjooss.de> wrote in message
> news:xn0e9f6ry15ryp7003@.msnews.microsoft.com...
>> S. Justin Gengo wrote:
>>
>>> 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.
>>
>> 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="http://schemas.microsoft.com/.NetConfiguration/v2.0">
>>
>> should be
>>
>> <configuration>
>>
>> Cheers,
>> --
>> http://www.joergjooss.de
>> mailto:news-reply@.joergjooss.de
For now I'm just going to move this info down to a commented line:

<configuration
<!-- xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"--
That way I can put it back in if I discover it's needed for any reason.

Thanks again!

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"Juan T. Llibre" <nomailreplies@.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 :
> <configuration
> xmlns="http://schemas.microsoft.com/.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 : http://asp.net.do/faq/
> Foros de ASP.NET en Espaol : http://asp.net.do/foros/
> ======================================
> "Joerg Jooss" <news-reply@.joergjooss.de> wrote in message
> news:xn0e9f6ry15ryp7003@.msnews.microsoft.com...
>> S. Justin Gengo wrote:
>>
>>> 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.
>>
>> 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="http://schemas.microsoft.com/.NetConfiguration/v2.0">
>>
>> should be
>>
>> <configuration>
>>
>> Cheers,
>> --
>> http://www.joergjooss.de
>> mailto:news-reply@.joergjooss.de
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"?>

<configuration
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
is not included when a new web.config is created in the release version of VS.

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

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"Juan T. Llibre" <nomailreplies@.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"?>
> 
> <configuration>
> <configuration
> xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
> is not included when a new web.config is created in the release version of
> VS.
>
>
> Juan T. Llibre, ASP.NET MVP
> ASP.NET FAQ : http://asp.net.do/faq/
> Foros de ASP.NET en Espaol : http://asp.net.do/foros/
> ======================================
> "S. Justin Gengo" <justin@.[no_spam_please]aboutfortunate.com> wrote in
> message news:Oi8Nggt4FHA.3348@.TK2MSFTNGP10.phx.gbl...
>> Thanks guys!
>>
>> 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
>>
>> www.aboutfortunate.com
>>
>> "Out of chaos comes order."
>> Nietzsche
>> "Juan T. Llibre" <nomailreplies@.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 :
>>>
>>> <configuration
>>> xmlns="http://schemas.microsoft.com/.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 : http://asp.net.do/faq/
>>> Foros de ASP.NET en Espaol : http://asp.net.do/foros/
>>> ======================================
>>> "Joerg Jooss" <news-reply@.joergjooss.de> wrote in message
>>> news:xn0e9f6ry15ryp7003@.msnews.microsoft.com...
>>>> S. Justin Gengo wrote:
>>>>
>>>>> 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.
>>>>
>>>> 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="http://schemas.microsoft.com/.NetConfiguration/v2.0">
>>>>
>>>> should be
>>>>
>>>> <configuration>
>>>>
>>>> Cheers,
>>>> --
>>>> http://www.joergjooss.de
>>>> mailto:news-reply@.joergjooss.de
Juan T. Llibre wrote:

> Great pointer, Joerg!
> I just confirmed the behavior, by replacing the <configuration>
> tag in my good web.config with :
> <configuration
> xmlns="http://schemas.microsoft.com/.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 ?

Well, it fixes the now broken content created with Beta 2 ;-)

In Beta 2 (and maybe earlier versions) the xmlns attribute was being
used. It has been removed in VS 2005 RTM.

Cheers,
--
http://www.joergjooss.de
mailto:news-reply@.joergjooss.de
Weird!

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" ?

Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
Foros de ASP.NET en Espaol : http://asp.net.do/foros/
======================================
"S. Justin Gengo" <justin@.[no_spam_please]aboutfortunate.com> wrote in message
news:On$75Au4FHA.1276@.TK2MSFTNGP09.phx.gbl...
> Juan,
> 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
> www.aboutfortunate.com
> "Out of chaos comes order."
> Nietzsche
> "Juan T. Llibre" <nomailreplies@.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"?>
>> 
>> <configuration>
>>
>> <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
>> is not included when a new web.config is created in the release version of VS.
>>
>>
>>
>>
>> Juan T. Llibre, ASP.NET MVP
>> ASP.NET FAQ : http://asp.net.do/faq/
>> Foros de ASP.NET en Espaol : http://asp.net.do/foros/
>> ======================================
>> "S. Justin Gengo" <justin@.[no_spam_please]aboutfortunate.com> wrote in message
>> news:Oi8Nggt4FHA.3348@.TK2MSFTNGP10.phx.gbl...
>>> Thanks guys!
>>>
>>> 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
>>>
>>> www.aboutfortunate.com
>>>
>>> "Out of chaos comes order."
>>> Nietzsche
>>> "Juan T. Llibre" <nomailreplies@.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 :
>>>>
>>>> <configuration xmlns="http://schemas.microsoft.com/.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 : http://asp.net.do/faq/
>>>> Foros de ASP.NET en Espaol : http://asp.net.do/foros/
>>>> ======================================
>>>> "Joerg Jooss" <news-reply@.joergjooss.de> wrote in message
>>>> news:xn0e9f6ry15ryp7003@.msnews.microsoft.com...
>>>>> S. Justin Gengo wrote:
>>>>>
>>>>>> 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.
>>>>>
>>>>> 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="http://schemas.microsoft.com/.NetConfiguration/v2.0">
>>>>>
>>>>> should be
>>>>>
>>>>> <configuration>
>>>>>
>>>>> Cheers,
>>>>> --
>>>>> http://www.joergjooss.de
>>>>> mailto:news-reply@.joergjooss.de
>>
>>
S. Justin Gengo wrote:

> Thanks guys!
> 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...

Probably, yes. It's not mentioned in
http://download.microsoft.com/downl...5-462b-b9ad-e6d
3cd6ad7c1/Breaking%20Changes%20Beta2%20to%20RTM.doc

Cheers,
--
http://www.joergjooss.de
mailto:news-reply@.joergjooss.de
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.

I don't understand why.

Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
Foros de ASP.NET en Espaol : http://asp.net.do/foros/
======================================
"Joerg Jooss" <news-reply@.joergjooss.de> wrote in message
news:xn0e9fb601buat6004@.msnews.microsoft.com...
> Juan T. Llibre wrote:
>> Great pointer, Joerg!
>>
>> I just confirmed the behavior, by replacing the <configuration>
>> tag in my good web.config with :
>>
>> <configuration
>> xmlns="http://schemas.microsoft.com/.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 ?
> Well, it fixes the now broken content created with Beta 2 ;-)
> In Beta 2 (and maybe earlier versions) the xmlns attribute was being
> used. It has been removed in VS 2005 RTM.
> Cheers,
> --
> http://www.joergjooss.de
> mailto:news-reply@.joergjooss.de
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.
> I don't understand why.

I'm sure he has mixed things up.

Cheers,
--
http://www.joergjooss.de
mailto:news-reply@.joergjooss.de
Juan,

I've got:

Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)

Microsoft .NET Framework
Version 2.0.50727

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
news:ezx0ytu4FHA.3876@.TK2MSFTNGP09.phx.gbl...
> Weird!
> 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" ?
>
> Juan T. Llibre, ASP.NET MVP
> ASP.NET FAQ : http://asp.net.do/faq/
> Foros de ASP.NET en Espaol : http://asp.net.do/foros/
> ======================================
> "S. Justin Gengo" <justin@.[no_spam_please]aboutfortunate.com> wrote in
> message news:On$75Au4FHA.1276@.TK2MSFTNGP09.phx.gbl...
>> Juan,
>>
>> 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
>>
>> www.aboutfortunate.com
>>
>> "Out of chaos comes order."
>> Nietzsche
>> "Juan T. Llibre" <nomailreplies@.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"?>
>>> 
>>> <configuration>
>>>
>>> <configuration
>>> xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
>>> is not included when a new web.config is created in the release version
>>> of VS.
>>>
>>>
>>>
>>>
>>> Juan T. Llibre, ASP.NET MVP
>>> ASP.NET FAQ : http://asp.net.do/faq/
>>> Foros de ASP.NET en Espaol : http://asp.net.do/foros/
>>> ======================================
>>> "S. Justin Gengo" <justin@.[no_spam_please]aboutfortunate.com> wrote in
>>> message news:Oi8Nggt4FHA.3348@.TK2MSFTNGP10.phx.gbl...
>>>> Thanks guys!
>>>>
>>>> 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
>>>>
>>>> www.aboutfortunate.com
>>>>
>>>> "Out of chaos comes order."
>>>> Nietzsche
>>>> "Juan T. Llibre" <nomailreplies@.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 :
>>>>>
>>>>> <configuration
>>>>> xmlns="http://schemas.microsoft.com/.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 : http://asp.net.do/faq/
>>>>> Foros de ASP.NET en Espaol : http://asp.net.do/foros/
>>>>> ======================================
>>>>> "Joerg Jooss" <news-reply@.joergjooss.de> wrote in message
>>>>> news:xn0e9f6ry15ryp7003@.msnews.microsoft.com...
>>>>>> S. Justin Gengo wrote:
>>>>>>
>>>>>>> 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.
>>>>>>
>>>>>> 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="http://schemas.microsoft.com/.NetConfiguration/v2.0">
>>>>>>
>>>>>> should be
>>>>>>
>>>>>> <configuration>
>>>>>>
>>>>>> Cheers,
>>>>>> --
>>>>>> http://www.joergjooss.de
>>>>>> mailto:news-reply@.joergjooss.de
>>>
>>>
>>
>>
Joerg,

Thanks, the document will come in handy!

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"Joerg Jooss" <news-reply@.joergjooss.de> wrote in message
news:xn0e9fbbm1bxals005@.msnews.microsoft.com...
> S. Justin Gengo wrote:
>> Thanks guys!
>>
>> 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...
> Probably, yes. It's not mentioned in
> http://download.microsoft.com/downl...5-462b-b9ad-e6d
> 3cd6ad7c1/Breaking%20Changes%20Beta2%20to%20RTM.doc
> Cheers,
> --
> http://www.joergjooss.de
> mailto:news-reply@.joergjooss.de
Guys,

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

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"Joerg Jooss" <news-reply@.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.
>>
>> I don't understand why.
> I'm sure he has mixed things up.
> Cheers,
> --
> http://www.joergjooss.de
> mailto:news-reply@.joergjooss.de
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.

Greg

"S. Justin Gengo" <justin@.[no_spam_please]aboutfortunate.com> wrote in
message news:eDmESEv4FHA.1416@.TK2MSFTNGP09.phx.gbl...
> Guys,
> 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
> www.aboutfortunate.com
> "Out of chaos comes order."
> Nietzsche
> "Joerg Jooss" <news-reply@.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.
>>>
>>> I don't understand why.
>>
>> I'm sure he has mixed things up.
>>
>> Cheers,
>> --
>> http://www.joergjooss.de
>> mailto:news-reply@.joergjooss.de
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

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"Greg Burns" <bluebunny@.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.
> Greg
> "S. Justin Gengo" <justin@.[no_spam_please]aboutfortunate.com> wrote in
> message news:eDmESEv4FHA.1416@.TK2MSFTNGP09.phx.gbl...
>> Guys,
>>
>> 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
>>
>> www.aboutfortunate.com
>>
>> "Out of chaos comes order."
>> Nietzsche
>> "Joerg Jooss" <news-reply@.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.
>>>>
>>>> I don't understand why.
>>>
>>> I'm sure he has mixed things up.
>>>
>>> Cheers,
>>> --
>>> http://www.joergjooss.de
>>> mailto:news-reply@.joergjooss.de
>>
>>
Thanks everyone for helping out here.

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

www.aboutfortunate.com

"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
> www.aboutfortunate.com
> "Out of chaos comes order."
> Nietzsche
> "Greg Burns" <bluebunny@.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.
>>
>> Greg
>>
>> "S. Justin Gengo" <justin@.[no_spam_please]aboutfortunate.com> wrote in
>> message news:eDmESEv4FHA.1416@.TK2MSFTNGP09.phx.gbl...
>>> Guys,
>>>
>>> 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
>>>
>>> www.aboutfortunate.com
>>>
>>> "Out of chaos comes order."
>>> Nietzsche
>>> "Joerg Jooss" <news-reply@.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.
>>>>>
>>>>> I don't understand why.
>>>>
>>>> I'm sure he has mixed things up.
>>>>
>>>> Cheers,
>>>> --
>>>> http://www.joergjooss.de
>>>> mailto:news-reply@.joergjooss.de
>>>
>>>
>>
>>
I just confirmed that, if you use the
Website Configuration Tool it *does* add the :

<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
tag, substituting the original <configuration> tag.

That doesn't happen when the "Add file" menu choice is taken.

So, it's a bug! Filing it was a good move...

Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
Foros de ASP.NET en Espaol : http://asp.net.do/foros/
======================================

"S. Justin Gengo" <justin@.[no_spam_please]aboutfortunate.com> wrote in message
news:%23xObfHw4FHA.3192@.TK2MSFTNGP12.phx.gbl...
> Thanks everyone for helping out here.
> 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
> www.aboutfortunate.com
> "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
>>
>> www.aboutfortunate.com
>>
>> "Out of chaos comes order."
>> Nietzsche
>> "Greg Burns" <bluebunny@.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.
>>>
>>> Greg
>>>
>>> "S. Justin Gengo" <justin@.[no_spam_please]aboutfortunate.com> wrote in message
>>> news:eDmESEv4FHA.1416@.TK2MSFTNGP09.phx.gbl...
>>>> Guys,
>>>>
>>>> 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
>>>>
>>>> www.aboutfortunate.com
>>>>
>>>> "Out of chaos comes order."
>>>> Nietzsche
>>>> "Joerg Jooss" <news-reply@.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.
>>>>>>
>>>>>> I don't understand why.
>>>>>
>>>>> I'm sure he has mixed things up.
>>>>>
>>>>> Cheers,
>>>>> --
>>>>> http://www.joergjooss.de
>>>>> mailto:news-reply@.joergjooss.de
>>>>
>>>>
>>>
>>>
>>
>>
S. Justin Gengo wrote:

> Guys,
> 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 :-/

Thanks for pointing this out!
--
http://www.joergjooss.de
mailto:news-reply@.joergjooss.de
I just found a previous bug filed for the same issue :

http://lab.msdn.microsoft.com/produ...2c-e7a2168bcc5e

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

I vote for it too.

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
news:uY7XAZx4FHA.4064@.TK2MSFTNGP10.phx.gbl...
>I just found a previous bug filed for the same issue :
> http://lab.msdn.microsoft.com/produ...2c-e7a2168bcc5e
> 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 Espaol : 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
>>
>> www.aboutfortunate.com
>>
>> "Out of chaos comes order."
>> Nietzsche
>> "Greg Burns" <bluebunny@.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.
>>>
>>> Greg
>>>
>>> "S. Justin Gengo" <justin@.[no_spam_please]aboutfortunate.com> wrote in
>>> message news:eDmESEv4FHA.1416@.TK2MSFTNGP09.phx.gbl...
>>>> Guys,
>>>>
>>>> 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
>>>>
>>>> www.aboutfortunate.com
>>>>
>>>> "Out of chaos comes order."
>>>> Nietzsche
>>>> "Joerg Jooss" <news-reply@.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.
>>>>>>
>>>>>> I don't understand why.
>>>>>
>>>>> I'm sure he has mixed things up.
>>>>>
>>>>> Cheers,
>>>>> --
>>>>> http://www.joergjooss.de
>>>>> mailto:news-reply@.joergjooss.de
>>>>
>>>>
>>>
>>>
>>
>>
On Sun, 6 Nov 2005 15:53:45 -0400, "Juan T. Llibre"
<nomailreplies@.nowhere.com> wrote:

>I just confirmed that, if you use the
>Website Configuration Tool it *does* add the :
><configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
>tag, substituting the original <configuration> tag.

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

Argh.

--
Scott
http://www.OdeToCode.com/blogs/scott/
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.

"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
> www.aboutfortunate.com
> "Out of chaos comes order."
> Nietzsche
re:
> Maybe I need to reinstall

You don't need to do that.
This is a bona-fide bug for the web site administration tool.

The bug was validated by the VS.NET team at :
http://lab.msdn.microsoft.com/produ...2c-e7a2168bcc5e

The WSAT should *not* be inserting that string.
That string *was* correct for Beta 1, but was eliminated for Beta 2.

Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
Foros de ASP.NET en Espaol : http://asp.net.do/foros/
======================================
"Angelo Cook" <angelo_cook@.hotmail.com> wrote in message
news:Ok%23NmQ64FHA.400@.TK2MSFTNGP09.phx.gbl...
>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.
>
> "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
>>
>> www.aboutfortunate.com
>>
>> "Out of chaos comes order."
>> Nietzsche
>>
And there still is no fix on the horizon. as long as you do use the WSAT
(web site admin tool) you can use the work-around.

"Juan T. Llibre" <nomailreplies@.nowhere.com> wrote in message
news:Oe6woU64FHA.1464@.tk2msftngp13.phx.gbl...
> re:
>> Maybe I need to reinstall
> You don't need to do that.
> This is a bona-fide bug for the web site administration tool.
> The bug was validated by the VS.NET team at :
> http://lab.msdn.microsoft.com/produ...2c-e7a2168bcc5e
> The WSAT should *not* be inserting that string.
> That string *was* correct for Beta 1, but was eliminated for Beta 2.
>
>
> Juan T. Llibre, ASP.NET MVP
> ASP.NET FAQ : http://asp.net.do/faq/
> Foros de ASP.NET en Espaol : http://asp.net.do/foros/
> ======================================
> "Angelo Cook" <angelo_cook@.hotmail.com> wrote in message
> news:Ok%23NmQ64FHA.400@.TK2MSFTNGP09.phx.gbl...
>>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.
>>
>>
>> "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
>>>
>>> www.aboutfortunate.com
>>>
>>> "Out of chaos comes order."
>>> Nietzsche
>>>
>>
>>

Wednesday, March 28, 2012

Web.config Intellisense ASP.NET 2.0

0 comments:

Post a Comment

WebClient

Blog Archive

About Me