difxapp and VisualStudio - step for step?
Hello,
I build a lot of small msi-packages with the setup-project-tools from Visual Studio 2005. But now, I have to deploy a driver for a USB-Device.
So, I found the difxapp-Mergemodule an read a lot here, but nothing that helped me out.
Is there a step-for-step-tutorial (in best case with pictures, the buttons in the German Version are named totally different as in the english Version)
any help is welcome :)
Regards
Daniel
I build a lot of small msi-packages with the setup-project-tools from Visual Studio 2005. But now, I have to deploy a driver for a USB-Device.
So, I found the difxapp-Mergemodule an read a lot here, but nothing that helped me out.
Is there a step-for-step-tutorial (in best case with pictures, the buttons in the German Version are named totally different as in the english Version)
any help is welcome :)
Regards
Daniel
0 Comments
[ + ] Show comments
Answers (11)
Please log in to answer
Posted by:
cygan
15 years ago
Posted by:
captain_planet
15 years ago
Posted by:
anonymous_9363
15 years ago
Posted by:
Daniel26
15 years ago
Posted by:
cygan
15 years ago
Posted by:
cygan
15 years ago
@ Captain_Planet: The first Problem: How do I create a component? Can't find that in the GErman Version. Or do you mean a Setup-Project as a component?
And how do I set the Inf-File as Keypath?
hi daniel from what I can see I think you are better off using dpinst
capture the your setup.exe ie using wise / installshield
and then use dpinst.exe to install your drivers ie .inf file using a custom action
I can show you how to go about it.
using the merge module difxapp can be a pain sometimes
this is just a suggestion go with what you are comfortable with
cheers
Posted by:
Daniel26
15 years ago
I tried dpinst from the commandline, but it don't work (in Vista x86).
Oh, sorry: It worked....but only one time.
After the dpinst I pluged in the device, and then the Driver-Installation-Assistent comes up and asked me where to search for the driver.
But I don't want this behavior.
Waht I want: The user gets a CD with the Hardware, puts in the CD before plugs in the device, installes the application and the drivers.
Then, he plugs in the device via USB, and the device is working. No driver-assistent.
Can I do this with difxapp?
But, to learn a little bit: Can you explain me what you mean with "component" and how do I create this? And how do I set the file as keypath?
Regards
Daniel
Oh, sorry: It worked....but only one time.
After the dpinst I pluged in the device, and then the Driver-Installation-Assistent comes up and asked me where to search for the driver.
But I don't want this behavior.
Waht I want: The user gets a CD with the Hardware, puts in the CD before plugs in the device, installes the application and the drivers.
Then, he plugs in the device via USB, and the device is working. No driver-assistent.
Can I do this with difxapp?
But, to learn a little bit: Can you explain me what you mean with "component" and how do I create this? And how do I set the file as keypath?
Regards
Daniel
Posted by:
cygan
15 years ago
But, to learn a little bit: Can you explain me what you mean with "component" and how do I create this? And how do I set the file as keypath?
have a look at this http://www.symantec.com/connect/articles/how-package-signed-device-driver-using-wise-package-studio
Posted by:
Daniel26
15 years ago
Posted by:
cygan
15 years ago
Posted by:
anonymous_9363
15 years ago
VS is not a packaging tool. Get yourself (or have you employer get for you) a proper tool. Although there are two main players, Wise/Altiris and InstallShield, there are doubts about the future of the Wise product line (or, more correctly, whether it will ever properly support up-to-date OSs in anything like a reasonable time-frame), now that they are owned by Symantec. I say this as a long-term Wise user and as someone who regards it as being - in general - the better product (no flames please).
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.