How to create manifest for non .net application

[DBC User]

Sorry for off topic here. I would like to know will it be possible to
create a manifest for non .net application? I have a program created
with VC 2.1 and Install Sheild as well. I want those two programs to
require admin privileges to run in vista. I know I can do it in VS
2005 by adding additional manifest during building. How can I do it
for the other apps?

Thanks.

 

[Willy Denoyette [MVP]]

Sorry for off topic here. I would like to know will it be possible to
create a manifest for non .net application? I have a program created
with VC 2.1 and Install Sheild as well. I want those two programs to
require admin privileges to run in vista. I know I can do it in VS
2005 by adding additional manifest during building. How can I do it
for the other apps?

Thanks.

The mt.exe tool (....\VC\bin\mt.exe), can be used to embed a manifest file
in an existing exe.

mt.exe -manifest SomeProgram.exe.manifest -outputresource:SomeProgram.exe;#1

Willy.

 

[Doug Semler]

Sorry for off topic here. I would like to know will it be possible to
create a manifest for non .net application? I have a program created
with VC 2.1 and Install Sheild as well. I want those two programs to
require admin privileges to run in vista. I know I can do it in VS
2005 by adding additional manifest during building. How can I do it
for the other apps?

Heh, I had to do this recently on a vb6 app that needed to run on a 64 bit
machine (requirement imposed: installing components outside of given
directories NOT permitted). Basically I did it by hand: in order to get the
right COM object dependencies, I just created a quick stub application and
dropped the same COM components (and there were ALOT of them) that the VB6
app uses into a form and marked them isolated. Then I just copied manually
made the changes I needed to the the manifest that was generated over to the
vb6.exe.manifest file and poof it worked.

--
Doug Semler, MCPD
a.a. #705, BAAWA. EAC Guardian of the Horn of the IPU (pbuhh).
The answer is 42; DNRC o-
Gur Hfrarg unf orpbzr fb shyy bs penc gurfr qnlf, abbar rira
erpbtavmrf fvzcyr guvatf yvxr ebg13 nalzber. Fnq, vfa'g vg?

 

[DBC User]

Heh, I had to do this recently on a vb6 app that needed to run on a 64 bit
machine (requirement imposed: installing components outside of given
directories NOT permitted). Basically I did it by hand: in order to get the
right COM object dependencies, I just created a quick stub application and
dropped the same COM components (and there were ALOT of them) that the VB6
app uses into a form and marked them isolated. Then I just copied manually
made the changes I needed to the the manifest that was generated over to the
vb6.exe.manifest file and poof it worked.

--
Doug Semler, MCPD
a.a. #705, BAAWA. EAC Guardian of the Horn of the IPU (pbuhh).
The answer is 42; DNRC o-
Gur Hfrarg unf orpbzr fb shyy bs penc gurfr qnlf, abbar rira
erpbtavmrf fvzcyr guvatf yvxr ebg13 nalzber. Fnq, vfa'g vg?

Thanks both. This will help me get started..