Updated from 3.6u2 to 3.7u3 and Vixen crashes on Windows 7 with Visual Styles disabled
Attaching logs to help. There was one wierd thing: My system 'updated' .NET framework 3.7.2 during the initial install, and then when I tried (after reboot) running Vixen it said .NET 3.8 wasn't there (of course) and then I had to install it. One wierd 'some process crashed' happened during this time, but I am not sure that is related to .NET or not, since the installation claimed it finished successfully. Then the Vixen crashing started upon the next reboot. What's going on? Thanks for taking a look at this.
I looked at this and I can modify the control we are using for the progress bar to gracefully degrade on systems that visual styles are not supported. It is a simple one line fix, so I don't have any problems making it to help in this case.
We have officially dropped support for Win 7 earlier this year when Microsoft did. As Jon mentioned we cannot hitch ourselves to outdated technology. There was nothing deliberate done to break it, but I think that the new progress bar used to show the startup progress is likely the component that is causing it. I will look at that and see if there is something obvious there that could restore it easily, but I am not intent on any significant work. Be aware there are other things like the vendor browser for custom props that does not work due to the outdated TLS support in Win 7. There may be other things I am not aware of because we don't test on that platform any longer.
Thanks Jon, for the extra info. I appreciate your perspective. It's mostly that, for me, having to rebuild and learn a new OS is a pain, and especially MS loves to do way more than a true OS should, and gets more bulky and unmanageable every time. The also love to continually hide, remove and change all the features that us power users and developers use and appreciate. I am sure you are aware of this phenomenon.
Take care and Happy Holidays!
Every year, we update the Vixen codebase to use the newest (stable) .net framework available at the time. With these new versions, we almost always benefit from new code efficiencies. Sometimes by quite a bit. And as we do these framework upgrades, we occasionally will drop support for the older OSes. It’s not that we’re choosing to drop them, but rather because Microsoft (and other libraries) drops support in the frameworks. It’s increasingly difficult to continue to get bigger and better while still maintaining support for outdated systems. I’m pretty sure that this year’s version dropped win7 support, but Jeff would have to confirm that.
Thanks for responding and offering the other user's solution.
Allowing "Use Visual Styles on Windows and Buttons" (no other Visual Effects checked) works. Yes, this is a Win 7 machine.
Question is, why did 3.6 versions not care about this and now in 3.7 they do? Did you have to use some code which required it? I would hope not, as you want (I presume) an optimized code that saves as much compute power for the core Vixen functions, not 'Window and button effects,' right? I would guess that .NET does not require usage of these effects, or it would not be an option in Windows itself. If possible, I would remove anything like this, not only to prevent errors and frustration, but also to keep the code as compatible with as many Windows versions as possible (please never stop supporting Win 7, even though M$ is...)
Thanks again for the help! (gotta finish my show, and get it running; people are asking about it!)