[Monodevelop-devel] how to fix moonlight project reference?

Michael Hutchinson m.j.hutchinson at gmail.com
Wed Apr 29 14:27:41 EDT 2009

2009/4/10 Atsushi Eno <atsushieno at veritas-vos-liberabit.com>:
> I am trying to fix assembly references in Moonlight [app/lib] projects,
> which are regarded as pointing to missing ones. I guessed that they
> are expected as wrong versions and hence added assembly versions
> (like there is in asp.net addin), as the attached patch, but it does
> *not* seem to fix the issue.
> So I wonder if references to 2.1 assemblies are resolved successfully
> in MD now. Any idea how to fix this issue?

In MD trunk it works for me.

Do you have the Moonlight assemblies installed to ~/lib/mono/2.1/?

> Or even better, it would be nicer if we can simply load Silverlight
> projects in moonlight, either as a moonlight project or new different
> one to replace (or coexist?) current ones.

You can already. I just tested opening a VS-created Silverlight
project and it still works.

Building xaps doesn't work yet, but MD can create/load Silverlight
projects and compile Silverlight library projects. Also, code
completion (including simple XAML code completion) uses the 2.1
assemblies. And there's even a xamlg-based parser that injects
codebehind partial classes into MD's code completion DOM.

The missing parts of Moonlight/Silverlight support are:
* xamlg invocation
* respack invocation
* xap manifest generation
* xap zipping
* generating host HTML page for previewing the xap

The xamlg invocation is the blocker, since it requires modifying MD
core, so that the compilation pipeline supports building files that
aren't part of the project

Michael Hutchinson

More information about the Monodevelop-devel-list mailing list