I saw one thread on this in the archives with no response. So, I figured the time may be ripe to ask again.
I have an installation for a web site that is working really well so far except for this one little snag. I've plumbed everything in for the site I install to use https except for the certificate which - for security reasons - is already installed on the box by someone else. The install runs fine, but the web site doesn't work until I go into IIS and goose the authentication (or the binding if I'm in IIS 7) to attach it to the certificate. I've been trundling though the 3.0 docs for the IIS extensions and I've seen the Certificate and CertificateRef elements. I tried to be cute with these to see if I could define a Certificate with just the required attributes (Name, StoreLocation, and StoreName). I was hoping that would be enough to point the MSI in the direction of the existing certificate. But alas, the compiler barked at me for not having either BinaryKey or CertificatePath defined. So, my question is: Is there something I'm missing or perhaps a workaround to this situation? Thanks - Rich Daniel ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
