VS2005 : how do you set DEFAULT encoding of cs files to UTF-8 ?

[Michel de Becdelièvre]

I'm developing a ASP.Net 2.0 Web site, all my pages are in UTF-8, BUT
when I add a new aspx page, the aspx file is created in UTF-8, but the
aspx.cs file is created as Western...1252. It is annoying to have to go to
the Advanced save Options dialogs for EACH .cs file (and accented characters
coming from compiled .cs saved as 1252 do not show correctly).

Any way to change the default .cs file creation option ?

NB : I know that "international" characters can end up in resx files, but
I'd like to avoid it in a number of places (UTF-8 math or symbols characters
DO NOT need to be translated for instance).

thanks in advance.

[Joerg Jooss]

Thus wrote Michel,

I'm developing a ASP.Net 2.0 Web site, all my pages are in UTF-8,
BUT when I add a new aspx page, the aspx file is created in UTF-8, but
the aspx.cs file is created as Western...1252. It is annoying to have
to go to the Advanced save Options dialogs for EACH .cs file (and
accented characters coming from compiled .cs saved as 1252 do not show
correctly).

Any way to change the default .cs file creation option ?

Weird -- I'm just working on a blog entry on that subject. What I've found
is that the only case in which VS2005 does *not* use UTF-8 as default encoding
for source files is when using pages with inline code.

Hm...
--
Joerg Jooss
ne********@joergjooss.de

[Michel de Becdelièvre]

"Joerg Jooss" <ne********@joergjooss.de> a écrit dans le message de news:
94**************************@msnews.microsoft.com...

Thus wrote Michel,

I'm developing a ASP.Net 2.0 Web site, all my pages are in UTF-8,
BUT when I add a new aspx page, the aspx file is created in UTF-8, but
the aspx.cs file is created as Western...1252. It is annoying to have
to go to the Advanced save Options dialogs for EACH .cs file (and
accented characters coming from compiled .cs saved as 1252 do not show
correctly).

Any way to change the default .cs file creation option ?

Weird -- I'm just working on a blog entry on that subject. What I've found
is that the only case in which VS2005 does *not* use UTF-8 as default
encoding for source files is when using pages with inline code.

Hm...

Not my case, I dislike inline code.

[Joerg Jooss]

Thus wrote Michel,

"Joerg Jooss" <ne********@joergjooss.de> a écrit dans le message de
news: 94**************************@msnews.microsoft.com...

[...]

Weird -- I'm just working on a blog entry on that subject. What I've
found is that the only case in which VS2005 does *not* use UTF-8 as
default encoding for source files is when using pages with inline
code.

Hm...

Not my case, I dislike inline code.

Mine neither, it was pure chance that I found that.

Cheers,
--
Joerg Jooss
ne********@joergjooss.de