This project has moved and is read-only. For the latest updates, please go here.

solution works in test & debug but not on server - "Path cannot be the empty string or all whitespace"

Jun 20, 2013 at 6:50 PM
I have a suite of components that are designed to be reused over quite a few large/small disparate developments/solutions. These all work fine in debug and integration test off server but when they are deployed to the test server environment we get strange and in the end unhelpful errors messages. We have had to go back into the code to increase the information we could get out of the system as the exceptions were originally pointing us to the dreaded "Loader Exceptions" collection and then the "CompositionException.Errors" exception.

Components stored each in their own directory - not in the exec folder/subfolder - they get pulled in to the Container by a bit of bootstrap code which uses absolute refs to each component's directory to create a DirectoryCatalog for each component which gets added to an AggregateCatalog.

In debug/testing this all works fine.

The server pumps out this message:

"The composition produced a single composition error. The root cause is provided below. Review the CompoistionException.Errors property for more detailed information.

1) Path cannot be the empty string or all whitespace.

Resulting in: An exception occurred while trying to create an instance of type 'email.sender'..."

It then goes on to list the subsequent fails because this "email.sender" failed.

We have taken this and all dependent modules and removed the directory ref bootstrapper bit and directly referenced the components and simply cataloged the BaseDirectory - with the same results - good in debug and bad on server.

Any clues please?