Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Feb 11, 2010 10:01 PM by dannil
Jan 22, 2006 06:46 PM|LINK
Sometimes, this error appears... A few pages seem to work after I access them straight from the server first?
Ive read up on this error and the function 'InitializeCulture' appears to be some kind of regional settings (for currency and time settings etc). At first the error happened whilst trying to access the site from an external machine, now I am getting it when
I test it on the server also...
Does anyone know anything about this error!?
Jan 24, 2006 05:57 PM|LINK
InitializeCulture is a virtual member of the Page class. It is used as a coinvenient point to set the Page.Culture/UICulture members that will be called extremely early in the page lifecycle for you to define the Thread settings.
Can you provide a repro for this issue?
Mar 09, 2006 10:47 PM|LINK
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.
TradeBug.com - Ottawa's Largest Online Classifieds, Auctions, Rock Bottom Deals, and Flea Markets.
Sep 05, 2007 09:06 PM|LINK
Sep 15, 2007 12:57 AM|LINK
That fixed my problem, too!
Nov 29, 2007 12:47 PM|LINK
I 've read your solution, but honestly don't know where to uncheck the "allo this precomplied site to be updatable" within the Visual Studio Web Developer 2005.
Can you help me out here, because i have the same error as mentioned into this thread.
Feb 27, 2008 08:27 PM|LINK
Thank you thank you thank you thank you!!!!!
Jun 19, 2008 03:02 PM|LINK
Jul 25, 2008 02:01 PM|LINK
I think I may have discovered the real culprit, and therefore a real solution, rather than a workaround.
In my case, I had needed to create multiple similar pages. I copied my "Contact" page and pasted it into the project 5 times. I then renamed the pages. What I forgot to do was change the class from Contacts to a new class name. For example, my Donors.aspx
page class was renamed to Donors. I also needed to change the class name where it is inherited on the .aspx page.
Once I did that, it still didn't work. I realized that I needed to build the site first. I built the site, then published it, and I kept the "allow this precompiled site to be updatable" checkbox checked.
Worked like a charm. Hopefully, this will work for you as well.
Jul 25, 2008 07:19 PM|LINK
I'll try your solution as soon as i get the next error.
Thanks for sharing your solution