D
Devon_Nullman
Guest
For many years, whenever I wanted to create a new version of an existing project, all I had to do was close Visual Studio and copy the Folder, then rename it. When I do that now after installing 2019 and removing 2017, it's a disaster. Example:
Folder "Steve's Time Sheets" contains
TimeSheets - V1
TimeSheets - V2
TimeSheets - V3
...
TimeSheets - V6
Switched to 2019, copied V6, renamed from TimeSheets - V6 - Copy to TimeSheets - V7
opened the .sln and the code is all there but opening the form designer gives this
"The file 'C:\Users\devon\source\repos\2017\Steve's Time Sheets\TimeSheets - V6 - Monthly\TimeSheets\Form1.vb' does not support code parsing or generation because it is not contained within a project that supports code."
It's somehow referring to the last project. I then deleted all of the V7, opened V6, cleaned both the Debug and Release Builds and repeated the copy - same error. I searched the entire V7 folder for "V6" and it's not there. So I had to create a new project, named "Time Sheets - V7" and open V6 and V7 side by side to copy the form and the code, then manually re-create all Settings. Any ideas of how to get around this would be greatly appreciated.
Continue reading...
Folder "Steve's Time Sheets" contains
TimeSheets - V1
TimeSheets - V2
TimeSheets - V3
...
TimeSheets - V6
Switched to 2019, copied V6, renamed from TimeSheets - V6 - Copy to TimeSheets - V7
opened the .sln and the code is all there but opening the form designer gives this
"The file 'C:\Users\devon\source\repos\2017\Steve's Time Sheets\TimeSheets - V6 - Monthly\TimeSheets\Form1.vb' does not support code parsing or generation because it is not contained within a project that supports code."
It's somehow referring to the last project. I then deleted all of the V7, opened V6, cleaned both the Debug and Release Builds and repeated the copy - same error. I searched the entire V7 folder for "V6" and it's not there. So I had to create a new project, named "Time Sheets - V7" and open V6 and V7 side by side to copy the form and the code, then manually re-create all Settings. Any ideas of how to get around this would be greatly appreciated.
Continue reading...