[Mono-bugs] [Bug 668497] New: CodeDomProvider.CompileAssemblyFromFile returning an error regarding Info.plist

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Jan 31 20:38:36 EST 2011


https://bugzilla.novell.com/show_bug.cgi?id=668497

https://bugzilla.novell.com/show_bug.cgi?id=668497#c0


           Summary: CodeDomProvider.CompileAssemblyFromFile returning an
                    error regarding Info.plist
    Classification: Mono
           Product: MonoMac
           Version: GIT
          Platform: Macintosh
        OS/Version: Mac OS X 10.6
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Bindings
        AssignedTo: gnorton at novell.com
        ReportedBy: the.justin.walsh at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-US)
AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10

When attempting to use a CSharpCodeProvider targeting v3.5, the
CompileAssemblyFromFile method is returning a rather peculiar error of
"mono[416:60f] No Info.plist file in application bundle or no NSPrincipalClass
in the Info.plist file, exiting".
I have ran the same code in a standard Mono console application and I do not
receive any error when compiling.

Reproducible: Always

Steps to Reproduce:
1. Create a new MonoMac application
2. Create a CodeDomProvider via CSharpCodeProvider with "CompilerVersion" set
to "v3.5"
3. Add some reference assemblies
4. Execute the CompileAssemblyFromFile or CompileAssemblyFromSource
Actual Results:  
Compiler error with the message...
Line 0 - 2011-01-31 18:32:55.760 mono[709:60f] No Info.plist file in
application bundle or no NSPrincipalClass in the Info.plist file, exiting

Expected Results:  
Error free compilation of my assembly source code

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list