Ayende @ Rahien

Andrey Shchekin commented on Castle Style Errors

Mon, 05 Nov 2007 19:08:37 GMT

I absolutely agree. My best exception text saved me a lot of answers on "why this thing is not working". It was (with real library name changed to xxx): "Native library for this platform was not found. There can be two reasons for this exception: 1. You are trying to run the xxx Demo on the 'real' device. The Demo version of xxx can be installed on emulator only. It does not support any other platform types. 2. This exception can occur when the Visual Studio fails to deploy the native library required by xxx. We suppose that it is a problem of Visual Studio unmanaged deployment system. As a workaround, we suggest you to add the xxxlib.dll to your project explicitly, as a content file. The emulator version of this dll can be found in the "[path to xxx]\bin\native\x86\" folder."

Ayende Rahien commented on Castle Style Errors

Mon, 05 Nov 2007 15:01:19 GMT

Bill, Touche! Although, it does give you the source view, which should make it easier.

Bill Pierce commented on Castle Style Errors

Mon, 05 Nov 2007 14:46:24 GMT

When can I see Castle Style errors for the Brail compiler? My dreams are filled with: "INDEX.brail(155,97): BCE0044: Boo.Lang.Compiler.CompilerError: unexpected char: '"' in my 100 line view :)

hammett commented on Castle Style Errors

Mon, 05 Nov 2007 13:53:11 GMT

From my wish list for a better world: NHibernate should have more descriptive error messages.

Markus Zywitza commented on Castle Style Errors

Mon, 05 Nov 2007 11:41:38 GMT

Now it reads: string message = string.Format( "Configuration parser encountered <{0}>, but it was expecting to find " + "<{1}>, <{2}>, <{3}> or <{4}>. There might be either a typo on <{0}> or " + "you might have forgotten to nest it properly.", node.Name, ContainersNodeName, FacilitiesNodeName, ComponentsNodeName, BootstrapNodeName); (Not that my todo-list is empty now, I did it in lunch break instead...)

Markus Zywitza commented on Castle Style Errors

Mon, 05 Nov 2007 11:16:55 GMT

It's already on my (evergrowing) todo-list.

Ayende Rahien commented on Castle Style Errors

Mon, 05 Nov 2007 11:07:00 GMT

Markus, Can you submit a patch that would make the error cleaner?

Markus Zywitza commented on Castle Style Errors

Mon, 05 Nov 2007 10:41:13 GMT

Unfortunately, this is not for all parts of Castle. Last Friday, all my tests failed with this rather mysterious error message: DeserializeElement cannot process element component I examined my component elements and they were all fine. By 7pm I went home, somewhat frustrated. This morning I reread my config, and guess what it was: I forgot components-tags around my single component. YAAAARRRGGG.

Casey commented on Castle Style Errors

Mon, 05 Nov 2007 08:08:41 GMT

Indeed - my Friday was wasted due to SharePoint giving completely useless HRESULT errors ... http://blog.goinsane.co.uk/archive/2007/11/04/sharepoint-server-has-a-4gb-database-limit-wss-has-no.aspx

Evan commented on Castle Style Errors

Mon, 05 Nov 2007 01:15:22 GMT

Agreed. :-)