You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need help using UMMM. My situation is this:
I just have a very simple network communication app I'm making but it uses MSWINSCK.ocx (which isn't installed by default in Windows). I need to be able to use my app portably (even from a jumpdrive) which means I can't create an installer for MSWINSCK.ocx to install it on end-users' PCs. I need to do this manifest technique. There's no .net components, just my program's EXE file "TCP Communicator.exe" (and yes, it does have a space in its name, not sure of UMMM can handle this), and the one OCX dependency which is MSWINSCK.ocx. I'm not sure which ini command to use in the ini file here. Should I use File or Dependency? And then, what command line should I type at the prompt to run UMMM? Do I need to include the name of the DLL file in the UMMM command line, or just the name of the ini file that UMMM is going to process?
The text was updated successfully, but these errors were encountered:
Use File. Dependency would only be used on a .NET dll that is being adapted for use in your program, which you have stated you do not have. The command would be something like UMMM.exe path/to/my/ini/file.ini "TCP Communicator.exe.manfiest" I believe. This will create an external manifest file. I don't remember if there are specific options to embed it in the exe itself. There should be usage information by just calling UMMM.exe. Just experiment.
I've used UMMM for other third party dependencies, including some from Microsoft, though not MSWINSCK in particular. Use the 'File' command in your INI settings. Should work fine.
I need help using UMMM. My situation is this:
I just have a very simple network communication app I'm making but it uses MSWINSCK.ocx (which isn't installed by default in Windows). I need to be able to use my app portably (even from a jumpdrive) which means I can't create an installer for MSWINSCK.ocx to install it on end-users' PCs. I need to do this manifest technique. There's no .net components, just my program's EXE file "TCP Communicator.exe" (and yes, it does have a space in its name, not sure of UMMM can handle this), and the one OCX dependency which is MSWINSCK.ocx. I'm not sure which ini command to use in the ini file here. Should I use File or Dependency? And then, what command line should I type at the prompt to run UMMM? Do I need to include the name of the DLL file in the UMMM command line, or just the name of the ini file that UMMM is going to process?
The text was updated successfully, but these errors were encountered: