Does anyone know if there are any WiX standard UI dialouges out there that you can use to integrate into your own WiX msi package?
For example:
Editing Connection Strings to database
Editing paths to log files in web.config/app.config
Setting up users for a Windows Service
Setting up WCF Endpoint addresses and other parameters
This would be very helpful!
I've haven't seen any UI dialog package either.
WixEdit has a dialog editor which I've heard is pretty useful, but I haven't used.
War Setup is a pretty good utility. It's been about a year since I've used it, so I don't remember if it has a dialog editor or not.
Edit: I couldn't think of the one I really loved, but I just found it: WixAware. It has probably the best dialog editor. The only thing is that it's trialware and the full version is $800.
Not today no. They aren't that hard to write though.
Related
I am trying to create a Modalless dialog in my exsisting project. CDialog::Create cause debug assertion. I tried a new Dialog based application and followed the same steps, the dialog gets created without any error.
Also in my exsisiting project I am using MFC as static Library, can this affect the functionality?
really looking forward for any helpful replies
Best Regards
Well this is just a stab in the dark given the vagueness and lack of information in the question, but have you created the dialog as a WS_CHILD and not WS_POPUP?
I'm a .NET Developer trying my hand at an application on OS X. MonoMac makes so many things easy for me. I've managed to write an application useful to myself using just the MonoMac posts people have done and the Apple Developer documentation.
I can't seem to find out how to actually associate a file extension to my application. I believe this needs to be done via Launch Services or maybe add something to the Info.plist in my project.
Any hints, code or how tos?
Read this guidelines on Runtime Configuration from Apple: http://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPRuntimeConfig/000-Introduction/introduction.html as pointed by this answer: How to associate a specified type of file with my program?
Does anyone know of a complete, downloadable/copyable example of a WiX installer that allows the user to select an existing website when installing a web application?
I'm trying to get this working and, after seeing that it seems to be a significant piece of work, I'd like to get an example running first so that I have a working project to base my own work on.
I found this (code is pasted as images) and this (can't get it running).
Just to confirm... Is it really as much work as the sites above suggest to allow a user to select the site to install to? Am I missing a trick?
I found this blog post that does the custom action in C# and has a complete downloadable sample. Pretty easy to follow.
Yes, that would be quite a bit of work to do it in WiX. I don't typically give a user this much choice. You might just want to do it as an after install configuration step if it's important to you.
I am looking into a way of setting read access on a specific file for a web application (where all files read option is set to be false--unchecked in IIS) deployed with Wix. Is it a possible option at all or I am asking the question in a wrong way?
Thank you.
That level of granularity is not supported by the WiX toolset's IIS custom actions today. It'd be cool if someone implemented it and contributed back to the community.
Our application commonly used an ActiveX control to download and install our client on IE (XP and prior), however as our user base has drifted towards more Vista boxes with "Protected Mode" on, we are required to investigate.
So going forward, is it worth the headache of trying to use the protected mode API? Is this going to result in a deluge of dialog boxes and admin rights to do the things our app needs to do (write to some local file places, access some other applications, etc)?
I'm half bent on just adding a non-browser based installer app that will do the dirty work of downloading and installing the client, if need be... this would only need to be installed once and in large corporate structures it could be pushed out by IT.
Are there some other ideas I'm missing?
This client, is it a desktop application and not some software that runs inside the browser? In that case, please just supply a regular download installer application. My personal experience with browser-hosted installers is that they are just confusing and the few I have seen seemed to be poorly coded in some way.
If you use an MSI based installer I'm sure lots of Windows domain administrators will love you too, as Microsoft has tools to deploy MSI based installations onto large sets of machines remotely.
Its far better to do this right than put it off any longer. Vista is Microsoft's way of saying they aren't letting people get away with ignoring security issues any more and encouraging people to update their code.
I'm sure other users here will be able to point you are some MSDN best practices about writing ActiveX controls.
Have you checked out Microsoft's ClickOnce Deployment?
If I remember correctly you can embed a manifests which would help with dealing with protected modes automatically, saving you those headaches with the APIs.
I believe ClickOnce is geared for the same thing your ActiveX installer was designed to do.
Since you say your IT dept could push this out, I assume you could use this kind of technology as well.
Even though you might not be writing applications on the .NET CLR, you can use Visual Studio to generate those manifest and installers for you.