473,327 Members | 1,952 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,327 software developers and data experts.

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."
Nietzsche
Nov 19 '05 #1
26 1828
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.com

"Out of chaos comes order."
Nietzsche
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:u7**************@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 Español : http://asp.net.do/foros/
======================================
"S. Justin Gengo" <justin@[no_spam_please]aboutfortunate.com> wrote in
message news:OS**************@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


Nov 19 '05 #2
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:ne********@joergjooss.de
Nov 19 '05 #3
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 Español : http://asp.net.do/foros/
======================================
"Joerg Jooss" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de

Nov 19 '05 #4
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" <no***********@nowhere.com> wrote in message
news:%2****************@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 Español : http://asp.net.do/foros/
======================================
"Joerg Jooss" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de


Nov 19 '05 #5
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" <no***********@nowhere.com> wrote in message
news:%2****************@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 Español : http://asp.net.do/foros/
======================================
"Joerg Jooss" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de


Nov 19 '05 #6
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 VS.


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:Oi**************@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" <no***********@nowhere.com> wrote in message
news:%2****************@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 Español : http://asp.net.do/foros/
======================================
"Joerg Jooss" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de

Nov 19 '05 #7
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" <no***********@nowhere.com> wrote in message
news:%2****************@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>

<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 Español : http://asp.net.do/foros/
======================================
"S. Justin Gengo" <justin@[no_spam_please]aboutfortunate.com> wrote in
message news:Oi**************@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" <no***********@nowhere.com> wrote in message
news:%2****************@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 Español : http://asp.net.do/foros/
======================================
"Joerg Jooss" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de


Nov 19 '05 #8
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:ne********@joergjooss.de
Nov 19 '05 #9
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 Español : http://asp.net.do/foros/
======================================
"S. Justin Gengo" <justin@[no_spam_please]aboutfortunate.com> wrote in message
news:On**************@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" <no***********@nowhere.com> wrote in message
news:%2****************@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>

<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 Español : http://asp.net.do/foros/
======================================
"S. Justin Gengo" <justin@[no_spam_please]aboutfortunate.com> wrote in message
news:Oi**************@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" <no***********@nowhere.com> wrote in message
news:%2****************@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 Español : http://asp.net.do/foros/
======================================
"Joerg Jooss" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de



Nov 19 '05 #10
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/downlo...-462b-b9ad-e6d
3cd6ad7c1/Breaking%20Changes%20Beta2%20to%20RTM.doc

Cheers,
--
http://www.joergjooss.de
mailto:ne********@joergjooss.de
Nov 19 '05 #11
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 Español : http://asp.net.do/foros/
======================================
"Joerg Jooss" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de

Nov 19 '05 #12
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:ne********@joergjooss.de
Nov 19 '05 #13
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" <no***********@nowhere.com> wrote in message
news:ez**************@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 Español : http://asp.net.do/foros/
======================================
"S. Justin Gengo" <justin@[no_spam_please]aboutfortunate.com> wrote in
message news:On**************@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" <no***********@nowhere.com> wrote in message
news:%2****************@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>

<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 Español : http://asp.net.do/foros/
======================================
"S. Justin Gengo" <justin@[no_spam_please]aboutfortunate.com> wrote in
message news:Oi**************@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" <no***********@nowhere.com> wrote in message
news:%2****************@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 Español : http://asp.net.do/foros/
> ======================================
> "Joerg Jooss" <ne********@joergjooss.de> wrote in message
> news:xn****************@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:ne********@joergjooss.de



Nov 19 '05 #14
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" <ne********@joergjooss.de> wrote in message
news:xn****************@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/downlo...-462b-b9ad-e6d
3cd6ad7c1/Breaking%20Changes%20Beta2%20to%20RTM.doc

Cheers,
--
http://www.joergjooss.de
mailto:ne********@joergjooss.de

Nov 19 '05 #15
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" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de

Nov 19 '05 #16
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:eD**************@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" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de


Nov 19 '05 #17
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" <bl*******@newsgroups.nospam> wrote in message
news:OH**************@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:eD**************@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" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de



