3 ms·

> but the largest and hardest part was actually migrating the entire project from VS2008 to VS2019 Worst I've ever had to do was 2008 to 2015 but damn I don't

> but the largest and hardest part was actually migrating the entire project from VS2008 to VS2019 Worst I've ever had to do was 2008 to 2015 but damn I don't envy those teams.

xeromal 4y ago
That is a monster migration. I wonder how big the migration compatibility list was. I haven't used VS since about 2017, but in some ways I miss it. It's big and unwieldy, but very powerful and helpful and was a staple of my 20s as a software dev.
- doubled112 4y ago
  Maybe it won't be so bad. Let's click build and see what fails? *errors scroll up screen faster than any mortal can read for 20 minutes* You know? Maybe I should check the docs.
  - xeromal 4y ago
    I remember doing it to one of our legacy projects and the list was so long I just created new solutions and projects from scratch and copy the files over one at a time and ran them independently so I could slowly ensure everything worked
NonNefarious 4y ago
I loved Visual Studio (and Visual C++ before it), but after firing it up again and seeing the same ridiculous defects 10 years later was pretty disheartening. This is a pretty good rundown: https://goldmanosi.blogspot.com/2012/05/visual-studio-is-it-getting-worse-as.html https://goldmanosi.blogspot.com/2012/05/visual-studio-is-it-...
thefz 4y ago
Had to do many VS migrations and in the end, proper version control system hygiene has helped a lot. Moving the strict necessary code and metadata only (.sln, .csproj and so on) and letting the IDE rebuild the rest has been the easiest.
- IYasha 4y ago
  You know, with all the UUID garbage these solution files have inside, I expected VS to recognize and set everything to right places. But NO. NONE of my projects could be built in the next release. NEVER. The errors are chaotic and it becomes easier to just write that sh* by hand in notepad. But what would you expect from an evilcorp?..
IYasha 4y ago
It struck me too! They have the entirety of my feelings. I was not yet able to migrate from 2010 to 2019 :( MS ruined VS after the 6.0.

> but the largest and hardest part was actually migrating the entire project from VS2008 to VS2019 Worst I've ever had to do was 2008 to 2015 but damn I don't envy those teams.

xeromal 4y ago

That is a monster migration. I wonder how big the migration compatibility list was. I haven't used VS since about 2017, but in some ways I miss it. It's big and unwieldy, but very powerful and helpful and was a staple of my 20s as a software dev.

doubled112 4y ago
Maybe it won't be so bad. Let's click build and see what fails? *errors scroll up screen faster than any mortal can read for 20 minutes* You know? Maybe I should check the docs.
- xeromal 4y ago
  I remember doing it to one of our legacy projects and the list was so long I just created new solutions and projects from scratch and copy the files over one at a time and ran them independently so I could slowly ensure everything worked

NonNefarious 4y ago

I loved Visual Studio (and Visual C++ before it), but after firing it up again and seeing the same ridiculous defects 10 years later was pretty disheartening. This is a pretty good rundown: https://goldmanosi.blogspot.com/2012/05/visual-studio-is-it-getting-worse-as.html https://goldmanosi.blogspot.com/2012/05/visual-studio-is-it-...

thefz 4y ago

Had to do many VS migrations and in the end, proper version control system hygiene has helped a lot. Moving the strict necessary code and metadata only (.sln, .csproj and so on) and letting the IDE rebuild the rest has been the easiest.

IYasha 4y ago
You know, with all the UUID garbage these solution files have inside, I expected VS to recognize and set everything to right places. But NO. NONE of my projects could be built in the next release. NEVER. The errors are chaotic and it becomes easier to just write that sh* by hand in notepad. But what would you expect from an evilcorp?..

IYasha 4y ago

It struck me too! They have the entirety of my feelings. I was not yet able to migrate from 2010 to 2019 :( MS ruined VS after the 6.0.