Hello!

After having viewed the latest .NET show from msdn.microsoft.com I was

inspired by firing up the windes.exe proggy to do some simple win32 gui

design. I don't have the VS.NET beta yet, so this is all I had available.



Knowing it was still alpha software I loaded, it quickly became obvious that

the designer was really slow to work with. Everything responded very slow

when adding/drawing buttons/labels etc. and dragging the sliders for the

property-windows was very slow too (when compared to a normal

slider-response time for e.g. the directory explorer).



How come? Is this due to the JIT or the CLR itself? Is the system.winforms

namespace really that slow? It sort of reminded my of the slow java

applications I've seen. Definately not the speed of normal win32

applications we're used to.



Is the windes.exe designer written on top of the .NET framework too? If yes,

it's not that promising I think =)



with regards

anders lundholm · lundholm@s...

the sphereworx / monoliner experience

--

The VS.NET beta is not publicly available yet.  So noone outside of

Microsoft has that.



Anyone who has used the Alpha release, has noticed the same slowness 

that

you refer to.  I believe that this is specifically because it is an 

Alpha

product that was slapped together for the PDC.  It is doubtful that any

optimization has been done and some of it (if not all) is probably 

debug

releases.  You probably also noticed that the IDE required 1 Gigabyte 

of

space.  I doubt that will be the case in the final product.



If you build an application using the IDE and compile it, you will not 

see

the slow response time that you are seeing within the IDE.



-----Original Message-----

From: Anders Lundholm [mailto:lundholm@s...]

Sent: Wednesday, November 01, 2000 9:59 AM

To: ASP+

Subject: [aspx] Dissapointed by .NET speed (windes.exe)





Hello!

After having viewed the latest .NET show from msdn.microsoft.com I was

inspired by firing up the windes.exe proggy to do some simple win32 gui

design. I don't have the VS.NET beta yet, so this is all I had 

available.



Knowing it was still alpha software I loaded, it quickly became obvious 

that

the designer was really slow to work with. Everything responded very 

slow

when adding/drawing buttons/labels etc. and dragging the sliders for 

the

property-windows was very slow too (when compared to a normal

slider-response time for e.g. the directory explorer).



How come? Is this due to the JIT or the CLR itself? Is the 

system.winforms

namespace really that slow? It sort of reminded my of the slow java

applications I've seen. Definately not the speed of normal win32

applications we're used to.



Is the windes.exe designer written on top of the .NET framework too? If 

yes,

it's not that promising I think =3D)



with regards

anders lundholm =B7 lundholm@s...

the sphereworx / monoliner experience

--