Test Case 13 for Vista Certification

Test Case 13 for Vista Certification

• MrCRM

  That dash problem occurs when you copy the command from

  the MSDN help web site as I just did!

  http://msdn2.microsoft.com/en-us/library/bb756929.aspx

  
  
  

• Ready4u

  If your installation is an setup exe it needs to be a bootstrapper or chainer.
  
  Bootstappers are an exe that will install pre-reqs and then call your msi. The msi maybe external to the bootstrapper exe or it may be embedded in the bootstrapper. If embedded in the bootstapper, the msi is extracted to a temp folder location and then installed.

  Chainer is similar to bootstrapper, it an exe that extracts all the MSIs required. Then it calls the primary MSI which will chain the other MSIs together.
  
  The "non-self containing" means the bootstrapper is external. An example of a containing bootstrapper is it's possible for an MSI to contain the bootstrapper and another MSI. Therefore the bootstrapper is contained. A contained bootstrapper exe is not tested for a manifest and a non-self contained bootstrapper is tested for a manifest. The common approach I see is to have a non-self containing bootstrapper.

  Let me know if you have more questions.

  
  
  

• Hamez

  I just had this same problem too, though I'm running all US / English. There is no way I typed in the wrong kind of hyphen, but had copied it from a project post-build event window.

  
  
  

• gudel

  Dear Friedrich B

  May you please tell me how do you do that

  
  
  

• MartinParé

  No.

  We decided to skip the exe and ship only the msi.

  
  

• Latso

  I get the same error when adding the manifest with MT.exe running under Vista (business), non admin mode, UAC enabled. Version of MT.EXE is 6.0.4071.0, exact error message is as follows:
  
  mt.exe:command line error c10100a8:No manifest outputs were specified to store the final manifest.
  Use the / option for help on usage and samples.
  
  If I run as a standard user on XP, the command runs fine. Command line used:
  mt -manifest test.manifest outputresource:VersionUpdate.exe;#1
  
  VersionUpdate.exe is a .NET 2.0 command line program.
  Using Visual Studio SP1 + Vista patches.
  
  I think this is a problem that you (Microsoft) need to fix.
  
  
  
  
  

• MrBogomips

  I got the same error. The reason is quite simple the second minus is not a minus! I guess that we copied the text form the same site or something.

  Use "-outputresource" instead of "–outputresource".

  Soren

  
  

• itsRashmi

  Thanks for pointing the solution out. That dash before outputresource is wrong. Two points worth attention:
  
  1) This problem is common. The project my company is working on also have this problem. It's not a coincident. I believe that line was generated by Visual Studio.
  
  2) I am the first person in my company who faced this problem. The reason is that if one uses English as the OS default language, he/she won't have the problem, even if the wrong dash is used. Only if the user's system OS uses a multibyte language, like Chinese or Korean, the difference of two dashes will take effect.
  
  

• Mike737Aviator

  So if I understand this requirement correctly we have to embed a manifest in our setup.exe created through build of a Visual Studio setup project.

  Is this correct

  I have tried to do this as a post build step:

  "C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin\mt.exe" -manifest "$(ProjectDir)setup.exe.manifest" –outputresource:"$(ProjectDir)$(Configuration)\setup.exe;1"

  However, I get the following error:

  mt.exe : command line error c10100a8: No manifest outputs were specified to store the final manifest.

  Does anyone spot any errors in the mt.exe call

  Thanks,

  Markus

  
  

• Jon Watte

  Did you find some way to get rid of this error

  I get the same error message as you.

  
  
• Test Case 13 for Vista Certification