Walter;

I have yet see any software development tool developed to its full potential or promise. When profits become too small, a new tool will be introduced to stimulate a company’s bottom line. If developers are left out in the cold so what? Surely there will be new or existing developers to purchase and use the new tools.

I see a number of reasons for creating new tools besides profit. Some technologies “hit the wall”. That is developers push the envelope and find it impossible to create a solution that is demanded or required. You could pour in an infinite amount of money to add to the existing tool and get little or nothing in return.

If we purchased the perfect computer and software tool ones which would never have to be replaced, companies would go out of business. In fact they do not have to be perfect, as I know of companies who had such high quality products and leading edge technology that sales dropped off as the market place became saturated. No income – no company.

Capitalism and technology combine to make an interesting environment! :)

Tom





>Markus,
>
>I think it is more the issue of investing time in a development tool that is going to phase out within a few years anyway (no matter if you can combine those two technologies). Why not stick with what you´re doing now, and use the new advanced technology when it is mature and available.
>
>Really as I see it. Winforms are just an intermediate step. So why bother with that right now.
>
>Walter,
>
>
>
>>>
>>>>hmmm....some food for thought:
>>>>http://www.joelonsoftware.com/articles/APIWar.html
>>>
>>>And if you're developing a Windows GUI app today using Microsoft's "official" latest-and-greatest Windows programming environment, WinForms, you're going to have to start over again in two years to support Longhorn and Avalon. Which explains why WinForms is completely stillborn. Hope you haven't invested too much in it.
>>>
>>>Ouch.
>>
>>This is wrong.
>>
>>Avalon objects can be used in addition to WinForms objects. For instance, the following is possible:
>>
>>

// WinForm Form
>>public class MyForm : System.Windows.Forms.Form
>>{
>>   // ...
>>
>>   public void SomeMethod()
>>   {
>>      // Instantiate an Avalon form
>>      System.Windows.Window oWind = new System.Windows.Window();
>>      oWind.Show();
>>   }
>>}

>>
>>This makes an app that mixes WinForms and Avalon. It is pretty simple, really. For an existing WinForms app, Avalon simply represents a whole set of additional controls.
>>
>>WinForms is by far the best way to get ready for Avalon, for this very reason.
>>
>>Markus