18
апр
Delphi 2007 Vista Uac
Posted:admin
Wednesday, February 28, 2007. UAC in the Oven I just noticed that Aleksander Oven, a honorable member of Delphi-SI community is blogging. Too bad - the series on Vista UAC and Delphi was very useful. Reply Delete. Yes, i've been looking for something good on that topic for a while. Reply Delete.
There is an APP i help work on, that was made for XP and only XP, and years of development work in it and few thousand people using it. This was started before I got there, and call from higher ups to be this way.Well the call came down, to make things UAC happy as possible with Vista / Win7 Finally.I can tell you that the app is located in program files.It writes ini and BDE db files with in its directory its installed in program files. (app was made YEARS before I started so no turning back on design).It updates/creates the registry data for a ODBC SystemDSN entry (no user interaction for this is key).It creates log files and some data export files within some directories with in the install folder.I've been reading up on UAC, Digital signed Certifications, Manifests, ect. On 11:00 PM, steven chesser wrote: Basically other then keeping with D7, what all does it take to make it so no UAC pop up comes up without turning UAC off. Is there a way to make it so Run As Administrator in the shortcut doesn't have to be checked on. And not have to rewrite tons and tons and tons of code.You must modify the application to store settings and data in locationsthat a limited user account can access. Anything else requires UACoff or gives an UAC elevation prompt.One way:In your installer create a directory under FOLDERIDProgramData(set the permissions so MACHINENAME/USERS or some othergroup that includes all the users who need access can read/write/modify.
Use that folder to store data files.Brian. On 2010-04-20 11:00 PM, steven chesser wrote: There is an APP i help work on, that was made for XP and only XP, and years of development work in it and few thousand people using it. Download psychonauts highly compressed. This was started before I got there, and call from higher ups to be this way. Well the call came down, to make things UAC happy as possible with Vista / Win7 Finally.I have recently learned to rely upon an approach I call the 'scratchpadapproach'. I have two working copies of my source code.
The stableversion, and the does-not-remain-stable version.Within the unstable version, remove the BDE, or whatever else it is,that is your biggest overall software headache. Now you will beprompted, line by line, as you try to rebuild, showing youwhere things are broken.I have used this approach to design abstract base classes thatcontain the interfaces that each part of my application needs,so that there can be ZERO coupling between IMPLEMENTATIONS,and the only coupling that exists is between the interfacesI define. Just because I said 'interfaces', does not meanI started using reference-counted 'Interface' types. In mydesigns, I generally use only abstract base classes to definethe abstract design of my system. I call that an interface,but if you like, call it your 'set of abstract base classes'.To make your classes abstract you do this:TDataWriterBase = class(TSomething)protectedfunction GetIdentity:String; virtual; abstract;publicprocedure GetData; virtual; abstract;procedure SetData; virtual; abstract.publishedproperty Identity:String read GetIdentity;end;Everything in the class is virtual; abstract;, or a property declarationthat really is just sugar coating a protected propertyget method, which is also abstract. There are no data fields(FCounter:Integer) or anything else in my abstract base classes.Pay no attention to my names for my methods.
Its up to you to definethese methods.At the same time as dropping the BDE, and maybe going to somethingmore modern, like dbExpress, you should consider dropping the delphihabit of having one giant mudball of source code.What I found, three months into one such cleanup, was that I had todrop my unstable version, and go back to maintain the mudball again.But eventually, when shipping versions of your code are relativelyproblem free, you can spend more time on your future-friendlyarchitecture. While you're being more blue sky, you can considermaking the big architectural changes that have always made you afraid.Fear of doing something can keep you alive, in business terms, but itcan also put you out of business, if you delay long enough. The key isto keep delivering your stable product, and building your 'great'product, incrementally, in parallel.:-)W.
Wednesday, February 28, 2007. UAC in the Oven I just noticed that Aleksander Oven, a honorable member of Delphi-SI community is blogging. Too bad - the series on Vista UAC and Delphi was very useful. Reply Delete. Yes, i\'ve been looking for something good on that topic for a while. Reply Delete.
There is an APP i help work on, that was made for XP and only XP, and years of development work in it and few thousand people using it. This was started before I got there, and call from higher ups to be this way.Well the call came down, to make things UAC happy as possible with Vista / Win7 Finally.I can tell you that the app is located in program files.It writes ini and BDE db files with in its directory its installed in program files. (app was made YEARS before I started so no turning back on design).It updates/creates the registry data for a ODBC SystemDSN entry (no user interaction for this is key).It creates log files and some data export files within some directories with in the install folder.I\'ve been reading up on UAC, Digital signed Certifications, Manifests, ect. On 11:00 PM, steven chesser wrote: Basically other then keeping with D7, what all does it take to make it so no UAC pop up comes up without turning UAC off. Is there a way to make it so Run As Administrator in the shortcut doesn\'t have to be checked on. And not have to rewrite tons and tons and tons of code.You must modify the application to store settings and data in locationsthat a limited user account can access. Anything else requires UACoff or gives an UAC elevation prompt.One way:In your installer create a directory under FOLDERIDProgramData(set the permissions so MACHINENAME/USERS or some othergroup that includes all the users who need access can read/write/modify.
Use that folder to store data files.Brian. On 2010-04-20 11:00 PM, steven chesser wrote: There is an APP i help work on, that was made for XP and only XP, and years of development work in it and few thousand people using it. Download psychonauts highly compressed. This was started before I got there, and call from higher ups to be this way. Well the call came down, to make things UAC happy as possible with Vista / Win7 Finally.I have recently learned to rely upon an approach I call the \'scratchpadapproach\'. I have two working copies of my source code.
The stableversion, and the does-not-remain-stable version.Within the unstable version, remove the BDE, or whatever else it is,that is your biggest overall software headache. Now you will beprompted, line by line, as you try to rebuild, showing youwhere things are broken.I have used this approach to design abstract base classes thatcontain the interfaces that each part of my application needs,so that there can be ZERO coupling between IMPLEMENTATIONS,and the only coupling that exists is between the interfacesI define. Just because I said \'interfaces\', does not meanI started using reference-counted \'Interface\' types. In mydesigns, I generally use only abstract base classes to definethe abstract design of my system. I call that an interface,but if you like, call it your \'set of abstract base classes\'.To make your classes abstract you do this:TDataWriterBase = class(TSomething)protectedfunction GetIdentity:String; virtual; abstract;publicprocedure GetData; virtual; abstract;procedure SetData; virtual; abstract.publishedproperty Identity:String read GetIdentity;end;Everything in the class is virtual; abstract;, or a property declarationthat really is just sugar coating a protected propertyget method, which is also abstract. There are no data fields(FCounter:Integer) or anything else in my abstract base classes.Pay no attention to my names for my methods.
Its up to you to definethese methods.At the same time as dropping the BDE, and maybe going to somethingmore modern, like dbExpress, you should consider dropping the delphihabit of having one giant mudball of source code.What I found, three months into one such cleanup, was that I had todrop my unstable version, and go back to maintain the mudball again.But eventually, when shipping versions of your code are relativelyproblem free, you can spend more time on your future-friendlyarchitecture. While you\'re being more blue sky, you can considermaking the big architectural changes that have always made you afraid.Fear of doing something can keep you alive, in business terms, but itcan also put you out of business, if you delay long enough. The key isto keep delivering your stable product, and building your \'great\'product, incrementally, in parallel.:-)W.
...'>Delphi 2007 Vista Uac(18.04.2020)Wednesday, February 28, 2007. UAC in the Oven I just noticed that Aleksander Oven, a honorable member of Delphi-SI community is blogging. Too bad - the series on Vista UAC and Delphi was very useful. Reply Delete. Yes, i\'ve been looking for something good on that topic for a while. Reply Delete.
There is an APP i help work on, that was made for XP and only XP, and years of development work in it and few thousand people using it. This was started before I got there, and call from higher ups to be this way.Well the call came down, to make things UAC happy as possible with Vista / Win7 Finally.I can tell you that the app is located in program files.It writes ini and BDE db files with in its directory its installed in program files. (app was made YEARS before I started so no turning back on design).It updates/creates the registry data for a ODBC SystemDSN entry (no user interaction for this is key).It creates log files and some data export files within some directories with in the install folder.I\'ve been reading up on UAC, Digital signed Certifications, Manifests, ect. On 11:00 PM, steven chesser wrote: Basically other then keeping with D7, what all does it take to make it so no UAC pop up comes up without turning UAC off. Is there a way to make it so Run As Administrator in the shortcut doesn\'t have to be checked on. And not have to rewrite tons and tons and tons of code.You must modify the application to store settings and data in locationsthat a limited user account can access. Anything else requires UACoff or gives an UAC elevation prompt.One way:In your installer create a directory under FOLDERIDProgramData(set the permissions so MACHINENAME/USERS or some othergroup that includes all the users who need access can read/write/modify.
Use that folder to store data files.Brian. On 2010-04-20 11:00 PM, steven chesser wrote: There is an APP i help work on, that was made for XP and only XP, and years of development work in it and few thousand people using it. Download psychonauts highly compressed. This was started before I got there, and call from higher ups to be this way. Well the call came down, to make things UAC happy as possible with Vista / Win7 Finally.I have recently learned to rely upon an approach I call the \'scratchpadapproach\'. I have two working copies of my source code.
The stableversion, and the does-not-remain-stable version.Within the unstable version, remove the BDE, or whatever else it is,that is your biggest overall software headache. Now you will beprompted, line by line, as you try to rebuild, showing youwhere things are broken.I have used this approach to design abstract base classes thatcontain the interfaces that each part of my application needs,so that there can be ZERO coupling between IMPLEMENTATIONS,and the only coupling that exists is between the interfacesI define. Just because I said \'interfaces\', does not meanI started using reference-counted \'Interface\' types. In mydesigns, I generally use only abstract base classes to definethe abstract design of my system. I call that an interface,but if you like, call it your \'set of abstract base classes\'.To make your classes abstract you do this:TDataWriterBase = class(TSomething)protectedfunction GetIdentity:String; virtual; abstract;publicprocedure GetData; virtual; abstract;procedure SetData; virtual; abstract.publishedproperty Identity:String read GetIdentity;end;Everything in the class is virtual; abstract;, or a property declarationthat really is just sugar coating a protected propertyget method, which is also abstract. There are no data fields(FCounter:Integer) or anything else in my abstract base classes.Pay no attention to my names for my methods.
Its up to you to definethese methods.At the same time as dropping the BDE, and maybe going to somethingmore modern, like dbExpress, you should consider dropping the delphihabit of having one giant mudball of source code.What I found, three months into one such cleanup, was that I had todrop my unstable version, and go back to maintain the mudball again.But eventually, when shipping versions of your code are relativelyproblem free, you can spend more time on your future-friendlyarchitecture. While you\'re being more blue sky, you can considermaking the big architectural changes that have always made you afraid.Fear of doing something can keep you alive, in business terms, but itcan also put you out of business, if you delay long enough. The key isto keep delivering your stable product, and building your \'great\'product, incrementally, in parallel.:-)W.
...'>Delphi 2007 Vista Uac(18.04.2020)New Posts
© 2020 Delphi 2007 Vista Uac.