Upgrade K9 to K10: CMSApp.csproj issues

After using the code analyzer did you use the Kentico installation manager to do the upgrade? And did you check the steps on the Kentico upgrade article?

I used the codeupgrade.exe before the upgrade with codeupgrade.exe ( codeupgrade.exe c:\project.sln -resolve ). I replaced my files with all the converted files ( all of them are only custom files like custom web parts ). All staging tasks were completed or removed and there were no problems with macro's reported.

After this, I used the Kentico Installation Manager 9.0 to do the upgrade. The upgrade reported 2 .new files ( global.asax.new and gulpfile.js.new ) which I merged manually afterwards.

Hopefully a Kentico support person will chime in, but if something botched, there are some options to consider (but do these on COPIES of course)

1: Try installing a fresh install of Kentico 10, then copy your custom files and code over to that, and change the database to point to your instance. Kentico is just files and database, if the database updated properly but the files didn't, sometimes just starting from a fresh kentico install file set and copying custom files is easiest.

2: You can do #1 but instead of copying custom from yours into the fresh, look to copy the LIB/bin/global.asax / .csproj files over from the fresh to your copy, perhaps those just didn't upgrade properly? Also do a text compare to see any differences between your web.config/cmsapp.csproj and a fresh, maybe you'll spot an error?

3: You can try re-doing the install processes, and don't change the code files until after the upgrade, i doubt it but maybe the early change messed up something that is required during the install...but again i doubt it.

Unfortunately this project was removed from v10. See the release notes in the Breaking changes - Platform section. There is a link in there on how to perform the upgrade to that project.

I know the CMSApp_AppCode project was removed from web application installations, but it's the main CMSApp project which doesn't update correctly.

Are all your references pointing to the correct directory with the updated dlls? You have to manually update those references if they are in a different location than initially installed.