Re: Vista problems




"Ed Dressel":>I am having serious problems with Vista. Can't figure out
why--I have my own
machine and everything works fine. But a couple of my users have problems
when opening my app in Vista.

On one machine, that I have logged onto remotely, it seems that at least
one of the file I install (a database file whose data is owned by us--is
not edited at all by the end user) does not get updated--it always
installes the old version. He has allowed me to delete everything that I
know how to--but when I install, the new EXE is there, and the old
database get's installed. (This sounds like I simply am losing it).



Sounds like a VirtualStore problem. Put a Vista section into
an XP manifest in your app. That will disable the VirtualStore.
You might get some errors but at least you'll have some hard
info to work with.

You probably need to put your database file in a writeable
location.

Here is an example of how to create and embed a manifest:


In Main unit:
{$R WinManifest.RES}


Command to compile the resource:
brcc32 WinManifest.rc


"WinManifest.rc" file contents:
1 24 "Win.Manifest"


"Win.Manifest" file contents:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
name="CompanyName.AppName"
processorArchitecture="x86"
version="1.0.0.0"
type="win32"
/>
<description>AppName</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="x86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker" uiAccess="false"/>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>


.



Relevant Pages

  • Re: Deployment under Vista
    ... Outlook apparently does not easily allow me step ... this app works perfectly under XP Home. ... The Install suggests putting the app where you set it to. ... you're breaking the Vista rules by putting data in a Program ...
    (microsoft.public.vb.general.discussion)
  • Re: Deployment under Vista
    ... The Install suggests putting the app where you set it to. ... you're breaking the Vista rules by putting data in a Program ... within the USER's folders. ...
    (microsoft.public.vb.general.discussion)
  • Re: Deployment under Vista
    ... combination of a special path designated by Windows and the current ... Consequently, under Vista CSIDLs were changed into KNOWNFOLDERIDs, ... Let's call my app Fred.exe and it uses say two random access files, ... The Install suggests that the app is placed in C:\Programs. ...
    (microsoft.public.vb.general.discussion)
  • Re: Deployment under Vista
    ... combination of a special path designated by Windows and the current ... Consequently, under Vista CSIDLs were changed into KNOWNFOLDERIDs, ... Let's call my app Fred.exe and it uses say two random access files, ... The Install suggests that the app is placed in C:\Programs. ...
    (microsoft.public.vb.general.discussion)
  • Re: Deploying Pocket PC Setup Applications (Vista Ultimate 64-bit
    ... I have similar problems with a very simple app on 32 bit Vista, ... I have had reports that my app does not install onto a Windows Vista ... My next thought was to simply install VS 2005 Pro onto my Vista Ultimate ...
    (microsoft.public.dotnet.framework.compactframework)