[MonoDevelop] Build and Deploy ASP.NET MVC Project

[Marcelo Zabani]

Thanks a lot for the answer, the link to your blog post and the
Microsoft.WebApplication.targets file.
Although I would certainly enjoy having a powerful xbuild system and a
completely automated deploy script, these are not top priority for me right
now. I would love, however, to help with ASP.NET where I can, since I'm an
avid user of mod_mono and xsp.
Do you, by chance, have any pointers on what areas of ASP.NET need more
attention right now and where to look at to be able to help? I would love
to spend a couple hours every weekend trying to improve ASP.NET on mono.

Thanks,


On Fri, Mar 29, 2013 at 7:03 PM, Michael Hutchinson <
m.j.hutchinson at gmail.com> wrote:

> On 27 March 2013 09:50, Marcelo Zabani <mzabani at gmail.com> wrote:
> > What happens when I build a ASP.NET MVC project? I mean how does
> MonoDevelop
> > create a build command? I have successfully built with xbuild
> > /property:Configuration=Release MySolution.sln. Is this what MonoDevelop
> do?
>
> MonoDevelop currently build most project types using its internal
> build engine, unless you enable the experimental xbuild engine. For
> more details, see
>
> http://mjhutchinson.com/journal/2012/08/19/state_msbuild_support_monodevelop
>
> > Also and more important, what happens when I use the Deploy to Web
> > functionality? What command is used by MonoDevelop? I have gone crazy
> over
>
> This is currently done with MD's internal deployment infrastructure.
> Essentially, it copies the project's content and output files to a
> directory. It deploys to ssh by mounting the remote directory using
> sshfs and copying the files to the mounted directory.
>
> > mdtool, xbuild and google and can't find a suitable solution to this.
> > And one last thing. Apparently my Web.Config.Release and Web.Config.Debug
> > transformations are not used at all. Is this a matter of improving the
> > .csproj files to apply the appropriate transformations for ASP.NETprojects?
>
> Correct, these transformations are not currently supported.
>
> Unfortunately, adding full support for the MS compile/deploy features
> is quite a lot of work. Ideally, we would enable the xbuild engine for
> Web projects, and improve complete Mono's implementation of
> Microsoft.WebApplication.targets (would need to *cleanly* reverse
> engineered the MS version). Mono's Microsoft.WebApplication.targets
> does not support many of the publishing/deployment features that the
> MS version does - you can see Mono's are very bare-bones
> (
> https://github.com/mono/mono/blob/master/mcs/tools/xbuild/xbuild/Microsoft.WebApplication.targets
> )
> and we don't have an implementation of
> Microsoft.Web.Publishing.targets at all.
>
> > If so, can I help with anything to get this done?
>
> Sure, we really need contributors for MD's & Mono's ASP.NET support.
> You could start out by building MD/Mono from source, then try
> implementing the features you care about (but make sure you read
> http://www.mono-project.com/Contributing#Important_Rules). And feel
> free to ask here and on the mono-devel-list if you need pointers :)
>
> --
> Michael Hutchinson
> http://mjhutchinson.com
>



-- 
Marcelo Zabani
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/monodevelop-list/attachments/20130330/b294fcf8/attachment.html>