ago. I've been using the Beta for a few w
s and one immediate problem isthat 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...
>
>
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:
>
> 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...
>
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...
>
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>
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
is not included when a new web.config is created in the release version of V
S.
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 messa
ge
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 w
ould 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...
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:
> 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>
> <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...
>
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:
> <!--
> <
0 comments:
Post a Comment