J
Jsytniak
Guest
VS 2015 just stopped working for me. Behavior was... splash screen... then stops. Google searches show it is not an uncommon problem and there were lots of various suggested fixes. I tried lots of the suggested fixes... my head was spinning.
Cutting to the chase.... See if you at some time added the machine.config setting… legacyCasPolicy. If so, comment it out or turn it off. Now try VS 2015.
The back story....
A couple weeks back, I began working on a bug in a legacy Windows Forms application. The app is pretty old stuff… was originally built with VS 2008. I upgraded it to VS 2010 about 7 years ago.
I needed to locate the form that triggered the offending buggy logic and the best way was to get a look at likely form candidates was using the form designer. I discovered that the VS 2010 form designer had issues with the DevExpress ActiveX control suite that the app’s forms contained. I wrestled with VS 2010 before discovering a workaround… this machine.config setting….legacyCasPolicy. Now… this setting was no panacea. It presented some flaky behavior in VS 2010. When toggled on, I could use the forms designer, but could not get anything to build. When off, I could build, but not view anything in designer. Plus... when toggling the setting…. this also involved stopping/starting VS 2010. Ok… clunky… but manageable.
Fast forward 10 days or so... and now I need to open another solution in VS 2015 to check on something. This when I discover VS 2015 is doing the splash then nothing thing. The odyssey begins of literally dozens of cycles of install repair/ retry…. uninstall this or that including VS 2015/retry.
Then on day 11... it occurs to me that maybe this machine config setting I had introduced and started using a while back for VS 2010 might be playing a role in my inability to run VS 2015.
Sure enough! I had left the setting toggled on and after turning it off VS 2015 ran fine. Now that all my third party tools have been uninstalled and my VS 2015 environment basically trashed. I think I can recover…. but WOW! Glad it occurred to me that the dots might connect.
Hopefully sharing my experience saves someone some time.
Continue reading...
Cutting to the chase.... See if you at some time added the machine.config setting… legacyCasPolicy. If so, comment it out or turn it off. Now try VS 2015.
The back story....
A couple weeks back, I began working on a bug in a legacy Windows Forms application. The app is pretty old stuff… was originally built with VS 2008. I upgraded it to VS 2010 about 7 years ago.
I needed to locate the form that triggered the offending buggy logic and the best way was to get a look at likely form candidates was using the form designer. I discovered that the VS 2010 form designer had issues with the DevExpress ActiveX control suite that the app’s forms contained. I wrestled with VS 2010 before discovering a workaround… this machine.config setting….legacyCasPolicy. Now… this setting was no panacea. It presented some flaky behavior in VS 2010. When toggled on, I could use the forms designer, but could not get anything to build. When off, I could build, but not view anything in designer. Plus... when toggling the setting…. this also involved stopping/starting VS 2010. Ok… clunky… but manageable.
Fast forward 10 days or so... and now I need to open another solution in VS 2015 to check on something. This when I discover VS 2015 is doing the splash then nothing thing. The odyssey begins of literally dozens of cycles of install repair/ retry…. uninstall this or that including VS 2015/retry.
Then on day 11... it occurs to me that maybe this machine config setting I had introduced and started using a while back for VS 2010 might be playing a role in my inability to run VS 2015.
Sure enough! I had left the setting toggled on and after turning it off VS 2015 ran fine. Now that all my third party tools have been uninstalled and my VS 2015 environment basically trashed. I think I can recover…. but WOW! Glad it occurred to me that the dots might connect.
Hopefully sharing my experience saves someone some time.
Continue reading...