#827: standalone-installer: execution failed on g.proj.exe -p ---------------------------+------------------------------------------------ Reporter: timmie | Owner: [email protected] Type: defect | Status: new Priority: normal | Milestone: 6.4.0 Component: Installation | Version: svn-releasebranch64 Resolution: | Keywords: wingrass Platform: MSWindows XP | Cpu: x86-32 ---------------------------+------------------------------------------------ Comment (by hellik):
Replying to [comment:21 glynn]: > > We're already faced with having to create manifests to keep UAC happy, so it would be useful if someone could read up on this stuff and figure out how to use manifests to control searching for DLLs. maybe this information is helpfull: http://msdn.microsoft.com/de-de/library/aa375365%28en-us,VS.85%29.aspx * Assembly manifests describe side-by-side assemblies. They are used to manage the names, versions, resources, and dependent assemblies of side-by-side assemblies. The manifests of shared assemblies are stored in the WinSxS folder of the system. Private assembly manifests are stored either as a resource in the DLL or in the application folder * Application manifests describe isolated applications. They are used to manage the names and versions of shared side-by-side assemblies that the application should bind to at run time. Application manifests are copied into the same folder as the application executable file or included as a resource in the application's executable file. * Application Configuration Files, are manifests used to override and redirect the versions of dependent assemblies used by side-by-side assemblies and applications. * Publisher Configuration Files, are manifests used to redirect the version of a side-by-side assembly to another compatible version. The version that the assembly is being redirected to should have the same major.minor values as the original version. Helmut -- Ticket URL: <http://trac.osgeo.org/grass/ticket/827#comment:24> GRASS GIS <http://grass.osgeo.org>
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
