[MonoDevelop] single file compile?

Fawad Halim fawad@fawad.net
Thu, 12 Aug 2004 13:24:55 -0500


Without having looked at the SharpDevelop code, it seems that 
SharpDevelop seems to do the equivalent of

msc Foo.cs

i.e. just link against the default set of assemblies (like mscorlib, 
System), and the target is exe. So, you couldn't for example make a 
one-file Windows form app, or reference System.EnterpriseServices in it.

I think that's a good enough behavior because a file-only compile would 
likely be throwaway code for testing something.

-fawad

Todd Berman wrote:

> This has been discussed before, and I don't see how it could possibly be
> truely useful.
> 
> The only way it might end up working, is when we compile, we /r: every
> assembly we know about. Also, a lot of our code completion is based on a
> defined list of references. This wouldn't work as expected for users.
> 
> I am open to patches that would make this work in a sane and consistent
> way.
> 
> --Todd
> 
> On Thu, 2004-12-08 at 10:58 -0500, Fawad Halim wrote:
> 
>>Mike, thanks for the info. I stand corrected. Simon, kindly file a bug 
>>on the bugzilla for this feature request.
>>
>>Regards
>>-fawad
>>
>>Mike Kr├╝ger wrote:
>>
>>>Hi
>>>
>>>SharpDevelop HAS single file compile ... it's easier for the user to 
>>>allow that.
>>>-> That is one issue that really bugs me with most current IDEs and one 
>>>of the points why I wrote #D.
>>>
>>>Regards
>>>Mike
>>>
>>>
>>>>Simon,
>>>>    Other .NET IDEs like VS.NET and SharpDevelop don't let you do that 
>>>>either. The Project is required for passing parameters like output 
>>>>type, references, etc. to the compiler.
>>>>
>>>>-fawad
>>>>
>>>>Simon Males wrote:
>>>>
>>>>
>>>>>I don't think I have ever been able to compile a single .cs file in 
>>>>>MonoDevelop, projects seem to be okay. Are other people experincing 
>>>>>this as well ?