Re: Trying to be 'well behaved' under Vista

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Wed, 4 Oct 2006 15:42:01 -0700, Dan Ritchie
<DanRitchie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Saddly, Microsoft hasn't learned from history. There have been OS's in the
past that have blatantly stated they would break applications that don't 100%
conform to the recommended guidlines for Software developement. The result
was usually mass migration of developers to other systems. Lets face it,
even Microsoft themselves don't adhear to any guidelines all that strictly,
or if they do, they change their minds on what the guidelines are a few
months later. Microsoft has left thousands upon thousands of developers up
the creek without a paddle this time, and that kind of thing can't go on
forever. Maybe, just maybe, the beginning of the end for them. Does anyone
here remember when Bell had the monopoly on telephone service?

Too true, pretty much every 3-5 years they make changes 'for the better'
and lose a few users that just want to stay with what they have that
works how they want it now. I know people that refuse to migrate to XP
and still use W2K or Win98, and even some that moved to Linux or Macs.
I'm still coding in VB6 because I have no compelling reason (or the
time) to re-write my codebase in .NET, although I am now learning c/c++
as an alternative.

The problem is that the reasons for change actually appear quite good,
and for 'well behaved' apps there will be minimal issues. MS came out
with this standard when they released W2K, it has just not previously
been enforced by the OS.

As the OP asked how to be 'well behaved' under Vista, it's not that
difficult to follow the MS standard, and stands less chance of being
invalidated later on (most current MS products use this standard
anyway), particularly if MS choose to close it down further and not let
executables install/run in My Documents or Application Data (which is
where I've heard several people propose to install the whole App).
--
Alfie
<http://www.delphia.co.uk/>
Crush your enemies, see them driven before you, and hear the lamentation of their women.

.

Relevant Pages

  • Re: Forth Frustrations
    ... called microFORTH, in the late 70's, primarily aimed at the hobbyist market. ... The big difference is that Forth83 was developed in only two 3-day meetings, 6 months apart, with somewhat differing membership, informal rules, and no official sanctioning body such as ANSI. ... The developers met 4 times a year, a total of 16 meeting days/year, in various parts of the country encouraging local Forthers to attend and voice their opinions. ... There were 4 drafts published for public review, and the standard was adopted in 1994 only after there were no more substantive changes resulting from the last review period. ...
    (comp.lang.forth)
  • Re: Member Variables Naming Convention
    ... you get some people saying "developers should be free to express ... I also believe that using industry standards (i.e. the naming convention ... all the work of writing the standard docs and publishing them and maintaining ... "Dave Sexton" wrote: ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Cant find String functions.... Missing library
    ... Merge modules provide a standard method by which developers deliver shared ... Windows Installer components and setup logic to their applications. ...
    (microsoft.public.excel.programming)
  • Re: Secure C library
    ... >> Then come to the meetings and help clean it up. ... >>>of C and probably won't actually do much to make software more secure. ... stuff into the standard. ... >developers and managers start doing jail time. ...
    (comp.std.c)
  • Re: Whats the story with the "end of XP"?
    ... Thats what all the linux guys say. ... OpenBSD on my Internet-facing servers since about '99. ... the OpenBSD developers set the gold ... it's standard stuff. ...
    (comp.arch.embedded)