Archive for May 2010
May 14, 2010 | 
Author Today, I got latest code from TFS and setup my application. When I execute the application I got wired error.
|
An exception of type ‘Microsoft.Commerce.Providers.Exceptions.ContextCreationException’ occurred and was caught. |
I have only one commerce server site configured in my application and from frontend configuration, I can’t connect to another commerce server in different machine (currently CS and MOSS are hug and can’t work from different machines). After troubleshooting further, I found that it is due to the case sensitive of site name in channelconfiguration file. The CS site created on my desktop is “SiteName” and the site name in channel configuration file is “Sitename”. After changing the site name, the application started working fine.
Even though the fix is simple but would like to keep it in my blog so that fellow developers (like me) will not waste their time much in fixing this simple issue.
If you like this post, please click on our sponsor advertisement.
Posted in 
There are no specific exception handling guidelines for CS2009. Through CS foundation (operation sequence components), we are calling different the services which performs some action and returns few validation exceptions for invalid data or conditions. We thought of creating custom exception class for each type of validation message so that the client application can react accordingly. Below diagram shows the high level architecture of exception handling across layers.
The implementation went smooth but the real problem came when we try to test the code. We are getting fault exception from the service and can be able to catch it properly in operation sequence components but when the control goes from operation sequence components to app layer the exception is converted as Generic exception. Not sure, where is the problem is and why the exception is converted back to generic exception. After troubleshoot further and digging through CS2009 code with reflector, I found that commerce server broker is catching all exceptions and converting to generic exceptions (except fault exceptions). Check below image for more details.
I feel, Microsoft feels it may be security issue of sending back all (external or internal) exceptions back to calling program and that might be the reason for suppressing all exceptions except fault exception. I have to changed my application architecture and now I am bringing fault exceptions and handling them in controller or presenter level which is still satisfying my requirement.
If you like this post, please click on our sponsor advertisement.
