yag: Community and Architecture

PingBack from http://www.universityupdate.com/Technology/Windows-Vista/5401197.aspx

Will it take a fix in Vista SP1 to correct this?

YAG,

I tend to agree with you that it is not a VFP or SP2 issue, as it can be reproduced in nearly any programming language.  I have one app that I have "inherited", that was setting the borderstyle property to 2 in the init, to make it easier for the previous developer to resize the form in the designer.  It is, however, an issue that apparently many developers are facing, and I'm just curious how much of a security issue changing the borderstyle of a form at runtime could be?  What possible security breaches could be exposed by making a window resizable or not?

Just curious.

I tend to agree with you that it is not a VFP or SP2 issue, as it can be reproduced in nearly any programming language.  I have one app that I have "inherited", that was setting the borderstyle property to 2 in the init, to make it easier for the previous developer to resize the form in the designer.  It is, however, an issue that apparently many developers are facing, and I'm just curious how much of a security issue changing the borderstyle of a form at runtime could be?  What possible security breaches could be exposed by making a window resizable or not?

http://blogs.msdn.com/ericgu/archive/2007/10/19/moving-from-write-no-tests-to-tdd.aspx http://blogs.msdn.com/yag/archive/2007/10/31/windows-vista-border-issue-and-sp2.aspx http://blogs.msdn.com/jim_glass/archive/2007/10/31/tap-tap-tap.aspx http://blogs.msdn.com/tzink/archive/2007/10/31/the-advantages-of-being-a-pm.aspx..

Yag,

if this is an issue that comes by design of windows vista there are are (only) two possible things ms can do to deal with is: 1) Change the behaviour in vista  

or

2) fix the applications to be "vista aware".  In the case of vfp this would possibly mean that vfp detects that it runs under vista and just simply ignores the borderstyle change. Anything like that. Producing graphic fragments on the screen is not what i'd understand as "dealing" with an definitly existing problem and does imho not make vfp vista-capable - which was a goal to achive with sp2 ("works with vista") .

Please think of the position we as developers are in now - we promised our customers that those problems would be gone soon and they could switch to vista if they asked for it. And now we have to admid that it's a problem with vista that probably never is going to be fixed. The first answer from our customers will be: "but i don't have a similar problem with other applications i use - it can't be a vista problem". so you leave it again to us, yag. please think of it.

regards

Pen

I did a lot of complaining when SP2 came out, because my apps were a mess under SP2 and Vista. Now that I know the whole thing was caused by changing BorderStyle in the Init, I'm much less concerned. That was done as a convenience for the developer and I can't think of any other reason I need to change it at runtime. So as far as I am concerned, case closed. Maybe you could add a "known issues" section in the list of fixes that accompanies SP2.

Any idea how to prevent a form from beeing resized conditionally without changing the borderstyle?

regards

Hey YAG, we're on time...

http://www.itworld.com/Comp/2296/071114leopardmauls/index.html