The new upgrade system
-
I have used Visual C++ for many years without trouble. But in the last few days, an automatic upgrade came: it shows a MessageBox that says "One-way upgrade. Visual Studio will automatically make functional changes to the following projects in order to open them. ...". With one of my projects (called 'dragclip_vc'), today, however often I open it and look in it and close it, the new upgrade system shows and needs attention, every time I open that project, and it does not preserve the display of opened files. Please how can I stop that from happening? (I know that the automatic upgrade needs doing once for each of my projects.) (Another of my projects (called 'makeobj_vc') auto-upgraded correctly and did not ask again for upgrading, and it preserves the display of opened files.) dragclip_vc is a very small project; all that it does is that if I drag a file into it from a directory display, it puts that file's full pathname in the Windows clipboard. It is useful. makeobj_vc is a big project. The '_vc' on the ends of their names means "for Visual C++"; it is to distinguish from old versions that I had written for Borland C.
-
I have used Visual C++ for many years without trouble. But in the last few days, an automatic upgrade came: it shows a MessageBox that says "One-way upgrade. Visual Studio will automatically make functional changes to the following projects in order to open them. ...". With one of my projects (called 'dragclip_vc'), today, however often I open it and look in it and close it, the new upgrade system shows and needs attention, every time I open that project, and it does not preserve the display of opened files. Please how can I stop that from happening? (I know that the automatic upgrade needs doing once for each of my projects.) (Another of my projects (called 'makeobj_vc') auto-upgraded correctly and did not ask again for upgrading, and it preserves the display of opened files.) dragclip_vc is a very small project; all that it does is that if I drag a file into it from a directory display, it puts that file's full pathname in the Windows clipboard. It is useful. makeobj_vc is a big project. The '_vc' on the ends of their names means "for Visual C++"; it is to distinguish from old versions that I had written for Borland C.
The affected project ('dragclip_vc') is still doing it this morning (5.37 a.m. by UK time), and wanting this upgrade every time that I open it. The other mentioned project ('makeobj_vc') opened correctly this morning and did not ask for this upgrade again. If needed, I have old backup copies of all my Visual C++ projects on an offload-disk.
-
I have used Visual C++ for many years without trouble. But in the last few days, an automatic upgrade came: it shows a MessageBox that says "One-way upgrade. Visual Studio will automatically make functional changes to the following projects in order to open them. ...". With one of my projects (called 'dragclip_vc'), today, however often I open it and look in it and close it, the new upgrade system shows and needs attention, every time I open that project, and it does not preserve the display of opened files. Please how can I stop that from happening? (I know that the automatic upgrade needs doing once for each of my projects.) (Another of my projects (called 'makeobj_vc') auto-upgraded correctly and did not ask again for upgrading, and it preserves the display of opened files.) dragclip_vc is a very small project; all that it does is that if I drag a file into it from a directory display, it puts that file's full pathname in the Windows clipboard. It is useful. makeobj_vc is a big project. The '_vc' on the ends of their names means "for Visual C++"; it is to distinguish from old versions that I had written for Borland C.
Anthony Appleyard wrote:
But in the last few days, an automatic upgrade came: it shows a MessageBox that says "One-way upgrade. Visual Studio will automatically make functional changes to the following projects in order to open them
What VS version are you using? In what version is it about to upgrade?
-
The affected project ('dragclip_vc') is still doing it this morning (5.37 a.m. by UK time), and wanting this upgrade every time that I open it. The other mentioned project ('makeobj_vc') opened correctly this morning and did not ask for this upgrade again. If needed, I have old backup copies of all my Visual C++ projects on an offload-disk.
-
Anthony Appleyard wrote:
But in the last few days, an automatic upgrade came: it shows a MessageBox that says "One-way upgrade. Visual Studio will automatically make functional changes to the following projects in order to open them
What VS version are you using? In what version is it about to upgrade?
I have VS 2015. Its help recommends upgrading to VS 2017.
-
Anthony Appleyard wrote:
But in the last few days, an automatic upgrade came: it shows a MessageBox that says "One-way upgrade. Visual Studio will automatically make functional changes to the following projects in order to open them
What VS version are you using? In what version is it about to upgrade?
Victor Nijegorodov wrote:
What VS version are you using? In what version is it about to upgrade?
When I run my project makeobj_vc , the initial black panel shows "Visual Studio / Community 2015". When I opened its help just now, a top panel said "We recommend using Visual Studio 2017 / Download now"; but will that cause a quick replacement of my VS 2015 by VS 2017, or will there be a long complicated process?
-
Anthony Appleyard wrote:
But in the last few days, an automatic upgrade came: it shows a MessageBox that says "One-way upgrade. Visual Studio will automatically make functional changes to the following projects in order to open them
What VS version are you using? In what version is it about to upgrade?
When I run my project makeobj_vc , the initial black panel shows "Visual Studio / Community 2015". When I opened its help just now, a top panel said "We recommend using Visual Studio 2017 / Download now"; but will that cause a quick replacement of my VS 2015 by VS 2017, or will there be a long complicated process?
-
Anthony Appleyard wrote:
But in the last few days, an automatic upgrade came: it shows a MessageBox that says "One-way upgrade. Visual Studio will automatically make functional changes to the following projects in order to open them
What VS version are you using? In what version is it about to upgrade?
I am using VS 2015. When I opened its help just now, a top panel recommended using VS 2017; will that cause a quick replacement of my VS 2015 by VS 2017, or will there be a long complicated process?
-
Victor Nijegorodov wrote:
What VS version are you using? In what version is it about to upgrade?
When I run my project makeobj_vc , the initial black panel shows "Visual Studio / Community 2015". When I opened its help just now, a top panel said "We recommend using Visual Studio 2017 / Download now"; but will that cause a quick replacement of my VS 2015 by VS 2017, or will there be a long complicated process?
-
When I run my project makeobj_vc , the initial black panel shows "Visual Studio / Community 2015". When I opened its help just now, a top panel said "We recommend using Visual Studio 2017 / Download now"; but will that cause a quick replacement of my VS 2015 by VS 2017, or will there be a long complicated process?
-
Anthony Appleyard wrote:
But in the last few days, an automatic upgrade came: it shows a MessageBox that says "One-way upgrade. Visual Studio will automatically make functional changes to the following projects in order to open them
What VS version are you using? In what version is it about to upgrade?
I have now upgraded to VS 2017. I have used it to remake my project 'dragclip_vc'. In it, the top menu has entries for "File, Edit, View, Project, Team, Tools, Windows, Help", but none of then seem to lead to an option letting me compile or run the source file. What should I do?
-
Fix your existing problems first. Once you have all your projects successfully building in VS2015 then you can consider upgrading to 2017.
Thanks for your help. I am sorry if I have caused any problems. I tried uploading VS 2017; it installed itself alongside my VS 2015 and did not obliterate it. I used my desktop "Visual C 2015 devenv.exe" icon to access my VS 2015, and I tried to access several of my projects. All but one of them that I tried came up and recompiled successfully, and there was no "One-way upgrade. Visual Studio ..." nuisance. The only project that caused trouble was dragclip_vc, which kept on showing the "One-way upgrade. Visual Studio will automatically make functional changes to the following projects in order to open them. ...". MessageBox. So I remade this project as a new VS 2015 project dragclip2 using copies of dragclip_vc's source files, and this new project behaves OK. I suspect that the "One-way upgrade. Visual Studio ..." nuisance persisted because dragclip is such a small project that it does not have some feature that "One-way upgrade. Visual Studio ..." looks for to see if it has already been called on that project. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Next step for me, I suppose, is to find how to run VS 2017. It looks very different from VS 2015. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I keep pointers to all my Visual C++ projects in a folder called C:\Visual_C\Visual_C_pointers\
-
Thanks for your help. I am sorry if I have caused any problems. I tried uploading VS 2017; it installed itself alongside my VS 2015 and did not obliterate it. I used my desktop "Visual C 2015 devenv.exe" icon to access my VS 2015, and I tried to access several of my projects. All but one of them that I tried came up and recompiled successfully, and there was no "One-way upgrade. Visual Studio ..." nuisance. The only project that caused trouble was dragclip_vc, which kept on showing the "One-way upgrade. Visual Studio will automatically make functional changes to the following projects in order to open them. ...". MessageBox. So I remade this project as a new VS 2015 project dragclip2 using copies of dragclip_vc's source files, and this new project behaves OK. I suspect that the "One-way upgrade. Visual Studio ..." nuisance persisted because dragclip is such a small project that it does not have some feature that "One-way upgrade. Visual Studio ..." looks for to see if it has already been called on that project. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Next step for me, I suppose, is to find how to run VS 2017. It looks very different from VS 2015. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I keep pointers to all my Visual C++ projects in a folder called C:\Visual_C\Visual_C_pointers\
-
No problem, just pointing out how the system works. And, for some odd reason, most of your messages were going to moderation as potential spam.
Thanks. Do you want me to send to you a copy of the old form of my 'dragclip' program?, so that you can investigate why "One-way upgrade. Visual Studio ..." repeatedly asked to upgrade it?
-
Thanks. Do you want me to send to you a copy of the old form of my 'dragclip' program?, so that you can investigate why "One-way upgrade. Visual Studio ..." repeatedly asked to upgrade it?