Thanks for the help and clarification -- I realized you didn't need MonoDevelop to develop for Mono, but I was relatively sure I read something about the 'web site' not working somewhere (in addition to MonoDevelop not recognizing them). Mea culpa.
Thanks :) On Wed, Jan 19, 2011 at 1:15 PM, Justin Malcolm <[email protected]>wrote: > Jeff, > > Mono itself support both 'Web site' and 'Web project' well. > > The issue is that MonoDevelop does not support 'Web site'. > > Of course, you do not need to use MonoDevelop to develop your project. My > first Mono site was built using 'Web site' on Web Developer Express years > ago. > > It seems to be a common misconception that you need to use MonoDevelop to > develop Mono apps. MonoDevelop is just a .NET IDE that runs on Linux, OS X, > and Windows. You can develop for .NET without using MonoDevelop at all > using MonoDevelop. > > Similarly, you can develop using any other .NET IDE and then deploy the > results on Mono anywhere that Mono runs. > > It is ideal to develop and test on the platform on which you will deploy of > course but the fact that MonoDevelop does not support 'Web site' does not > stop you from using Mono. > > On 19 January 2011 06:54, JZ <[email protected]> wrote: > >> >> I'm in the process of evaluating Mono for my job -- We'd love to break the >> shackles Windows has on us right now! To that end, I've managed to get our >> framework building and passing tests on Linux, which is a step in the >> right >> direction for sure. >> >> Unfortunately, our two websites are of the 'Web site' vs 'Web project' >> type. >> I'm not sure what the exact term is, but the websites don't have .csproj >> files, and are compiled 'on the fly', both the .aspx and .aspx.cs files >> sit >> on our webserver and are updateable. >> >> It's my understanding that Mono doesn't support this type of web project. >> 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 sites >> 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 >> until >> 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 >> least). >> >> I'd appreciate any tips or pointers in the right direction, thanks! >> -- >> View this message in context: >> http://mono.1490590.n4.nabble.com/Porting-Website-with-Codebehinds-tp3225417p3225417.html >> Sent from the Mono - ASP.NET mailing list archive at Nabble.com. >> _______________________________________________ >> Mono-aspnet-list mailing list >> [email protected] >> http://lists.ximian.com/mailman/listinfo/mono-aspnet-list >> > >
_______________________________________________ Mono-aspnet-list mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-aspnet-list
