On 02-Sep-10 06:13, Pally Sandher wrote: > I have personally fixed things like that myself. Last year one of our dev's > decided to implement the use of CAPICOM for some basic password encryption& > MD5 checking& thought it was OK to tell me "just self-register the CAPICOM > DLL in the installer& it'll work". He was also recommending we use an > out-dated version of the discontinued CAPICOM containing some known security > vulnerabilities. I re-wrote his code using the CryptoAPI completely removing > the need for the CAPICOM redistributable. Incidentally he no longer works for > us any more. > > When the product developers make stupid decisions which impact upon setup > development, call them on it or be prepared to put up with more of the same > until the end of time.
This is why it's important for "setup developers" to be developers in their own right, so they can speak with authority and, when necessary, write code outside of setup to "lend a hand." -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
