[Mono-aspnet-list] Develop in VS, Deploy to Linux/Mono Best Practices

Stifu stifu at free.fr
Tue Jul 6 18:02:58 EDT 2010

Keep in mind that you may encounter Mono-specific bugs, or non-implemented
things, so don't expect everything to always work perfectly. Simply copying
files won't let you debug such issues easily.

stevenjamesfrank wrote:
> I am currently evaluating development of an ASP.NET site that is to be run
> on Linux/Apache with Mono.
> My desired workflow is to do all development and compilation on a Windows
> workstation, then copy/transfer the required output to the Linux/Apache
> box.
> My plan is to create a new web site in VS, with a location of my
> workstation's filesystem, then with each build, simply copy the directory
> structure up to the Linux box (probably with Samba).  The other options
> are a direct HTTP link to the web server (which without IIS will obviously
> not work) or having the build go to an FTP server (ostensibly on the Linux
> server) which, I believe, would also work for me.
> Assuming that Apache is set up properly to run the site, the ASP.NET code
> should run, correct?
> I'm I missing something from the workflow?
> Thanks!

View this message in context: http://mono.1490590.n4.nabble.com/Develop-in-VS-Deploy-to-Linux-Mono-Best-Practices-tp2280224p2280265.html
Sent from the Mono - ASP.NET mailing list archive at Nabble.com.

More information about the Mono-aspnet-list mailing list