Globalization is ambiguous Error in SP2 - Error Level Severe - General Support

Welcome Guest! To enable all features please Login or Register.

Notification

Error

BV Commerce Forum » BV Commerce Support » General Support » Globalization is ambiguous Error in SP2 - Error Level Severe

Globalization is ambiguous Error in SP2 - Error Level Severe

Options

Previous Topic Next Topic

Outdoor Ed		#1 Posted : Wednesday, April 18, 2007 7:18:21 AM(UTC)
Rank: Member Joined: 3/4/2006(UTC) Posts: 121		For those considering the upgrade to SP2 I would hold off. After installing it over a working SP1 I am now receiving a number of errors in Admin pages related to globalization code. I've been working through Help Tickets with Everett. I thought it might be because I am running Bvc 5 in a subfolder of my site so it is inheriting my Web.config (same configuration as in SP1). I have a globalization setting in my root web.config. I removed that setting but it has not corrected the errors. At the moment this leaves Bvc 5 SP2 in an unusable state. The offending code lines are related to currency and date: If Date.TryParse(args.Value, Threading.Thread.CurrentThread.CurrentUICulture, Globalization.DateTimeStyles.None, Nothing) Then If Decimal.TryParse(ToPriceTextBox.Text, Globalization.NumberStyles.Currency, Threading.Thread.CurrentThread.CurrentUICulture, val) Then These files are affected. I tried 'touching' every page available from the second level of the Admin Control panel. I didn't go any deeper than that so there may be other pages that call the globalization code Source File: \BVAdmin\Controls\ProductFilter.ascx.vb Line: 122 Source File: \BVAdmin\Controls\ProductFilter.ascx.vb Line: 122 Source File: \BVAdmin\Controls\DatePicker.ascx.vb Line: 75 Source File: \BVAdmin\People\PriceGroups.aspx.vb Line: 43 Source File: \BVAdmin\Orders\NewOrder.aspx.vb Line: 233 Source File: \BVAdmin\Configuration\Shipping.aspx.vb Line: 66 Source File: \BVAdmin\Configuration\GiftCertificates.aspx.vb Line: 22 Source File: \BVModules\PaymentMethods\Google Checkout\Edit.ascx.vb Line: 99 Hoping for a fix soon. Given that there were database changes made while applying the SP2 patch it may not be possible to roll back to SP1. Rick


User Profile View All Posts by User View Thanks

jetheredge		#2 Posted : Wednesday, April 18, 2007 8:32:57 AM(UTC)
Rank: Member Joined: 3/1/2006(UTC) Posts: 1,142		We have seen this before and it is usually related to installing ASP.net AJAX on your site. It inserts a reference in your web project to System.Web.Extensions that adds a Globalization namespace to the System.Web namespace. This is why you are seeing this conflict. If you have a reference in the default namespaces section of your web.config to System.Web.Extensions then you should try and remove it.
		Justin Etheredge Senior Software Engineer BVSoftware


User Profile View All Posts by User View Thanks

jetheredge		#3 Posted : Wednesday, April 18, 2007 9:58:40 AM(UTC)
Rank: Member Joined: 3/1/2006(UTC) Posts: 1,142		It appears that if the System.Web.Extensions dll is included as an assembly at the machine level, then this error occurs because the System.Web namespace is already a default. In order to remedy this you can change your local web.config to look like below... basically the two "remove" statements need to be added so that the System.Web.Extensions and System.Web.Extensions.Design dlls don't get loaded. <compilation debug="false" strict="true" explicit="true"> <assemblies> <remove assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> <remove assembly="System.Web.Extensions.Design, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> </assemblies> </compilation>
		Justin Etheredge Senior Software Engineer BVSoftware


User Profile View All Posts by User View Thanks

Andy Miller		#4 Posted : Friday, July 27, 2007 3:41:31 PM(UTC)
Rank: Member Joined: 11/5/2003(UTC) Posts: 2,136 Was thanked: 1 time(s) in 1 post(s)		I changed every occurance of "Globalization" to "System.Globalization" in the BVC5 front-end (there were about 100 and I got most of them by search/replace). After that I was able to run the site with both ASP.NET Ajax and Anthem.NET.
		Andy Miller Structured Solutions Shipper 3 - High Velocity Shipment Processing


User Profile View All Posts by User View Thanks

Outdoor Ed		#5 Posted : Tuesday, July 31, 2007 9:06:01 AM(UTC)
Rank: Member Joined: 3/4/2006(UTC) Posts: 121		Andy, I had posted about this earlier. Your approach sounds good up to a point. The question I have is whether BVSoftware is going to actually fix this in across the entire product. I hate to do a globall search and replace, change their code only to have that be overwritten in a hotfix or a future Service Pack and then suddenly have the site stop working. BVSoftware, any responses? Rick


