Looks like that might be the reason, yes.

On Fri, Feb 27, 2009 at 7:56 AM, Martin Nilsson <[email protected]> wrote:

> If I change to my previous Boo.Lang.Compiler it's working again.
> Has Boo been upgraded?
>
>
> On Fri, Feb 27, 2009 at 1:36 PM, Martin Nilsson <[email protected]>wrote:
>
>> I'm getting the same error after upgrading to latest trunk.
>>
>> The layout:
>>
>> <html>
>>     <head>
>>          <title>Title</title>
>>     </head>
>>     <body>
>>         Test
>>     </body>
>> </html>
>>
>> Stacktrace:
>>    at System.ThrowHelper.ThrowKeyNotFoundException()
>>    at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
>>    at Boo.Lang.Compiler.CompilerContext.GetService[T]()
>>    at
>> Boo.Lang.Compiler.Steps.ProcessMethodBodies.get_CallableResolutionService()
>>    at
>> Boo.Lang.Compiler.Steps.ProcessMethodBodies.GetCorrectCallableReference(Node
>> sourceNode, ExpressionCollection args, IEntity[] candidates)
>>    at
>> Boo.Lang.Compiler.Steps.ProcessMethodBodies.GetCorrectConstructor(Node
>> sourceNode, IType type, ExpressionCollection arguments)
>>    at
>> Boo.Lang.Compiler.Steps.ProcessMethodBodies.ProcessConstructorInvocation(MethodInvocationExpression
>> node, IEntity targetEntity)
>>    at
>> Boo.Lang.Compiler.Steps.ProcessMethodBodies.ProcessMethodInvocationExpression(MethodInvocationExpression
>> node, IEntity targetEntity)
>>    at
>> Boo.Lang.Compiler.Steps.ProcessMethodBodies.OnMethodInvocationExpression(MethodInvocationExpression
>> node)
>>    at
>> Castle.MonoRail.Views.Brail.ReplaceUknownWithParameters.OnMethodInvocationExpression(MethodInvocationExpression
>> node) in
>> d:\OSS\Castle\trunk\MonoRail\Castle.MonoRail.Views.Brail\ReplaceUknownWithParameters.cs:line
>> 59
>>    at Boo.Lang.Compiler.Ast.MethodInvocationExpression.Accept(IAstVisitor
>> visitor)
>>    at Boo.Lang.Compiler.Ast.DepthFirstVisitor.Visit(Node node)
>>
>> System.Collections.Generic.KeyNotFoundExceptoin: {"The given key was not
>> present in the dictionary."}
>>
>> Btw, the dictionary is empty
>>
>> Setting the parameter (statusMessage) in the controller action and having
>> below view doesn't help either:
>>
>> <html>
>>     <head>
>>          <title>Title</title>
>>     </head>
>>     <body>
>>         ${statusMessage}
>>         Test
>>     </body>
>> </html>
>>
>>
>> On Tue, Feb 24, 2009 at 6:50 PM, Adeel <[email protected]> wrote:
>>
>>>
>>> *** Because of a glitch with google/ gmail, this message did not
>>> appear in the list, so I am sending it again, if someone has already
>>> received this message, please do ignore it***
>>>
>>>
>>> I upgraded to trunk the trunk yesterday.  As a newbie to castle, I
>>> tried to get a view running, but for every page I try to open I get a
>>> Parser Error. I am using brail as a viewengine to be exact.
>>>
>>>  Parser Error
>>> Description: An error occurred during the parsing of a resource
>>> required to service this request. Please review the following specific
>>> parse error details and modify your source file appropriately.
>>>
>>> Parser Error Message: Internal compiler error: The given key was not
>>> present in the dictionary
>>>
>>> Source Error:
>>>
>>> Line 1:
>>> Line 2:  output """<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
>>> Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
>>> Line 3:  <html xmlns="http://www.w3.org/1999/xhtml";>
>>>
>>> Source File: layouts/default.brail    Line: 1
>>>
>>> The error is on line 1, but this line is empty.
>>> I have tried stripping everything out of the view and still the error
>>> persists.
>>>
>>> Does anyone have a clue?
>>>
>>> Kind regards
>>>
>>>
>>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Castle Project Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/castle-project-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to