This is indeed strange.
- What version of Monobjc are you using ?
- Have you tried to build the SparkleSampleApp and test it ?
- Can you post the top of the debug log ?
Regards, Laurent Etiemble.
2011/1/20 Edward Gent <e.g...@oodrive.fr>
> Hi Laurent,
> Looking at the debug output, the application is not looking for the
> Framework its embedded Frameworks directory,
> "myapp.app/Contents/Frameworks". It looks only in the following directories
> So I really don't know what I'm missing here.
> Thanks for your help
> ----- Original Message -----
> From: "Laurent Etiemble" <laurent.etiem...@monobjc.net>
> To: firstname.lastname@example.org
> Sent: Wednesday, 19 January, 2011 10:43:41 PM
> Subject: Re: [email@example.com] Embedding the Sparkle Framework in
> a Bundle (Not loading)
> You can start by checking that everything is ok with the SparkleSampleApp
> which is included in the Monobjc distribution. Refer to
> http://www.monobjc.net/index.php?page=samples if you need help to build
> the sample applications.
> With your application you can try:
> - Open the Terminal application and go where your application is
> - Execute the following command:
> export MONOBJC_DEBUG=3
> - Launch you application:
> ./YourBundle.app/Contents/MacOS/YourBundle > output.log
> - The output.log file will contains many useful logs. Look at the start of
> the file; you should see the loading phase logs along with the scanned
> folders. It should help to diagnose what is going wrong.
> Let me know of the result.
> Regards, Laurent Etiemble.
> 2011/1/19 Edward Gent <e.g...@oodrive.fr>
>> Hi All,
>> We are currently having trouble getting the Sparkle framework to load
>> during startup via ObjectiveCRuntime.LoadFramework("Sparkle"), we used the
>> example provided on the Monobjc site as a *strict* guideline on what
>> needs to be done. Unfortunately LoadFramework doesn't seem to look in the
>> Application bundle Contents/Frameworks directory for the Sparkle framework.
>> If I put the framework in /Library/Frameworks everything works fine, what
>> are we missing here?
>> Maybe the problem due to the Application being a standalone embedded Mono
>> OSX application???
>> Thanks for any help