Matthew you appear to have taken offence to my comparisons, I did not intend to belittle .net in anyway. I will openly admit when I built the site and added the comparisons over a year ago, I was new to .net. I am not biased either over the past year and a half I have become a highly certified MCPD, I admit I have been a CF developer for the past 10 years and love it but I find .net equally as exciting ITS ALL WEB TO ME!
The aim of the site is to at the very least point either a CF or .net developer in the right direction regarding a specific piece of functionality. The goal is to open up the barriers between the two languages, if you know better ways of representing a particular piece of functionality just email me and I will update the entry happily. I honestly did not mean to annoy anyone, there is always more than one way to achieve something. This is an academic free resource I'm all for learning and sharing the knowledge ;) Jose Diaz On Wed, Jun 23, 2010 at 6:47 PM, Matthew Small <chestypul...@beachbum.net>wrote: > > All language religion aside - it's not a fair comparison, it's biased > towards CF. You should be more honest in your comparisons if you expect > anyone to take it seriously. > > Example: > > CFEXECUTE: > > CF: > <cfexecute name="C:\WinNT\System32\netstat.exe"> > </cfexecute> > > > ASP.NET <http://asp.net/> > > 01.using System; > 02.using System.Drawing; > 03.using System.Collections; > 04.using System.ComponentModel; > 05.using System.Windows.Forms; > 06.using System.Data; > 07.using System.Diagnostics; > 08. > 09. ... > 10. > 11. //Declare and instantiate a new process component. > 12. System.Diagnostics.Process process1; > 13. process1= new System.Diagnostics.Process(); > 14. > 15. //Do not receive an event when the process exits. > 16. process1.EnableRaisingEvents = false; > 17. > 18. > 19. //The "/C" Tells Windows to Run The Command then Terminate > 20. string strCmdLine; > 21. strCmdLine = "/C netstat "; > 22. System.Diagnostics.Process.Start("CMD.exe",strCmdLine); > 23. process1.Close(); > > > > All that is actually needed is: > > System.Diagnostics.Process.Start("netstat.exe"); > > All of the other stuff is extraneous. The need for the "using" statements > is negated by the fully-qualified name for the method. The object > "process1" isn't used at all for the actual execution. Passing the > netstat.exe executable to the cmd.exe process is ridiculous - you could do > the same with CFEXECUTE. Adding in extra string arguments just builds up the > amount of code you want to display. And FYI: this one line of code can be > executed in the .aspx page: > > <% System.Diagnostics.Process.Start("netstat.exe") %> > > There are numerous similar examples on your website. It's a dishonest > misrepresentation. > > - Matt Small > > > > > > > >This is pretty sweet Jose. > > > >Thanks for taking the time to create this site! An excellent resource > >indeed. > > > >Warm regards, > >Jordan Michaels > >Vivio Technologies > >http://www.viviotech.net/ > >Open BlueDragon Steering Committee > >Railo Community Distributions > > > >On 06/22/2010 06:47 AM, Jose Diaz wrote: > >> > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:334778 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