User Profile View All Posts by User View Thanks

Outdoor Ed		#6 Posted : Saturday, August 11, 2007 6:07:04 PM(UTC)
Rank: Member Joined: 3/4/2006(UTC) Posts: 121		I did a search using Dreamweaver's great Find All feature as Andy suggested and got 130 instances of the word "Globalization". Some lines of code were already written as System.Globalization while others were not. Here are the various code references I found which did not use System.Globalization. Globalization.NumberStyles.Currency Globalization.NumberStyles.Number Globalization.NumberStyles.Integer Globalization.DateTimeStyles Globalization.CultureInfo.CultureUiCulture.NumberFormat.PercentSymbol Globalization.CultureInfo.CurrentCulture Here are the files where I found some type of Globalization code. WebServices4.aspx.vb BVAdmin/Catalog/GiftCertificateEdit.aspx.vb BVAdmin/Catalog/KitPart_Edit.aspx.vb BVAdmin/Catalog/ProductCombinationsEdit.aspx.vb BVAdmin/Catalog/Products_Edit.aspx.vb BVAdmin/Configuration/Countries_Edit.aspx.vb BVAdmin/Configuration/GiftCertificates.aspx.vb BVAdmin/Configuration/Shipping.aspx.vb BVAdmin/Controls/DatePicker.ascx.vb BVAdmin/Controls/DropDownDate.ascx.vb BVAdmin/Controls/PercentAmountSelection.ascx.vb BVAdmin/Controls/ProductFieldCopier.ascx.vb BVAdmin/Controls/ProductFilter.ascx.vb BVAdmin/Marketing/Sales.aspx.vb BVAdmin/Orders/EditOrder.aspx.vb BVAdmin/Orders/NewOrder.aspx.vb BVAdmin/Orders/ReceivePayments.aspx.vb People/Affiliates_Edit.aspx.vb BVAdmin/People/PriceGroups.aspx.vb BVModules/ContentBlocks/Flash Image Rotator/adminview.ascx.vb BVModules/ContentBlocks/Html Rotator/adminview.ascx.vb BVModules/ContentBlocks/Html Rotator/view.ascx.vb BVModules/ContentBlocks/Image Rotator/adminview.ascx.vb BVModules/ContentBlocks/Image Rotator/view.ascx.vb BVModules/ContentBlocks/Product Rotator/adminview.ascx.vb BVModules/ContentBlocks/Product Rotator/view.ascx.vb BVModules/Offers/Buy One Get One/Edit.ascx.vb BVModules/Offers/Free Shipping/Edit.ascx.vb BVModules/Offers/Order Total/Edit.ascx.vb BVModules/Offers/Product(s)/Edit.ascx.vb BVModules/Offers/Shipping/Edit.ascx.vb BVModules/OrderTasks/Apply Minimum Order Amount/Edit.ascx.vb BVModules/PaymentMethods/Google Checkout/Edit.ascx.vb BVModules/ProductModifers/Drop Down List/Edit.ascx.vb BVModules/ProductModifers/Image Radio Button List/Edit.ascx.vb BVModules/ProductModifers/Radio Button List/Edit.ascx.vb BVModules/Shipping/By Item Count/Edit.ascx.vb BVModules/Shipping/By Order Total/Edit.ascx.vb BVModules/Shipping/By Weight/Edit.ascx.vb BVModules/Shipping/FedEx/Edit.ascx.vb BVModules/Shipping/Per Item/Edit.ascx.vb BVModules/Shipping/Per Order/Edit.ascx.vb BVModules/Shipping/UPS/Edit.ascx.vb BVModules/Shipping/US Postal Service/Edit.ascx.vb So it's in part due to inconsistent coding practices. If we can get a commitment from BV staff that this will be fixed in the future and that the code will be cleaned up to System.Globalization then I'd be happy to update the current BV5 SP2 code I have knowing that any future Hot Fix or Service Pack will use System.Globalization. Until then I'm going to hold off because it would be a major problem to have the site stop working again if the base code isn't consistently fixed by BV. Rick


User Profile View All Posts by User View Thanks

jetheredge		#7 Posted : Thursday, August 30, 2007 2:00:34 PM(UTC)
Rank: Member Joined: 3/1/2006(UTC) Posts: 1,142		We have already fixed this issue and it will be in SP3.
		Justin Etheredge Senior Software Engineer BVSoftware


User Profile View All Posts by User View Thanks

Forum Jump

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.