The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Don't use that phrasing when talking with Linux affectionados! As if a command line interface is not a "user interface"
You still edit the .wxs file (the main input file, identifying files and components and all the other stuff describing which pieces to put together in which way, and other red tape such as which user dialog style to user, product IDs etc.) in a textual format (XML), but all the rest is usually handled well by Visual Studio. You don't have to care about that crowd of individual Wix tools; when you build your solution, VS will take care of the building steps of Wix as well. There is no sort of graphic interface for putting your system together like with Lego blocks (if that is what you were hoping for).
I was an active Wix user several years ago, subscribing to the mailing lists and eagerly reading the blogs of the developers (at WiX Toolset[^]).
I see only two issues with WiX: First, it has got (almost) all the functionality you could dream of, but does it really have to be that complex? You've got two options, either the very naive, simplistic use where VS handles everything for you, or you have to accept the full complexity with a crowd of individual tools and a hundred call line options, "Linux style" in the worst possible sense. You just got to keep that 450 page book handy at all times... (and be aware in which parts the book is outdated).
Second, and this is a non-issue if you think it is perfectly OK to fill up your machine with all sorts of obsolete software. Between three and four years ago, I did a major cleanup of about twenty build agents, installing only tools in actual use, updating tools to new versions, to clean out .NET 2.x and 3.x (and a lot of other obsolete stuff). WiX 3.x requires .NET 3.x, which pulls 2.x along, so we decided to go for WiX 4, based on .NET 4, even though it was not yet released, and no VS integration was available. Sure, WiX 4 itself does not need obsolete .NET versions, but the installer package for WiX 4 itself (probably made with WiX 3) needs it! The WiX development team didn't believe me when I reported this, not until I mailed a full log from everything from Windows reinstallation on a newly formatted disk to the WiX installer complaints.
So I was promised a new release that would fix this. It didn't. Nor did the second attempt. Then I gave up, accepted that I had to maintain a .NET version released in 2006 for a single reason: To install WiX. Then we might as well use WiX 3, first released in 2009 (the Windows XP days), to keeping the VS integration intact, while waiting for WiX 4.
Six years after WiX 4 development started, it still is in the "real soon now" stage - but you can no longer download any pre-release from the web site. It states "WiX Toolset v4.x reference manual (coming soon)", but who would trust that after six years of ... nothing useful. The WiX blog of the main developer, Rob Mensching, has had a single entry for more than a year, where he states: "Completing WiX v4 is at the top of my list." Yeah, I guess that is true, but it no longer matters to me. I'm no longer waiting for Godot. I consider WiX dead software, just like .NET 2.x - you have to keep it on your machine because someone needs it.
Maybe WiX 4 will come one day, 12-15 years after WiX 3 was released. In that time span, software development has changed so much that I expect WiX 4 to be like a completely new product, not a simple version upgrade. It is guaranteed to have incompatibilities, and many fancy new possibilities that it takes a lot of resources to learn to use. Switching to WiX 4 must be judged against switching to any other installer generator - at some time into the future when it arrives. You can't even read the documentation for it today.
So, go ahead and used WiX 3.11 (the current stable version) with VS integration. But consider it stale software, dead, with no bright future ahead. If any WiX has a future, it is WiX 4. But that's another, future product that is not available today.
Rule #1 of using third party packages.
1. You must make it work with what is currently supported
2. Never trust anyone else's "ship date"
Flashback to a module I used during the 16bit to 32bit transitions.
I had to write a 16bit service to process requests from 32bit applications.
It seemed backwards to me, but that was the only way the APIs would let you do it.
The promised 32bit version never shipped over a 1 year span of promises!
Maybe it shipped after I left that position.
Thank goodness the 16bit Intel architecture is no longer relevant to Windows.
There are probably similar problems with 32bit and 64bit, but I have not had to dive into anything like that for a long time.
Yes, I have used it (and paid for it regrettably). Didn't like the product or the company. I settled on WiX Toolset, it takes a little extra effort to learn but your installer can then be pure "you" when you create your own bootstrapper.
I gave up on InstallShield years ago. I wrote programs to generate the complex install scripts, but it didn't do everything I needed to do. Then I found Visual Installer Visual & Installer[^] which does everything I need to have done. I still use a program to generate the code, but the program does the entire build for a CD or download installation. Visual Installer works very well for me.
If you want cheap, try the open-source WiX for authoring installers. I use it for work and like it way better than InstallShield. It's not hard to use unless you need to do something unusual (since you mentioned InstallShield Express, i suspect not).
Lenovo's website wasn't cooperating. Best to match the model (M8/M10) to its case.
I see no reason why a Xamarin Forms app shouldn't run on an Android device. BTW, I use Xamarin to build native Android apps. I (and an iOS colleague) built a pretty complex dual platform tablet app about 4 years ago when Xamarin Forms debuted. It worked very well at the time and I'm sure the platform's only improved with age.
I suppose it's to keep with what they already have & use, but I though the Android Tablet was being sent to the 'care home' as there has not been an OS update for sometime and the only upgrades that were out there company (Samsung, I'm looking at you!) mods & patches for specific models. I was think the only Tablet being supported was the iPads...
Yeah, so effin' what? Show me the content that used to be there.
"Check the Microsoft Product Lifecycle page for information about how this product, service, technology or API is supported".
No, just show me the page that used to be there. It existed at one point. I don't care that you no longer support the product.
I understand Microsoft's desire to move its documentation to "better" (ahem) systems over time, but what would it cost them to leave older pages exactly where they are? It's like what's no longer current no longer exists. Or they're trying their best to pretend it never existed in the first place. Enough with this already.
Even the old MSDN archive CDs were better than this.
Try one of the many links to an MSDN blog which are "in the wild". The content is archived but still there, so you'd think they'd redirect you to the archived version, right?
Wrong. They redirect you to the "Archived MSDN and TechNet Blogs" page[^], with a list of letters to select the first name of the blog you were looking for. You then have to search through multiple pages of the blogs starting with that letter to find the blog you want, and then search through the archived posts from that blog to find the post you were looking for.
It's not rocket science. All they had to do was redirect:
What you can do to get around this is... We're no longer updating this content regularly.
Check our Product Lifecycle page for information about how this product, service, technology or API is supported.