SharpDevelop Community

After updating to the latest SharpDevelop 2.0.0 build 1710 compiling boo projects from within SharpDevelop is locking up.  Booc.exe compiles
them fine from outside SharpDevelop though. C# projects build OK.

When I build a boo project from within SharpDevelop, SharpDevelop creates the exe in obj/debug ok, but I have to kill the booc.exe
process for things to continue, whereupon the bin/debug directory is populated with the same exe plus the usual boo dlls.

Why does the build process lock up like this?  I've uninstalled & reinstalled SharpDevelop.  I've cleaned out the ...\Local
Settings\Temp\SharpDevelop\DomCache. I've removed older booc.exe's.  My PATH points to nothing special.  There is no boo stuff in the GAC.

Installing SharpDevelop on a brand new system works fine, though.  But not on my main development machine where I have visual studio 2005
installed.  E.g. I just create a new boo console project and hit play! I see
  Build started.
  Compiling BooCCC2
and the status bar reads
  Building BooCCC2...
forever - until I kill the booc.exe process, that is.

 Any thoughts on fixing my development machine's install of
sharpdevelop?  (P.S. same problem using SharpDevelop_2.1.0.2201_Beta3)

P.S. Could it be that MsBuild is locking up somehow?  Hasn't SharpDevelop
moved to using MsBuild recently?  As I said, I never had this problem
with an older build of SharpDevelop.  Hmm upgrading is always risky -
isn't it!  Is there any way to trace the use of MsBuild and diagnose what is
happening?

cheers,
Andy Bulka
www.atug.com/andypatterns

SharpDevelop 2.x has always used MSBuild. 

If booc.exe is hanging, it's not a problem with MSBuild but with booc.exe itself. Different SharpDevelop versions come with different versions of Boo, so maybe older Boo versions didn't have that problem.

 

You can run msbuild on the command line, or try to compile your program directly using booc to see if you get more information on the console. booc.exe also has a verbose switch to see what's happening inside the compiler.

When I compile my program directly (just a simple hello world) the booc.exe from the sharpdevelop plugins directory works fine.  It doesn't hang.

So either its MSBUILD that is hanging or its is booc.exe that is hanging when called from sharpdevelop.  I don't know what possible parameters are being passed by sharpdevelop to either msbuild or booc.exe - is there a way of seeing or controlling these?  Ideally sharpdevelop would have a 'verbose' mode?

-Andy

I just uninstalled the official 2.0 release
  SharpDevelop2_2.0.1.1710_Setup.exe
and went back to
  SharpDevelop2.0.0.1441_Setup.exe
and everything now works again.

In other words, boo projects build without hanging.  So that's good, but I would rather be using the latest versions of both Boo and Sharpdevelop.

I'm running out of ideas here...

-Andy

Please check that there are no Boo libraries in the GAC. SharpDevelop comes with its own version of Boo, but that booc.exe will load Boo libraries from the GAC instead of the correct libraries in its application directory if Boo is in the GAC. If those libraries are not compatible, all strange things might happen.

Yes, that's DLL hell with the GAC, due to Boo always using the same assembly version number for all releases.

I thought of this and checked a long while ago.  I have double checked - there is no reference to boo in the GAC, according to both VS2005 and the Gacview utility.

I compared the 1710 official release of shardevelop (the one where booc.exe/building locks up) and the earlier 1441 release RC1, which works OK for me.  I compared the BooBinding directory.  The version of boo (and supporting boo dlls) is actually identical!  The only file that is different is BooBinding.dll - were there any significant functionality changes to the binding between these versions that might account for my troubles?   Cos it sounds like booc.exe itself is off the hook (since both versions are the same, and at any rate booc.exe has always run fine from the command line)

cheers,
-Andy

The only change from SD 2.0.0 to SD 2.0.1 (which is incorrectly labelled 2.0.0.1710 on the splash screen) was a bugfix in ICSharpCode.SharpDevelop.dll that could cause serious loss of data when trying to remove the ghost ".." folder that could show up for manually modified .*proj files. All AddIns are completely unchanged (but were recompiled).

I don't remember the changes from SD 2.0 RC1 to SD 2.0.0, but I don't think there was anything changed regarding Boo compilation.

I have no idea why it would happen only for SD 2.0.1. You might want try SharpDevelop 2.1 beta, it comes with a new version of Boo (including support for generics).

When I first encountered this problem, I tried SharpDevelop 2.1 beta and found it had the same problem!

Anyway, after uninstalling 2.0 and reinstalling 2.0 RC1 and then installing 2.0 again - things now seem to be working with the official 2.0 release.  I had tried various uninstall and reinstalls before, but this round of uninstalls/reinstalls seems to have done the trick.  I just hope the problem doesn't come back!  Thanks for your assistance anyway.

cheers,
Andy