------------- Also, it's very difficult to build ASP.NET apps without Visual Studio.NET. The huge files are difficult to navigate with a regular text editor. ------------------ The files are only huge if you created them in VS first using the visual tools. The generated code tends to have a lot of extra 'fluff'
Having had a couple of .NET projects that were basically straight ports of CF apps, I can attest that if you approach .NET as you would a typical OO ColdFusion app, the differences in general architecture aren't terribly large. 90+% of the process was simply syntax conversion, and you can often end up with less code simply due to C# or VB having a much less verbose syntax than CF. I still prefer CF for the most part, but .NET has its charms if you don't get too wrapped up in the whole 'visual' coding paradigm. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:262161 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
