Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General Discussion » View Thread |
Messages 1 to 10 of 11 total |
Please, advice on deploying on Vista/7 systems |
Fri, Dec 18 2009 4:16 AM | Permanent Link |
Tiago Ameller | Until now, I used to deploy my apps in this way: (SSC stands for my company logo)
Main application: x:\SSC\<appname> Shared bpls and dlls: %winsys% DBISAM data in one machine installations: x:\SSC\<appname>\DATA ... User private config, DBISAM private dir: x:\SSC\<appname>\<username>\PRIVDIR In order to avoid problems with Vista and 7, I'll change this (despite I don't like Microsoft suggestions) to Main application: %programfiles%\SSC\<appname> Shared bpls and dlls: %programfiles%\%commonfiles%\SSC\SHARED DBISAM data in one machine installations: %userprofile% or %allusersprofile%\%programdata%\SSC\<appid> User private config, DBISAM private dir: %userprofile%\SSC\<appname>\PRIVDIR I don't like it due data and app are in different locations. I affraid people will backup app but not data when formating their disk Any suggestions? How are you doing it? Thanks to all! |
Fri, Dec 18 2009 5:38 AM | Permanent Link |
"Iztok Lajovic" | Tiego,
I don't like Microsoft's suggestions either. I use the same directory structure as you are used to and I have no problems with this directory structure using Vista and Windows 7. In your case I should preserve old approach. Iztok Lajovic "Tiago Ameller" <tiago@sistemasc.net> je napisal v sporočilo news:2DE00C96-EF7A-4868-8742-4E36A3B43D40@news.elevatesoft.com ... > Until now, I used to deploy my apps in this way: (SSC stands for my > company logo) > > Main application: x:\SSC\<appname> > Shared bpls and dlls: %winsys% > DBISAM data in one machine installations: x:\SSC\<appname>\DATA ... > User private config, DBISAM private dir: > x:\SSC\<appname>\<username>\PRIVDIR > > In order to avoid problems with Vista and 7, I'll change this (despite I > don't like Microsoft suggestions) to > > Main application: %programfiles%\SSC\<appname> > Shared bpls and dlls: %programfiles%\%commonfiles%\SSC\SHARED > DBISAM data in one machine installations: %userprofile% or > %allusersprofile%\%programdata%\SSC\<appid> > User private config, DBISAM private dir: > %userprofile%\SSC\<appname>\PRIVDIR > > I don't like it due data and app are in different locations. I affraid > people will backup app but not data when formating their disk > > Any suggestions? How are you doing it? > > Thanks to all! > |
Fri, Dec 18 2009 6:02 AM | Permanent Link |
Tiago Ameller | Iztok Lajovic,
Thanks for your advice. Currently: Old approach 1 New approach 0 Any other opinion? |
Fri, Dec 18 2009 6:57 AM | Permanent Link |
"Malcolm" | OK, just to even up the score.
I decided to make the switch nearly two years ago for my DBISAM apps and have stayed that way for EDB. So I install the program and read-only recources to {program files}\MyCo\MyApp and the data and user editable files to {commonappdata}\MyCo\MyApp. I have no shared DLLs, etc. I have not had any trouble doing this. I have used {commonappdata} as my apps can run alone or in shared data mode so the user-specific locations are not suitable. HTH -- |
Fri, Dec 18 2009 7:05 AM | Permanent Link |
Tiago Ameller | Thanks, Malcom:
Old: 1 New: 1 Have you realized AV software has less false positives against app and data when it's located on these "normalized" folders? |
Fri, Dec 18 2009 8:10 AM | Permanent Link |
"Malcolm" | Tiago Ameller wrote:
> Thanks, Malcom: > Have you realized AV software has less false positives against app > and data when it's located on these "normalized" folders? I never noticed. I have not had any reports of false positives so I have no data on the subject. -- |
Fri, Dec 18 2009 11:04 AM | Permanent Link |
"Daniel Kram" | I'll offer another suggestion, from the old days.
Over the years, I grew tired of Microsoft moving things around, creating the documents folder, data folder, etc. So I decided to just create a folder off of the root of C:\ or the %system_drive% - yes, you may need Administrator to do this the first time, but after this, I can play in my own sandbox and never have to worry about where things are. In my sandbox, I have a multitude of folders for various items, but basically, exe and associated files are in one, data in another. Neat, simple, easy. This works with an installation application too, just direct it to the system drive folder instead of the Program Files folder. Daniel |
Fri, Dec 18 2009 12:11 PM | Permanent Link |
Tiago Ameller | Daniel,
<I'll offer another suggestion, from the old days.> Not bad idea, just the opposite M$ wants Old: 2 New: 1 |
Sun, Dec 20 2009 5:13 PM | Permanent Link |
"Adam H." | + 1 for this idea too. For single machine applications, I normally put
my data in the root directory (for the users who are happy with this) and change the permissions so I too have my own sandbox. There have been the odd occasions where I've put both my data and application in the program files directory (changing the permissions on the new folder I create within the program files directory) to make things a little neater. I haven't had any issues with this as long as I set the permissions correctly on 'my' folder. Cheers Adam. |
Mon, Dec 21 2009 10:44 AM | Permanent Link |
Tiago Ameller | Adam,
Old: 3 New: 1 We have a winner! Thanks to all for share your suggestions with us. |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Friday, March 29, 2024 at 03:30 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |