We moved our build server machine to a new machine. In the new build server, we have Installed the Installshield 2011 as the previous server. But in the new machine, the Install Shield wizard shows, the Install Shield Object is missing. If I try to register the objects, some of the objects are not properly mapped to the corresponding feature. They still show the missing icon.How to get rid of this?
There are multiple paths where the objects are kept.
Check in program files\installshield xx\Objects
Check in program files\Common files\installshield\objects
Copy your objects to these two folders and reopen the installshield. Try rebuilding the project.
Related
I need to work on Project Server using Microsoft.Office.Interop.MSProject.dll from Visual Studio.
Using gacutil.exe I have registered Microsoft.Office.Interop.MSProject.dll and at folder "C:\Windows\assembly" there is entry for MSProject.dll whose processor architecture is MSIL.
I have created Console Application and when I try to create Application instance it gives error:
Class not registered-HRESULT: 0x80040154 exception. As shown in image.
Target platform for this project is x86(32-bit). What could be the reason for the error?
Is it because office is not installed on local machine? Is there any alternative to using PIA without installing Office?
I have tried creating Project Add-in from Visual Studio, it works successfully, but it requires Project Professional to be open, which I want to avoid. Is it possible to avoid opening of Project Professional application in this case?
You need to have the Application (i.e. MS Project) installed on the PC. Interop files sre used for marshalling property or method calls from a managed code to the host application.
I am trying to use Monogame for the first time.
I found creating a content project is impossible on Visual Studio 2012,
so I would like to know if I can create some .xnb (contents) files from another PC and move it in my PC that Visual Studio 2012 is installed.
This is because I failed to install Windows Phone SDK in my PC for some reason.
My OS was Windows 7 so I could not install Windows Phone SDK.
So, is it possible to create a content project on another PC and move it into my PC? Or, can I copy the .xnb files to my PC?
Thanks in advance for your help.
You can create the xnb files from whichever system you want by using an XNA game project.
The steps to follow would be:
Create a new XNA Game project (it needs to be a game and not a content project).
Add the assets you want to port into the content project of the game.
Compile.
Go to the output folder and copy all the xnb files.
In your monogame project, add the existing xnb files to the project's Content folder.
Change their properties to: "Content" for "Build Action" and "Copy if newer" for output directory.
You can find a tutorial (written by me) explaining exactly how to use sounds and spritefonts in Monogame here. This can be helpful given that these files need to be created from an external project as Monogame was not able to used them without being in xnb format; and was also unable to create this format for itself.
One last thing, it is also possible to install XNA in VS 2012/2013 and Windows 8/8.1 without any problem by using XNA Refresh. This may help you in avoiding the need to use another computer for this process.
Using InstallShield LE with Visual Studio 2013, dev and target machines are Windows 7.
How do I create a folder under ProgramData and place a file in it? I have a text configuration file that I need to put there so the user can edit it as needed.
[I know this isn't a forum for ranting, so use your imagination to insert some nasty non-family-friendly comments about InstallShield here.]
InstallShield is a Windows Installer authoring tool. InstallShield rants aside, let's talk about the Windows Installer pain of what you are trying to do.
Installing per-user components is a pain. It requires a repair in each user context to populate the file. It's very ugly and has issues such as source resolution.
There is an easier way. Install a "seed" of the file in [ProgramFiles]Company\Product or [CommmonAppData]Company\Product and when the user runs your program copy the file to the users ProgramData if it does not exist.
This way you keep it simple for the installer, only add a few lines of code to your startup and don't have to worry about MSI trying to "fix" the user config file when the user edits the content because the installer doesn't know anything about it.
Easy, heh? Application design and Installer design have to go hand in hand.
Am trying to Deploy my visual studio 2012 vc++ application through Install Shield wizard.
The error am getting is :
Error 1324. The path .. contains an invalid character
I followed this tutorial and got succeed with a sample application .
http://www.flexerasoftware.com/webdocuments/productdemos/IS2010_VSLE_Demo/IS2010_VSLE_Demo-lite.html
But when i try to deploy my application, the setup file which i created is giving me this error.
Please help me
I've never seen this one before in the wild but it's described at:
http://support.microsoft.com/kb/292582
Basically it sounds like the computer has invalid data in the registry for one of the built in directories that Windows Installer resolves. It's an environmental issue rather then installer logic issue.
I'd have to see the installer log and computer registry to confirm or deny that though.
I had the same problem recently (with Installshield 2015). The problem was, that under Application Data/Files and Folders there was a definition for a folder called .. - so the setup would try to create a folder .. on the target system, which of course doesn't work.
Deleting that folder definition and moving its contained files to the parent folder definition fixed the problem for me.
I have a setup which has been created using InstallScript MSI project type. This problem is encountered by our client and he wants a quick solution.
Let's assume I have initiated the installation from a path like
C:\Setup_V_1.0.0931.1
Inside this folder I have Setup.exe through which I will install the product. After installation or after some days pass I will change the path to:
C:\New\Setup_V_1.0.0931.1
and this time I want to modify the setup. Actually we are supporting 3 features: Server, Client and Service.
This time I want only Client and not Server. So I will click on the Setup.exe or click on Uninstallation Icon in the Startup Menu which will lead to Maintenance Mode there you have an option to Modify, Repair or Remove. I choose Modify and select the feature, but as the installation progresses, this error message will pop up:
Setup could not find a file on the specified path or Disk. Please check
that the proper disk is inserted or specify a new path. Unable to
locate file c:\New\Setup_V_1.0.0931.1\setup.msi
Then, another popup will be shown saying:
Error: 1706. No Valid Source could be found for product. The Windows
Installer cannot continue.
The next error message is:
Error: 1603. Fatal error during installation. Consult Windows Installer
Help (Msi.chm) or MSDN for more information.
But if I change the path to its original location, it works fine.
How can I solve this?
I event checked in this registry path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\{Product-Key}
This key contains a lot of information inside InstallProperties. There is a key called InstallSource and its value is C:\Setup_V_1.0.3909.1\. Even after changing this value installshiled is still showing errors.
I found the same registry information for Uninstallation Information:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Product-Key}
In your properties change ReinstallMode (or maybe Reinstall I forget which) from omus to vomus
the v means cache your install, so it will put your .msi file in c:\windows\installer so it can be used later.
When installing a MSI, Windows Installer saves the original MSI path in registry (the InstallSource entry you mentioned). When running the MSI in maintenance mode, Windows Installer will use this path to find the installation data (CAB files).
When you move the MSI, the path stored in registry is no longer valid, so Windows Installer cannot find the installation data.
A possible solution is to use "Add or Remove Programs" or "Programs and Features" in Control Panel to modify the installation. This way the cached MSI is used.