Who doesn't love a good "versus" debate?

re: Who doesn't love a good "versus" debate?

Jeff — Mon, 16 Oct 2006 23:55:03 GMT

I didn't ask you for your opinion, I asked if it was being used in production. You can go on all day about whether or not you think it's ready, but you haven't used it, so your opinion means little to me.

re: Who doesn't love a good "versus" debate?

Jigar — Mon, 16 Oct 2006 23:50:28 GMT

"http://local.live.com/ not in production?"

Use of atlas at live.com does not mean any thing, I don't think that I can convince my superior to use software which still going beta stage(in fact its still pre-beta) for production site

According to Scott Guthrie we are still two to three months away from release.

"Atlas" 1.0 Naming and Roadmap

re: Who doesn't love a good "versus" debate?

Scott — Fri, 13 Oct 2006 20:24:05 GMT

Let me clarify that. In my experience, Visual studio 2005 is a disaster when doing Winforms development. I haven't had any problems using Either Web Developer Express or VS 2005 for ASP.NET development. A few things I've had happen to me while using VS 2005 for Winforms development: 1) columns in the DataGridView are re-arrainged when opening the form in the designer. 2) Runtime errors when using generated ST datasets with generated SQL and sprocs. 3) VSTS only: "Run tests" button is disabled after running and I had restart the IDE to get it to come back. May be something I was doing wrong, but it wasn't intuitive. 4) "Cannot find Microsoft .NET 2.0.blah blah" when compiling with ClickOnce security enabled. Known bug. 5) Set DataGridView column visible=false, compile, run, column shows up in DataGridView. Have to re-set column visibility after databinding. 6) When addding queries to existing table adapters, I sometimes get an dialog box showing an error in the designer telling me that it can't load the connecion string. Even though there is only one connection string defined in the project and it has the same name as the connection string it says it can't load. IMO, Winforms 2.0 was left by the wayside in the tidal wave of WPF development and it shows in the IDE support.

re: Who doesn't love a good "versus" debate?

Jeff — Fri, 13 Oct 2006 17:34:30 GMT

I'll never understand that either, how VS 2005 is a "disaster." Compared to what? I use it every day, and it's not very frequent that the IDE gets in the way of development.

re: Who doesn't love a good "versus" debate?

Scott — Fri, 13 Oct 2006 16:06:36 GMT

Hmmmm, what would you think of a port of Django to IronPython? re: learning Ruby. It's a small language and the syntax makes a lot of sense. I use Ruby(under linux/OSX) or Python(under windows) instead of VBScript or Bash script for day-to-day one-off and admin scripts. Rails is great for prototyping. Although I'm considering writing a few upcoming small appliations using it simply because Visual Studio 2005 is a disaster. It drove me back to EditPlus development.

re: Who doesn't love a good "versus" debate?

ian — Fri, 13 Oct 2006 08:36:08 GMT

I think Rails is popular because a large number of people have an almost religious fervour that prohibits them from using anything by Microsoft.

re: Who doesn't love a good "versus" debate?

Jeff — Fri, 13 Oct 2006 04:03:26 GMT

Not ready for production? Is http://local.live.com/ not in production?

re: Who doesn't love a good "versus" debate?

Jigar — Fri, 13 Oct 2006 03:32:29 GMT

"...That's pretty AJAXy to me, and idiot proof if you already get ASP.NET." Unfortunately it’s still not ready for production probably we are still two months away from release I am asp.net developer by profession, I tried rails just out of curiosity and from what I have seen so far in Rails it looks promising for at least small to medium sized application.

re: Who doesn't love a good "versus" debate?

Jeff — Fri, 13 Oct 2006 00:16:14 GMT

http://atlas.asp.net

...That's pretty AJAXy to me, and idiot proof if you already get ASP.NET.

re: Who doesn't love a good "versus" debate?

Jigar — Thu, 12 Oct 2006 22:57:16 GMT

"Asp.net 2.0's only real problem is that it needs LINQ now not later" You missing AJAX, Rails has one of the most beautiful integration of AJAX I have seen so far.