MonoDevelop AssemblyBoo build errors preventing me from using debugg

First off, the game works in unity and i can play.
The only problem is that the MonoDevelop Assembly-Boo get 4 errors when building, this prevents me from using the MonoDevelop debugg mode which i need.
I have gone through the warnigns there seems to be no warning that is accositated with these errors.
The errors are:
Error BCW0000: WARNING: Could not load types from ‘UnityEditor, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null’: System.IO.FileNotFoundException: Could not load file or assembly ‘UnityScript, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’ or one of its dependencies. The system cannot find the file specified. (BCW0000: WARNING: Could not load types from ‘UnityEditor, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null’: System.IO.FileNotFoundException) (Assembly-Boo)

Error File name: ‘UnityScript, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’ (File name) (Assembly-Boo)
Error WRN: Assembly binding logging is turned OFF. (WRN) (Assembly-Boo)
Error Note: There is some performance penalty associated with assembly bind failure logging. (Note) (Assembly-Boo)

Anyone got any idea whats the problem is?

The first two problems only appear when unity is running.
But still got this problem left.

Error Fatal error: Unable to load assembly (bad file format): WRN: Assembly binding logging is turned OFF. (Fatal error: Unable to load assembly (bad file format): WRN) (Assembly-Boo)

Could not start monodoc : System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at MonoDevelop.Core.Execution.ProcessWrapper.Start() in c:\BuildAgent\work\8aca918ee1e565a1\monodevelop\main\src\core\MonoDevelop.Core\MonoDevelop.Core.Execution\ProcessWrapper.cs:line 26
at MonoDevelop.Core.Execution.ProcessService.StartProcess(ProcessStartInfo startInfo, ProcessEventHandler outputStreamChanged, ProcessEventHandler errorStreamChanged, EventHandler exited) in c:\BuildAgent\work\8aca918ee1e565a1\monodevelop\main\src\core\MonoDevelop.Core\MonoDevelop.Core.Execution\ProcessService.cs:line 163
at MonoDevelop.Core.Execution.ProcessService.StartProcess(String command, String arguments, String workingDirectory, ProcessEventHandler outputStreamChanged, ProcessEventHandler errorStreamChanged, EventHandler exited, Boolean redirectStandardInput) in c:\BuildAgent\work\8aca918ee1e565a1\monodevelop\main\src\core\MonoDevelop.Core\MonoDevelop.Core.Execution\ProcessService.cs:line 116
at MonoDevelop.Core.Execution.ProcessService.StartProcess(String command, String arguments, String workingDirectory, TextWriter outWriter, TextWriter errorWriter, EventHandler exited, Boolean redirectStandardInput) in c:\BuildAgent\work\8aca918ee1e565a1\monodevelop\main\src\core\MonoDevelop.Core\MonoDevelop.Core.Execution\ProcessService.cs:line 106
at MonoDevelop.Ide.HelpOperations.CheckExternalMonodoc() in c:\BuildAgent\work\8aca918ee1e565a1\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Ide\HelpOperations.cs:line 85

Then a popup with this text appears.
You need a newer monodoc to use it externally from monodevelop. Using the integrated help viewer now.

Well it worked with unity 3.3 so i expect help with this.