Now, that we have a certificate, we can inform the certificate to have the final MSIX package file automatically signed. It is not necessary to provide the installer file, as the tool monitors all changes made to the operating system.
In this step, it is necessary to provide information such as the name of the package, the description that will be displayed to the user during installation, the name of the supplier must be the same as the certificate and the version number. Fill in the requested information:. As we already have the VB3 installed, this is the moment to moving back the emulator and VB3 folders to the drive C root:.
Click on the Next button only after completing the application installation and all settings. On the next screen it is necessary to define which applications will be visible in the start menu.
As VB3 is a bit application that depends on the bit emulator, select only the otvdm. Notice that is not possible to provide the arguments for the otvdm. For now, we can ignore the arguments as we are fix that later. The following screen is displayed at the end of the installation and asks for confirmation if the monitoring can be ended:. At this point, it is necessary to inform where the package will be generated, as well as it is possible to edit the package before saving it.
It is possible to edit the manifest information, such as processor architecture, application description, minimum supported version of Windows 10 and others.
The only problem here, is that is no possible to pass arguments in this manifest file. We will now create an execution alias to allow launching the application by typing or calling the VB. EXE command from anywhere. Click on Package files and check if all the files and directories listed are used by the application. It is at this step that we need to add the Package Support Framework files, to allow the PsfLauncher The id corresponds to the Application Id defined in the application manifest, the executable contains the emulator path inside the package and the arguments the VB3 path inside the package.
In the Package file tab, right click on Package folder and click on. Click on the Create button to generate the package and inform where the file should be generated.
You can now launch the application directly from Start menu or typing vb. You must be a registered user to add a comment. I found this website that will allow you to download the full. ISO images of CC3 so you can reinstall the software if you have the valid serial. MSI file I created is linked to by product key so technically I would have to recreate the. MSI file with your key. Since part of the process is to create the.
MSI file, it uses whatever you have typed in during the install process. If you have Windows 7 bit which is the system I am currently using, you could just load up the Windows XP Mode which is free from Microsoft and allows you to use Creatacard Gold 3 just fine under Windows 7. Hopefully this helps some. I will keep this website in my list so I can check back if you update again. Mail will not be published. Subscribe in a reader. Delivered by FeedBurner. About Contact.
August 18, at pm. Facebook 0 Tweet 0 Pin 0 Print 0. Subscribe Subscribe in a reader. Enter your email address: Delivered by FeedBurner. Remove From My Forums. Asked by:. Archived Forums. General Windows Desktop Development Issues. Sign in to vote. Anyone any ideas why this is happening? Monday, June 23, AM. Hi, I am afraid that here is not the correct forum for this issue.
I found it to be very fast and stable and i didn't have any problems with it so far Today I've tried to install one of our applications it is bit onto my win7 laptop and I worked! And this is why I am writing this post: I am confused: if there is no support for bit applications in Windows 7, then how it is possible there are wowexec and ntvdm???
Maybe I am wrong and there is the bit support? Any ideas will be highly appreciated! Thursday, May 14, PM.
0コメント