A few other comments, sorry for the two separate e-mails. My fingers moved faster than my brain.
Web Services: .NET has built in support for web services. It works much the same way as CF does. It is very easy to use. WebForms: These are great. It allows the application to function in a much more "stateless" way. I have not seen a major performance hit. Looping over Grouped Queries: In .NET you will use things like data grid and data lists to perform these functions. They are very easy to use, once you get the hang of it. I have done some fairly complex things. Error Handling: .NET uses try/catch/throw the same way CF uses it, which is the same way Java did it. It doesn't have anything to compare with the cferror tag, but I hardly ever use that tag. Extendibility: .NET frowns on the use of COM. I personally hate COM; it can cause a number of problems. With .NET you build classes just like you do in Java, or CFCs. The rule of thumb here is that business logic goes in your components. .NET is a true object oriented language. The component are compiled. Language: You left out C++, F#, and J#. F# is still in development, and personally I think looks dumb. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=5 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=5 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5
