[Mono-osx] My Project Files Moved & Susan's Xcode Plug-in

[Susan Mackay]

Hi Mark,

>I've also been playing with Susan's wonderful Xcode plug-in. Ken
>didn't seem to have much luck with it on his G4 iMac, but I've only
>run in to a few problems on my 12" PB (1GHz G4, 10.4.8, Mono 1.1.18,
>Xcode 2.4).


Firstly thank you for the kind remarks. It's nice to know that someone else
is using the plugin.

I've been in contact with en privately and we resoled the issues that he was
having. Ken added a response to one of my messages indicating the resolution
he found. He was using a ppc-based system but Mono 1.1.17.

>1. Compiling the default Hello-World! app results in the following
>Error:
>"[Session started at 2006-10-15 16:51:51 +0100.]
>
>Unhandled Exception: System.TypeInitializationException: An exception
>was thrown by the type initializer for System.Console --->
>System.NullReferenceException: Object reference not set to an
>instance of an object
>   at System.TermInfoDriver.Init () [0x00000]
>   at System.ConsoleDriver.Init () [0x00000]
>   at System.Console..cctor () [0x00000] --- End of inner exception
>stack trace ---
>
>   at <0x00000> <unknown method>
>   at InstallTest.InstallTest.Main () [0x00000]
>   at InstallTest.InstallTest.Main () [0x00000]
>
>InstallTest has exited with status 1."
>
>By setting the .NET version flag to V1 in the Build tab of the Target
>Info inspector window I got the expected output:
>"[Session started at 2006-10-15 16:54:05 +0100.]
>Goodbye, Forever!
>
>InstallTest has exited with status 0."
>
>What is interesting though is that if you run the V2 compiled program
>from Terminal (or WidgetTerm) it works perfectly. After some poking
>around in the project file, plug-in code and various templates I
>can't see what's going wrong. Could it be a bug in GMCS/Mono on PPC
>or in Xcode on PPC with regards to Xcode's Pseudo Terminal?


I've only just downloaded Mono 1.1.18 and I have not tried installing it yet
(too many other things just at the moment - perhaps in the weekend!!!) so
I'll see if I get the same errors. It may well be something in the way I
build the command line.

Can anyone else try this combination (Mono 1.1.18 on a PPC-based system)
with my plugin?


>2. Adding C Sharp/Executable targets doesn't really work. Adding an
>executable generates the target & it appears OK, but the associated
>Executable is not configured to run /usr/bin/Mono. Also, changing the
>build setting to Release and pressing Build does not actually build
>anything. Haven't checked into this to see what's really going on, so
>it could very well be something I'm doing wrong.

On Page 23 of my (probably very overly verbose) documentation, I make a
comment about a limitation of the plugin when it comes to *ADDING* an
executable target - as you found out it doesn't work without creating a
custom executable, or hacking your 'user profile' file within the project
file. 

If you want this to work, create an executable project and add the library
targets to this.

If you can find a way around this, I would love to hear about it.

>Finally, if you would like me too I'll make the time to make the
>CocoaSharpApplication a proper project template and then someone can
>add it to the files distributed with the plug-in.
>
It's late here and I must admit I'm not sure of your meaning - perhaps you
could explain the reference to the CocoaSharpApplication with respect to the
plugin?

>Frankly I'm really impressed with the work Susan has put into this
>plug-in as it does seem to work reasonably well most of the time.
>When I get my new Macbook Pro (sometime in the next week) I'll try
>comparing Intel/PPC in the (probably vain) hope that it might
>illuminate some of the odd behaviour on PPC. I spent most of the
>summer working in Objective-C and Cocoa, though I would not claim to
>be any kind of expert, so I should be able to track down at least
>some of the bugs. Of course my doing this shouldn't stop the more
>experienced programmers out there from having a go.
>
>Thanks Susan!

My pleasure.

Susan