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

[ddn123456]

Hi All, I manifested all files below.

• "\Perl\bin\perl.exe"
• "\Perl\bin\perl5.8.6.exe"
• "\Perl\bin\perlglob.exe"
• "\Perl\bin\wperl.exe"

• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\lib\netcheck.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\lib\pai.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\lib\pai_icons.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\lib\pdkcheck.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\lib\pdklib.dll"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\lib\perl58.dll"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\lib\scineplex.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\lib\tkkit.dll"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\lib\vbsperlui.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\lib\vpmd.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\pdkdebug.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\perlapp.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\perlctrl.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\PerlDB.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\perlfb.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\PerlNH60.dll"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\perlsvc.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\perltray.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\plc.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\vbsperl.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\bin\vpm.exe"
• "\Program Files\ActiveState Perl Dev Kit 6.0\lib\auto\MSI\Util\Util.dll"
• "\Program Files\ActiveState Perl Dev Kit 6.0\lib\auto\Win32\Cabinet\Cabinet.dll"

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

[ddn123456]

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