Compiler Error Message: BC30456: 'InitializeCulture'

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.

Advertisements

"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" <> wrote in message
news:...
> 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.
>

Advertisements

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" <> wrote in message
> news:...
> > 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.
> >
>
>
>

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

"Mauricio Pires" <> wrote in message
news:...
> 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" <> wrote in
>> message
>> news:...
>> > 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.
>> >
>>
>>
>>

Well, 30 Seonds is all it took me on google to find this post which both fixed my problem and gave me a laugh, so thank you both kindly sirs.

Jeff Dillon said:

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" <> wrote in message
news:...
> 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.
>

I used this form of compiling you described. I unchecked the "Allow this precomplied site to be updatable" checkbox in the MSBuild Options pane of the project Properties and I repaired the display errors but I have got problems with the reports I'm using. I don't know if you can help me with this trouble I've got, and thank you for the post because it helped me.

Share This Page

Welcome to The Coding Forums!

Welcome to the Coding Forums, the place to chat about anything related to programming and coding languages.

Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free. You'll be able to ask questions about coding or chat with the community and help others.
Sign up now!