Last post Feb 11, 2006 02:34 PM by bot2601
Feb 03, 2006 05:24 PM|bot2601|LINK
I ran into an issue migrating a commerce server 2002 site from asp.net 1.1 to 2.0. Everything is working well (after some work) except for the messageManager component that is embedded in the order pipeling. In the web.config file, he has the following entrie
<cultures default="en-US" baseName="Commerce.ProjectResources" assembly="Commerce">
<culture id="en-US" />
<culture id="fr-fr" />
<culture id="ja-JP" />
<resource id="pur_badsku" />
<resource id="pur_badplacedprice" />
<resource id="pur_discount_changed" />
<resource id="pur_discount_removed" />
<resource id="pur_noitems" />
<resource id="pur_badshipping" />
<resource id="pur_badhandling" />
<resource id="pur_badtax" />
<resource id="pur_badcc" />
<resource id="pur_badpayment" />
<resource id="pur_badverify" />
<resource id="pur_out_of_stock" />
<resource id="pur_AddItem" />
<resource id="pur_VariantPrice" />
The resources file itself was upgraded with the site. When I try to run this, I get a parser error stating it cant load the assembly 'commerce' which is somewhat expected since commerce is now a website and not a project. I cant leave the assembly attribute
out, as I would expect to do, because it insists it is a required attribute. I tried to add the resource as a new default resource to one of my components that 'does' have a dll, and the satellite assembly is created, but the error I then get is:
Parser Error Message: There was an error loading resources for the messageManager section. Please check that the baseName 'Commerce.Resources' is valid and a valid satellite assembly exists for the default culture
Line 94: the executing application or the name of a satellite assembly. Line 95: --> Line 96: <cultures default="en-US" baseName="Commerce.Resources" assembly="Commerce">
Thanks for any help!
Feb 06, 2006 07:25 PM|ScottGu|LINK
I just sent mail to the Commerce Server team pointing them at this thread. We'll try and get someone there to help out.
Feb 07, 2006 08:40 AM|bot2601|LINK
Feb 07, 2006 10:44 AM|rdonovan|LINK
This is unfortunately actually to be expected. The short answer is that Commerce Server 2002 cannot run natively in .NET 2.0. Ditto for running CS2002 on 64-bit or SQL2005. It can, however, run on a system with .NET 2.0 side-by-side .NET 1.1.
The longer answer is that there are many changes in .NET 2.0, 64-bit Windows, and SQL2005 that necessitated relatively substantial changes in Commerce Server. The team put several months of effort into making these changes for Commerce Server 2006. At this
point, I do not see a high liklihood of us going back and back-porting these to CS2002 given the product's age and the imminent launch of CS2006.
If you would like to use the latest/greatest Microsoft platform, I recommend checking out the CS2006 Beta. It has been available since December and can be downloaded from
Thanks & best regards,
Feb 08, 2006 04:16 PM|bot2601|LINK
Well, so far I have everything working as expected except for the MessageManager which unfortunantly is an important piece. I tried removing the resource file totally from within the web.config and add all of the strings manually to the MessageManager in
the on application start method of the site, but it doesn't appear to work, though this is probably me doing something wrong, since it doesn't seem to work for me in 1.1 either.
Anyhow, if/when I get over this specific issue, all should be working, but it looks like a show stopper at this point. I have a case open with Microsoft Support, but they seem to be avoiding me like the plague.
Feb 09, 2006 01:23 PM|rdonovan|LINK
I might try downloading the Starter Site from
http://www.microsoft.com/commerceserver/downloads/solutionsites2002.mspx as that should have a working message
manager configured correctly that you can use as a guide.
If you get this working on .NET 2.0, do realize that it won't be supported by PSS if you have issues and they will make you repro any problems on 1.1.
You might also want to make sure your app. is actually running in 1.1 and not 2.0, though I am sure you have already done that. That has been a cause of consternation for a few folks.
Feb 09, 2006 03:46 PM|bot2601|LINK
I have this working now. The site/app everything is running in 2.0. The solution ended up being that I had to get away from using a resource file to load the messageManager. I had this part worked out, I am pumping him in the application on start and dropping
him into the application object (though this might change). The part I was missing was passing the messageManager object to the pipeline before running the pipeline. It seems this was automatic when it was in the web.config file, but has to be done manually
when building your own.
At this point, Profiles, Addresses, Catalogs, Discount, Promotional Codes, Baskets and Pipelines are all working correctly in .Net 2.0. I'll come back and post more information on it once I get my thoughts together for anyone else that finds themselves needing
to do this.
Feb 11, 2006 02:34 PM|bot2601|LINK
I made the solutions I found, and the information I gathered available online for anyone who runs into issues porting their Commerce Server 2002 site from ASP.NET 1.1 to ASP.NET 2.0. You can read the post here :
Thank you to all who helped or tried to help!