Nov 19 '05 #18
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:%2***************@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" <bl*******@newsgroups.nospam> wrote in message
news:OH**************@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:eD**************@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" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de



Nov 19 '05 #19
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 Español : http://asp.net.do/foros/
======================================

"S. Justin Gengo" <justin@[no_spam_please]aboutfortunate.com> wrote in message
news:%2****************@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:%2***************@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" <bl*******@newsgroups.nospam> wrote in message
news:OH**************@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:eD**************@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" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de




Nov 19 '05 #20
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:ne********@joergjooss.de
Nov 19 '05 #21
I just found a previous bug filed for the same issue :

http://lab.msdn.microsoft.com/produc...c-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 Español : http://asp.net.do/foros/
======================================
"S. Justin Gengo" <justin@[no_spam_please]aboutfortunate.com> wrote in message
news:%2***************@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" <bl*******@newsgroups.nospam> wrote in message
news:OH**************@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:eD**************@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" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de



Nov 19 '05 #22
Hmmmm, I missed that one when I was looking for it as a reported bug. Should
have seen that.

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" <no***********@nowhere.com> wrote in message
news:uY**************@TK2MSFTNGP10.phx.gbl...
I just found a previous bug filed for the same issue :

http://lab.msdn.microsoft.com/produc...c-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 Español : http://asp.net.do/foros/
======================================
"S. Justin Gengo" <justin@[no_spam_please]aboutfortunate.com> wrote in
message news:%2***************@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" <bl*******@newsgroups.nospam> wrote in message
news:OH**************@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:eD**************@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" <ne********@joergjooss.de> wrote in message
news:xn****************@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:ne********@joergjooss.de



Nov 19 '05 #23
On Sun, 6 Nov 2005 15:53:45 -0400, "Juan T. Llibre"
<no***********@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/
Nov 19 '05 #24
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:OS**************@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

Nov 19 '05 #25
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/produc...c-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 Español : http://asp.net.do/foros/
======================================
"Angelo Cook" <an*********@hotmail.com> wrote in message
news:Ok***************@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:OS**************@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


Nov 19 '05 #26
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" <no***********@nowhere.com> wrote in message
news:Oe**************@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/produc...c-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 Español : http://asp.net.do/foros/
======================================
"Angelo Cook" <an*********@hotmail.com> wrote in message
news:Ok***************@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:OS**************@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



Nov 19 '05 #27

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

1
by: Adam Clauss | last post by:
I have a few variables that I want declared as global. To accomplish this, I made the files globals.h and globals.cpp. In globals.h I have the declarations for the structs, and one variable...
3
by: Andy | last post by:
Hello All: When you develop a C# app that is deployed as an .exe, you can use a .exe.config file to set some parameters to avoid changing code. I would like to do the same thing using a .dll,...
1
by: ABC | last post by:
Web.Config Editing have no intellisense feature on VC# web site project under VS IDE 2005. How can I turn it on?
2
by: louise raisbeck | last post by:
Hi, I am using c#. i have my server code within script tags on my aspx page i am not using code behind. Do you not get intellisense when working like this? it would speed up my work considerably...
4
by: ABC | last post by:
Web.Config Editing have no intellisense feature on VC# web site project under VS IDE 2005. How can I turn it on?
3
by: Sami Marzouki | last post by:
Hi, What I'm trying to do is: - To write a Web.config with custom sections. (Done) - To write a xsd schema for this custom sections.(Done) - Tell the Web.config to take the two schemas. When...
1
by: SeeSharp | last post by:
..NET 2.0 has a great feature where you can remove certain elements from your web.config and put them in an external file. For example the membership element has the configSource attribute and you...
5
by: sunev | last post by:
We are working on a large project and using a number of the new asp.net 2.0 features a number of third party controls. One such feature is the global registration of controls in the web.config,...
1
by: Nathan Sokalski | last post by:
On Microsoft's page about IE8 and Defining Document Compatibility at: http://msdn.microsoft.com/en-us/library/cc288325(VS.85).aspx They give the following code to add to Web.config: <?xml...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you
0
by: Faith0G | last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.