SharpDevelop Community

On my Windows XP x64 system i can't build any Boo project.

SharpDevelop's output looks like this:

Build started.
Compiling myBoo
Error BCE0000: Unable to load assembly (bad file format): Assembly manager loaded from:  h:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
Build finished successfully.

Also, i've tried to debug IDE (using source code) and there was an exception during loading project: 

SharpDevelop Version : 2.2.1.2648
.NET Version         : 2.0.50727.1433
OS Version           : Microsoft Windows NT 5.2.3790 Service Pack 1
Current culture      : Russian (Russia) (ru-RU)
Current UI language  : en-US
Working Set Memory   : 202648kb
GC Heap Memory       : 138243kb

Exception thrown:
Debugger.DebuggerException: Stepper is not in collection
   at Debugger.Thread.GetStepper(ICorDebugStepper corStepper)
   at Debugger.ManagedCallback.StepComplete(ICorDebugAppDomain pAppDomain, ICorDebugThread pThread, ICorDebugStepper pStepper, CorDebugStepReason reason)
   at Debugger.ManagedCallbackProxy.<>c__DisplayClass1.<StepComplete>b__0()
   at Debugger.MTA2STA.<>c__DisplayClass3.<EnqueueCall>b__0()
   at Debugger.MTA2STA.PerformAllCalls()
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

The first problem looks like there is some problem with Boo compiler or the MSBuild reference lookup on 64bit Windows, I'll reboot into XP 64bit and will try to reproduce it.

The second problem is a known bug in the debugger. 

I found the exact problem now. Wow, I just spent 5 hours on this - though most of this updating my Windows XP 64 installation (last time I needed it was last June), then trying to install .NET 3.5 to test SharpDevelop 3.0, only to have the installation fail, so I removed .NET 2.0, which also failed, but googling for the error code I found a KB entry with a workaround that solved my problems: remove the drive letters from all CD-ROM drives (WTF???)

Back to your issue, the problem is that SharpDevelop.exe is a 32-bit process (Subversion AddIn and debugger are not yet 64-bit compatible) and uses 32-bit MSBuild; but booc.exe is marked as "AnyCPU" and runs as 64-bit process. 32-bit MSBuild tells booc to use the 32-bit versions of the .NET libraries, which of course fails in a 64-bit process.

You can solve the problem by marking booc.exe as 32-bit only. Open a command prompt, cd to the directory ...\SharpDevelop\2.2\AddIns\AddIns\BackendBindings\BooBinding, and run the command "corflags booc.exe /32BIT+". (corflags.exe is part of the .NET 2.0 SDK).

Alternatively you could also use corflags.exe to remove the 32-bit only flag from SharpDevelop.exe - the Subversion AddIn will be disabled automatically; the debugger will sort-of work but tends to crash and/or hang often after debugging (you could disable the debugger using the AddIn Manager).

Thanks for focusing attention on this problem.

I had some ideas, that there is an incompartibility between 32 and 64 assembly images, but i didn't know corflags tool. :)