Compiler Error Message: BC30456: 'InitializeCulture'

[Mauricio Pires]

All my pages work just fine on development, but as soon as I publish
(deploy) to a W2K Server with .Net Framework 2.0 , I always get
Compiler Error Message: BC30456: 'InitializeCulture' is not a member of
'ASP.default_aspx'.
This happens for every page and after I created a MasterPage.

Please help. I have seen multiple questions from people on this same
issue, but with no answers.

[Jeff Dillon]

30 seconds on Google:

"I found a solution. During the publishing stage on framework 2.0 uncheck
the "allow this precompiled site to be updatable". Once I unchecked this it
published correctly and functioned correctly on IIS. With it checked I
would always receive 'InitializeCulture' is not a member of ...

Another alternative to these is to copy the files directly from your
development environment as the aspx pages define there CodeBehind pages in
there header tags. Either method will work. Option 1 is faster.

I hope this helps.

Anthony"

"Mauricio Pires" <Ma***********@discussions.microsoft.com> wrote in message
news:69**********************************@microsof t.com...

All my pages work just fine on development, but as soon as I publish
(deploy) to a W2K Server with .Net Framework 2.0 , I always get
Compiler Error Message: BC30456: 'InitializeCulture' is not a member of
'ASP.default_aspx'.
This happens for every page and after I created a MasterPage.

Please help. I have seen multiple questions from people on this same
issue, but with no answers.

[Mauricio Pires]

Excuse me, but in 30 seconds you found out the wrong response.
The problem was ambiguos inheritance in my pages.
Thanks.


"Jeff Dillon" wrote:

30 seconds on Google:

"I found a solution. During the publishing stage on framework 2.0 uncheck
the "allow this precompiled site to be updatable". Once I unchecked this it
published correctly and functioned correctly on IIS. With it checked I
would always receive 'InitializeCulture' is not a member of ...

Another alternative to these is to copy the files directly from your
development environment as the aspx pages define there CodeBehind pages in
there header tags. Either method will work. Option 1 is faster.

I hope this helps.

Anthony"

"Mauricio Pires" <Ma***********@discussions.microsoft.com> wrote in message
news:69**********************************@microsof t.com...

All my pages work just fine on development, but as soon as I publish
(deploy) to a W2K Server with .Net Framework 2.0 , I always get
Compiler Error Message: BC30456: 'InitializeCulture' is not a member of
'ASP.default_aspx'.
This happens for every page and after I created a MasterPage.

Please help. I have seen multiple questions from people on this same
issue, but with no answers.

[Jeff Dillon]

And in less than 30 seconds you were rude

At least I tried, and you're welcome. I've added you to my "don't help in
the future" list

"Mauricio Pires" <Ma***********@discussions.microsoft.com> wrote in message
news:08**********************************@microsof t.com...

Excuse me, but in 30 seconds you found out the wrong response.
The problem was ambiguos inheritance in my pages.
Thanks.


"Jeff Dillon" wrote:

30 seconds on Google:

"I found a solution. During the publishing stage on framework 2.0
uncheck
the "allow this precompiled site to be updatable". Once I unchecked this
it
published correctly and functioned correctly on IIS. With it checked I
would always receive 'InitializeCulture' is not a member of ...

Another alternative to these is to copy the files directly from your
development environment as the aspx pages define there CodeBehind pages
in
there header tags. Either method will work. Option 1 is faster.

I hope this helps.

Anthony"

"Mauricio Pires" <Ma***********@discussions.microsoft.com> wrote in
message
news:69**********************************@microsof t.com...

> All my pages work just fine on development, but as soon as I publish
> (deploy) to a W2K Server with .Net Framework 2.0 , I always get
> Compiler Error Message: BC30456: 'InitializeCulture' is not a member of
> 'ASP.default_aspx'.
> This happens for every page and after I created a MasterPage.
>
> Please help. I have seen multiple questions from people on this same
> issue, but with no answers.
>