These questions seem to be sprinkled across this forum but I still cannot find the answer. We are upgrading a SP2010 site to 2016. There must be some magic combination that makes this work but so far I have not found it. When we open the application in VS 2015 the tool prompts for and then completes an upgrade process. But the result is the file not found exception. If I check on the hard drive I can find the files in the expected place
"C:\Program Files\Common Files\microsoft shared\Web Server
Extensions\16\TEMPLATE\CONTROLTEMPLATES\AdminWebParts/Admin_Welcome/Admin_WelcomeUserControl.ascx"
the package.package version number is updated to 16.0 and the ascx path is
@"~/_CONTROLTEMPLATES/Brookfieldrps.OE.AdminWebParts/Admin_Welcome/Admin_WelcomeUserControl.ascx";
when the code tries to load the file from the AscxPath it cant find the file. Some posts have suggested adding 15 to the path, although 16 seems like a better choice given we are trying to go to SP2016 but neither of these work.
If I create a new web part then the Package.package version number is 16.0 and the _ascxpath is
_ascxPath = @"~/CONTROLTEMPLATES/SharePointProject1/VisualWebPart1/VisualWebPart1UserControl.ascx.
The path where I can find the deployed code is
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\TEMPLATE\CONTROLTEMPLATES\SharePointProject1\VisualWebPart1
\VisualWebPart1UserControl.ascx
This matches what the upgraded project is. So does anyone know what the paths should be and why it can't find it at the place it is supposed to be?
Also do I have to change the "layouts" path as well?
