[MonoDevelop] ASP.NET Project and Web Deploy

Michael Hutchinson m.j.hutchinson at gmail.com
Mon Dec 8 12:45:45 EST 2008


The internal list of deploy files is built from several sources. Normally
projects include the binaries, 'local copy' references, the 'copy to output'
files, and any files that are explicitly marked for deployment (see the
property pad when selecting a file in the solution pad). ASP.NET projects
also include all files with a 'content' build action.

If it's not working for one of your projects, please file a bug.

On Dec 7, 2008 5:00 PM, "Etienne Fortin" <etienne.fortin at sympatico.ca>
wrote:

Hello All,
Don't know if it's the right place to talk about this, but since it's
related to Monodevelop (and ASP.NET plugin), I'll ask my question here.

I have a WebApplication (Screwturn Wiki Engine not to name it). I want to
use the Web Deploy feature of Monodevelop. It deploy some files, but not
all. All the files are tagged as "Content" in build action, but not all are
transfered to the deployment target. Is only the build action taken into
account by Monodevelop when deciding if a file should be copied to the
target deployment directory? Or is there anything else involved in the
decision?

By the way, the project has been created in Visual Studio 2008 and compiled
with the latest Trunk code of Monodevelop (r120939).

Etienne


_______________________________________________
Monodevelop-list mailing list
Monodevelop-list at lists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/monodevelop-list/attachments/20081208/bb3efaa8/attachment.html 


More information about the Monodevelop-list mailing list