[Mono-aspnet-list] Porting Website with Codebehinds
maxr at expeditions.com
Wed Jan 19 11:03:45 EST 2011
Talking from my experience, Mono can compile on a fly. However, I always thought that putting source code out there is not a good idea. So I use Web Deployment Project to pre-compile everything and then just FTP files over to my server (works great btw!).
> -----Original Message-----
> From: mono-aspnet-list-bounces at lists.ximian.com [mailto:mono-aspnet-
> list-bounces at lists.ximian.com] On Behalf Of JZ
> Sent: Wednesday, January 19, 2011 9:55 AM
> To: mono-aspnet-list at lists.ximian.com
> Subject: [Mono-aspnet-list] Porting Website with Codebehinds
> I'm in the process of evaluating Mono for my job -- We'd love to break
> shackles Windows has on us right now! To that end, I've managed to get
> framework building and passing tests on Linux, which is a step in the
> direction for sure.
> Unfortunately, our two websites are of the 'Web site' vs 'Web project'
> I'm not sure what the exact term is, but the websites don't have
> files, and are compiled 'on the fly', both the .aspx and .aspx.cs files
> on our webserver and are updateable.
> It's my understanding that Mono doesn't support this type of web
> I'm willing to lose the 'on the fly' and 'updatable' nature of the
> sites, no
> problem -- but if at all possible I'd like to avoid converting these
> to .csproj web projects. I'd like to leave the current workflow as
> undisturbed as possible for the developers working on Windows/VS. I'm
> willing to put it work to create a mono-specific (I'll write Makefiles
> my eyes bleed if that's what it comes down to) build process if it's
> possible to make the sites work with no changes (prior to Mono build at
> I'd appreciate any tips or pointers in the right direction, thanks!
> View this message in context:
> Sent from the Mono - ASP.NET mailing list archive at Nabble.com.
> Mono-aspnet-list mailing list
> Mono-aspnet-list at lists.ximian.com
More information about the Mono-aspnet-list