> -----Original Message----- > From: nejiba [mailto:nejiba.ta...@gmail.com] > Sent: Monday, June 25, 2012 09:26 > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] custom action with administrator privileges > > Re > I was following the tutorial here: > http://www.codeproject.com/KB/library/driver-install-with-wix.aspx > The command usind DPinst.exe works and shows me the message "the > driver was successfully installed" but my case is a little more specific.. the > device still not working and my computer cannot detect it. I think that the > command wdreg do more things than simply installing the driver (add > register key > ....) > In this case I must use the cmd command or is there an other alternative? > Thanks!
That's because DPInst is the wrong tool for the job. Use DIFxApp extension. DPInst is not really supported or intended for use with Windows Installer. The fact that this article has 18 votes and is rated 4.96 stars out of 5 speaks very poorly about the knowledge level of people at Code Project. My experience is that Code Project has many articles that have key errors or omissions, or takes a fundamentally flawed approach (e.g. use of undocumented behavior when it's not needed), but still gets a high ranking/vote because it "just works". I suspect the site is frequented by developers who are just looking for code to copy and paste to get it to work on their local system, who don't care what the code is actually doing, and who don't care about how well the resulting product will actually work, whether it will be maintainable, whether it will work when faced with new versions of Windows and various 3rd-party programs installed, whether it will fail when faced with certain edge conditions, etc. I still read Code Project articles - many of them do have useful information and can help point me in the right direction when trying to learn from MSDN documentation. But I read them over with a very critical eye - I think about whether there are simpler, better supported ways of doing what the author is doing. And I always revise all code used from there, and carefully check each line of code for bugs, and check it against official documentation to be sure that various API calls, etc. are being made properly. In short, I don't use any code from there without a careful code review. I have seen many cases where the Code Project author reinvents the wheel, when a simple API call could have sufficed. This is one of those cases. If you look at the end of the page, there are some comments: "I do have one question. How is doing it using the DPInst different from using the that is part of the DifxAppExtension for WiX?" The author's response: "DifxApp can cause difficulties if you want to create one version of the installer both for x32 and x64 platforms. From the other side, DifxApp allows to handle driver installation rollbacks in much easier way. I must say that the main reason is that I have much more experience in using DPInst than DifxApp." So he decided to use the incorrect, unsupported way just because he "has more experience with DPInst"? Because he was unable to figure out one of the many possible solutions to making an MSI with DIFxApp that can work on both 32-bit and 64-bit Windows? At the same time, he admits his solution doesn't handle one of the key Windows Installer features - rollback. Apparently he's afraid of learning something new, so he tried to reinvent the wheel and did it poorly. Sad. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
