You're always welcome, Robert.
All the best,
Catalin
Find out more ›
Thank you for providing these details. I am pretty sure this will be of help for investigating the root cause of this issue.- Installed VS 2015 and VS 2017
- the solution is now in VS2017 and had been imported from a previous VS2015 Project.
This was fixed in 15.8 version of Advanced Installer, released on March 20th, 2019.Daniel wrote: ↑Mon Feb 18, 2019 1:25 pmHello John,
Thank you for your valuable feedback. Indeed it seems our application fails to import a SLN when VS 2017 and VS 2019 are installed side by side.
We will try to add a fix for this issue in a future version of Advanced Installer, thank you for helping us to isolate this. As soon as a fix is out we will update this thread.
All the best,
Daniel