5 ms·
Try C++/CLI :) Had that problem recently when I assumed .NET was installed, but it needed a separate C++ runtime for C++/CLI
by NKCSS 10y ago
Try C++/CLI :) Had that problem recently when I assumed .NET was installed, but it needed a separate C++ runtime for C++/CLI
- tonyedgecombe 10y agoI think I'll skip that :) One of the reasons I switched to C# was to move away from C++.
- jsmeaton 10y agoShipping c++ redistributable libraries is a major PITA. I couldn't figure out how to bundle them with a clickonce or wix installer.
- NKCSS 10y agoIt's not just that; everything feels old and fragile when you mess with C++(/CLI); I was amazed I had to write a stupid post-build event just to copy the app.config to the build dir... why is the experience so different from when you use C#? When doing .NET stuff, it would be nice if those things would be the same.
- kohanz 10y agoI did this once at a previous job. Was able to bundle all of the installers (including C++ redistributable, driver updates, etc.) into a single installer that ran off a single click, first in a Setup & Deployment project and then ported to Wix. It wasn't fun, but once it worked it saved us a ton of headaches in the field.
- snuxoll 10y agoI really need to figure out an easy way to bundle the C++ redist's with Wix myself, I've got a PowerShell module I've packaged up along with a MSM containing a vendor SDK it uses. Problem is, said SDK has native components so the VC++2015 runtime also needs to be installed. I deploy this using Ansible anyway so I am able to just install the C++ runtime separately, but it's a huge pain when I want someone to be able to double click an MSI on their developer machine and have it not work.
- jsmeaton 10y agoThat was basically my situation. My project was c# but a vendor exe packaged with it required c++ libs. Never figured out how to bundle it.
- deleted 10y ago[deleted]