vb.net deployment
-
I have developed a windows applicatio using vb.net as MS Access.I have created a setup program using the package and deploymnet wizard.But I am not able to install it on a system with Windows ME OS.I can install it on Windows XP and Wndows 2000.What could be the problem?The OS I use is Windows 2000.Can anyone help me.Thanks in advance.
What do you mean by 'you are not able to install it' ? It won't install ? It won't run ? Is the .NET framework installed on this machine ? Christian Graus - Microsoft MVP - C++
-
What do you mean by 'you are not able to install it' ? It won't install ? It won't run ? Is the .NET framework installed on this machine ? Christian Graus - Microsoft MVP - C++
-
dot net framework is installed in the target machine.not able to install means i cud not able to run the setup program in windows ME.
An installer can be created to target specific machines - perhaps your installer thinks it is only for 2000/XP ? What happens, do you get an error ? A crash ? Nothing happens ? Christian Graus - Microsoft MVP - C++
-
dot net framework is installed in the target machine.not able to install means i cud not able to run the setup program in windows ME.
Post an error message. I believe that ME requires ANSI setups built like a Win98 setup. Win2K, XP and 2003 definitely use Unicode. This may be part of youre problem.
-
An installer can be created to target specific machines - perhaps your installer thinks it is only for 2000/XP ? What happens, do you get an error ? A crash ? Nothing happens ? Christian Graus - Microsoft MVP - C++
-
when I double click the windows installer file An Open With Dialog box is opened and I am not sure how to proceed from there.Please help.
Ah - the lights come on. You need to install the msi installer itself, ME does not know what to do with an msi file otherwise. Christian Graus - Microsoft MVP - C++
-
when I double click the windows installer file An Open With Dialog box is opened and I am not sure how to proceed from there.Please help.
Windows ME is supposed to have the Windows Installer service installed as part of the OS. The Net Framework installation is also supposed to install the Windows Installer service if it is not present. No Windows Installer service on ME may mean a corrupt Windows install, but the dotnetfx should fix at least the installer service. Are you bootstrapping the dotnetfx setup in your setup package?
-
Ah - the lights come on. You need to install the msi installer itself, ME does not know what to do with an msi file otherwise. Christian Graus - Microsoft MVP - C++
-
Could you please help me on how to go about this.(Install the msi installer)I mean explain a bit going step by step.Thanx in advance
There are two Windows Installer setups named InstMsiA.exe and InstMsiW.exe for ansi and unicode respectively. You just find and run the correct program for the OS - I think MsiA is correct for ME but I'm not positive. Running this will do everything to install Windows Installer. That still does not answer why the dot net framework setup did not install the same components that InstMSI installs. You may need to search the Microsoft site to see if there are known bugs associated with installing the dot nmet framework and/or the Windows Installer on ME systems.
-
There are two Windows Installer setups named InstMsiA.exe and InstMsiW.exe for ansi and unicode respectively. You just find and run the correct program for the OS - I think MsiA is correct for ME but I'm not positive. Running this will do everything to install Windows Installer. That still does not answer why the dot net framework setup did not install the same components that InstMSI installs. You may need to search the Microsoft site to see if there are known bugs associated with installing the dot nmet framework and/or the Windows Installer on ME systems.
-
It sounds like the Windows Installer service is either missing files or one or more of the files has been corrupted. Unfortunately there is not a repair switch for InstMSI. It could just be a missing file type registration or a path registration problem too. Try running an install from the commandline. Find msiexec.exe - it should be in the Windows system folder. If you can find that, try running any msi from the commandline using "C:\\msiexec.exe" /i "\yourmsi.msi" and see if it works from the commandline.
-
Ah - the lights come on. You need to install the msi installer itself, ME does not know what to do with an msi file otherwise. Christian Graus - Microsoft MVP - C++
Could you please provide me with a detailed instructions on how to go about this(to install the msi installer itself, ME does not know what to do with an msi file otherwise.) or provide some links where I can get this information .I am quite new to VB.Net.Thanks so much for your help
-
Could you please provide me with a detailed instructions on how to go about this(to install the msi installer itself, ME does not know what to do with an msi file otherwise.) or provide some links where I can get this information .I am quite new to VB.Net.Thanks so much for your help
I can't really add to what the other person has said. If the MSI installer claims it's already here, you need to figure out a way to repair the install. Christian Graus - Microsoft MVP - C++
-
Could you please provide me with a detailed instructions on how to go about this(to install the msi installer itself, ME does not know what to do with an msi file otherwise.) or provide some links where I can get this information .I am quite new to VB.Net.Thanks so much for your help
Again, unless there is some sort of bug that is specific to Windows ME, and I know very little about Windows ME, at this point about all I know of to suggest is to re-install Windows. You've tried running InstMSI, and it said it was already installed. I assume you've installed the dotnetfx.exe, and that also installs the Windows Installer if it is not present or not the correct version. Since your Windows seems to think the Windows Installer is there, it should at least recognize an msi file even if the msi file is corrupt or not compatible. Since it does not the only thing I can assume is that your Windows Installer service is corrupted somehow, and I know of no way to repair it other than a complete OS reinstall. Sorry I cannot be more helpful.