[MonoDevelop] Import Visual Studio .NET Projects

[Todd Berman]

On Tue, 2005-03-15 at 13:18 -0500, John Luke wrote:
>On Tue, 2005-03-15 at 10:10 -0800, Todd Berman wrote:
>> On Tue, 2005-03-15 at 13:00 -0500, Dean Brettle wrote:
>> >On Tue, 2005-03-15 at 09:26 -0500, Dean Brettle wrote:
>> >> On Tue, 2005-03-15 at 08:01 -0600, Francisco T. Martinez wrote:
>> >> <snip>
>> >> > in my little research I have discovered that MD is not liking 
>> >> > Mono's core 2.0 (the library set you get when you build mono 
>> >> > --with-preview=yes) references.  Have I arrived at the wrong conclusion 
>> >> > with the 2.0 references?
>> ><snip>
>> >> I was planning to look into it sometime over the next couple days.
>> >
>> >Found the problem, created a bug, and attached the patch to the bug.
>> >
>> >See:
>> >
>> >http://bugzilla.ximian.com/show_bug.cgi?id=73724
>> >
>> >Cheers,
>> >--Dean
>> 
>> As I said in the bug report, that isnt everything that is needed. I
>> (think) we need to use gmcs to build, and only allow either 1.0 or 2.0
>> references, otherwise you can easily get into huge issues.
>> 
>> Also, our parser doesn't support the 2.0 syntax extensions (generics,
>> etc)
>> 
>
>Although it would be nice, I think you can do the first two things
>without 2.0 parser support.  People will just have to understand it
>could cause problems like breaking completion but I don't think it will
>crash.
>
>Then we can add some 2.0 parser features as we go, with generics
>probably being last.


That sound's good as far as the parser, however I think to accept
allowing 2.0 assemblies to be used we have to have the following (all in
one single patch)

1) Ability to pick gmcs/mcs and use it properly
2) Only allow gmcs + 2.0 assemblies or mcs + 1.0 assemblies and not
allow mixing 1.0 and 2.0 assemblies.

Also, as a bit of warning, I think we need to make sure that we
completely load assemblies out of process, because I am not even sure
that we can generate a 2.0 mscorlib completion database.

--Todd