Comments on: Highlander Field Test - Apply Here http://blogs.codegear.com/chrispattinson/2007/06/28/36584 CodeGear QA Manager for RAD Studio products Thu, 20 Nov 2008 07:33:48 +0000 http://wordpress.org/?v=2.6.2 By: Chris Pattinson http://blogs.codegear.com/chrispattinson/2007/06/28/36584#comment-76 Chris Pattinson Fri, 29 Jun 2007 11:20:51 +0000 http://blogs.codegear.com/chrispattinson/2007/06/28/36287/#comment-76 The simple answer: We are no longer supporting Winforms in Highlander. <br> <br>As to the why? <br> <br>There is a fair amount of discussion in the thread in borland.public.delphi.non-technical on the subject. <br> <br>I suggest the thread started here: <br> <br>From: "Roland" <beensoft@yahoo.com> <br>Subject: How can you drop Winforms support? <br>Date: Fri, 22 Jun 2007 11:04:45 +0100 <br> <br>Allen Bauer posted some insight into the 'why': <br>"While the core WinForm designer isn't specifically tied to VS, most of <br>the services on which it depends are provided by VS. It is the <br>myraid of these services that we've had to maintain and keep in sync. <br>There is very little documentation on a lot of this so we're forced to <br>"fly by the seat of our pants." " <br> <br>Basically the cost of maintenance and redoing VS work was preventing us focusing on Delphi and C++, which statistically is still our largest user base. This was one of the factors in being able to do our Unicode and 64 bit work earlier (and some would say - better). <br> <br> The simple answer: We are no longer supporting Winforms in Highlander.

As to the why?

There is a fair amount of discussion in the thread in borland.public.delphi.non-technical on the subject.

I suggest the thread started here:

From: "Roland" <beensoft@yahoo.com>

Subject: How can you drop Winforms support?

Date: Fri, 22 Jun 2007 11:04:45 +0100

Allen Bauer posted some insight into the ‘why’:

"While the core WinForm designer isn’t specifically tied to VS, most of

the services on which it depends are provided by VS. It is the

myraid of these services that we’ve had to maintain and keep in sync.

There is very little documentation on a lot of this so we’re forced to

"fly by the seat of our pants." "

Basically the cost of maintenance and redoing VS work was preventing us focusing on Delphi and C++, which statistically is still our largest user base. This was one of the factors in being able to do our Unicode and 64 bit work earlier (and some would say - better).

]]> By: Ilse http://blogs.codegear.com/chrispattinson/2007/06/28/36584#comment-39 Ilse Fri, 29 Jun 2007 07:05:27 +0000 http://blogs.codegear.com/chrispattinson/2007/06/28/36287/#comment-39 "Among the topics of interest are the changes to Winforms." <br> <br>Boy this is getting confusing: will we get winforms or not? "Among the topics of interest are the changes to Winforms."

Boy this is getting confusing: will we get winforms or not?

]]> By: lee galileo http://blogs.codegear.com/chrispattinson/2007/06/28/36584#comment-23 lee galileo Fri, 29 Jun 2007 00:20:52 +0000 http://blogs.codegear.com/chrispattinson/2007/06/28/36287/#comment-23 Is C#Builder alive ? I would like C#Builder more than others. Is C#Builder alive ? I would like C#Builder more than others.

]]> By: Steve Hodgkiss http://blogs.codegear.com/chrispattinson/2007/06/28/36584#comment-47 Steve Hodgkiss Thu, 28 Jun 2007 16:15:44 +0000 http://blogs.codegear.com/chrispattinson/2007/06/28/36287/#comment-47 I want to be involved in any way possible to preview and give feedback on .NET support for Delphi. <br> <br> I want to be involved in any way possible to preview and give feedback on .NET support for Delphi.

]]>