in reply to How can I integrate within the PDK perlapp the manifest assembly workaround for Vista UAC?

Hi All, I manifested all files below.


The PDK could no longer launch after being manifested so fallback to none-manifested binaries.
After fallback of PDK only, the compilation with PDK went fine.

At execution however the problem remains.

Summarised. I did not manage to launch a manifested-PDK-created-executable as a parent process within the "asInvoker" security context thus executing other none-manifested executables. The manifested subprocesses within the same context did run fine however.

I see something similar happening with a manifested-perl.exe launching a script. Similar impression is mentioned at <Ahref="http://aspn.activestate.com/ASPN/Mail/Message/pdk/3396900">RE: Win32::Msg

I have posted this on the ActiveState PDK Support forum

Many thanks to all who provided me with their valuable insights.

With kind regards.

DDN
  • Comment on Re: How can I integrate within the PDK perlapp the manifest assembly workaround for Vista UAC?

Replies are listed 'Best First'.
Re^2: How can I integrate within the PDK perlapp the manifest assembly workaround for Vista UAC?
by ddn123456 (Pilgrim) on Aug 02, 2007 at 12:52 UTC
    Dear PerlMonks, Following quote from Mark Minasi at link: WindowsITpro Article 96375 explains this behaviour.

    "Or what about the small-but-essential fact that adding an external manifest to a legacy program in hopes of solving a User Account Control compatibility problem works sometimes but not always, thanks to a glitch in the disk-caching algorithm?"

    I guess we'll just have to wait praying that the next Vista Service Pack solves this issue.

    Regards.
    DDN123456
[reply]

In Section Seekers of Perl Wisdom