Driving .NET - All Comments

re: Ruby on the rise

bonskijr — Mon, 25 Jun 2007 05:06:01 GMT

my free cd of Netbeans arrived yesterday.. didn't know they already have 6.0.. and supports ruby.. 5.5 seems ok although the idiosyncrasies of java vs .net that I have to settle first :P

I think I'll wait for IronRuby to mature further w/c I think they'll implement the soonest..

re: Ruby on the rise

smash — Mon, 25 Jun 2007 04:23:59 GMT

Thanks for the heads up bonskijr! The last time I downloaded Aptana they have this teaser about Ruby and somehow it slipped my mind.

BTW, the Netbeans 6.0 Ruby support looks and feels great. And I also got to test the improvements they made on their Swing GUI designer called Matisse, and I'm very surprised to discover that it works a lot better than the previous version.

It got me thinking about giving Java another go. But ofcourse if they can make a Java based Ruby compiler (JRuby) then maybe they can also make a C# compiler too. :)

re: Ruby on the rise

bonskijr — Sat, 23 Jun 2007 06:06:26 GMT

Aptana already is capable of handling Ruby+Rails with its latest incarnation(it combines RadRails IDE w/c it recently acquired)..

MbUnit 2.4 RTM is out

jokiz — Fri, 25 May 2007 00:18:54 GMT

See the official announcement from Andy's blog here . You can download the bits here . Nudge to smash

re: using Backbase forms in ASP.NET

smash — Mon, 21 May 2007 03:37:04 GMT

Though Silverlight 1.1 is still in alpha I was able to use it to create a SPI web application. An invisible Silverlight control acted as the application controller. The thing is the views (html) are embeddeded on the dll. The great thing about this is that i dont have to worry about the user clicking the backbutton since there's no page transition/postback whatsoever. The downside is you will not be able to use those ASP.NET controls anymore and will probably write your own Silverlight controls to replace them. BTW I used Sharpdevelop to write the dll and VWD to write the ASP.NET app.

re: using Backbase forms in ASP.NET

Ron — Fri, 18 May 2007 12:08:19 GMT

I asked them about that edition, and it no longer exists, according to them. I have tried the one for eclipse as well, but that isn't working.

re: a parser tale

jokiz — Thu, 17 May 2007 06:08:28 GMT

let me guess, you haven't tried mbunit yet? mbunit is very helpful for developing unit tests especially for these kind of tasks, specifically the RowTestFixture, try it, i'm sure you'll also be a convert.

re: using Backbase forms in ASP.NET

smash — Thu, 10 May 2007 02:20:54 GMT

Backbase actually has a .NET edition so you can visually design your Backbase enabled webforms in Visual Studio. The downside is it doesnt come cheap, unlike the Client edition.

You can read a blog post comparing Atlas with Backbase.NET here: www.backbase.com/weblog

re: using Backbase forms in ASP.NET

Ron — Mon, 07 May 2007 09:39:43 GMT

That is what the architecture would be if I go with Backbase. I looked up ASHX after I posted. I have done a lot of .NET (since 1.0), but have never come across handler files because I have not had a use for them.

Right now, I am balancing out the pro's and con's of using Backbase and ASP.NET Ajax. With BB, I have to deal with XSLT which is not a fun, and I don't get the use of an IDE for dragging and dropping. I do get an SPI, but I can do the same thing with ASP.NET Ajax, using a command pattern; much like BB.

With ASP.NET Ajax, I have to deal with cross-browser support and probably use something like CSS Friendly Adapters. I am just trying to figure out from an architecture point of view, which one will server us best in the long run with good design and low development time.

There are good and bad things for each.

re: using Backbase forms in ASP.NET

smash — Sat, 05 May 2007 21:48:12 GMT

have you tried putting the WebService call inside an HttpHandler?

re: using Backbase forms in ASP.NET

smash — Sat, 05 May 2007 21:42:58 GMT

response.ashx is an httphandler that simply returns whatever you typed in the textbox. Backbase did all the heavy lifting in placing the string value returned by the httphandler in place of the <div> tag at the bottom.

I think the primary strength of Backbase is in Single Page Interface (SPI), meaning we just have a single HTML page for our web app and just swap the other pages into that single page.

With the release of Silverlight 1.1 SDK, I'm thinking of using XAML for my views in a Single Page Backbase application. I think it could work since Silverlight is touted as a browser friendly technology.

re: using Backbase forms in ASP.NET

Ron — Fri, 04 May 2007 10:28:21 GMT

I am attempting to work with Backbase because I really like the cross-browser compatibility without having to worry about it. We are heavy .NET and are disappointed by some of the problems with AJAX and cross-browser. Unfortunately, BB has not been cooperative when it comes to us wanting to use BB and .NET web services (even sending back XML). Have you had any luck with this? Also, in the example, did you mean ashx, aspx, or asmx?

re: XAML meets Boo

jop — Wed, 04 Oct 2006 22:34:16 GMT

Woah, that's neat. With this you can replace you're view quite easily. As long as both views (or xaml files) contain the same components, it should just work.

re: XAML renders differently

keithrull — Sat, 30 Sep 2006 14:31:50 GMT

i'm currently experimenting in XAML too but haven't had the time to post about it since i'm still stuck with .NET 2.0 apps. Probably in the next year or two we could start rolling out applications using this technology.

re: XAML renders differently

smash — Sat, 30 Sep 2006 09:46:40 GMT

i'm glad you liked the WPF version keith! i have a feeling those who do asp.net apps like you would be able to relate to XAML. :)