I have been involved in the development of a fairly large SharePoint application. Our goal currently consists in migrating the application to SP 2013 and carrying on with the development using the SP 2013 features and object model. I have already successfully
tried the following scenarios:
- Install the 2010 solution wsp directly on SP 2013.
- Import the wsp in VS 2012 rebuild and deploy it to a 2013 installation.
However, neither of the cases has the desired effect. In the second case I cannot modify the code anymore, since it appears only inside the imported dlls (although the version is correct, i.e. 4.0 instead of 3.5).
Ideally, I would like to open the old solution with VS 2012 target the .NET 4.5 framework and reference the SharePoint 2013 dlls. However, the project properties only allow me to select .NET Framework 3.5 (hence even if I reference the new SP dll s, the build will fail, because these depend on other assemblies, such as mscorlib etc., whose version is defined automatically by the project target framework and cannot be tampered with.)
I have the feeling I am missing something here, but I do not know what. What is preventing my solution from targeting .NET 4.5 and is there any way to change this? I have already tried this with more than one SP 2010 solutions, (simple as well as more complicated), but so far no success.
Many thanks for any help or hints on the issue.
- Install the 2010 solution wsp directly on SP 2013.
- Import the wsp in VS 2012 rebuild and deploy it to a 2013 installation.
However, neither of the cases has the desired effect. In the second case I cannot modify the code anymore, since it appears only inside the imported dlls (although the version is correct, i.e. 4.0 instead of 3.5).
Ideally, I would like to open the old solution with VS 2012 target the .NET 4.5 framework and reference the SharePoint 2013 dlls. However, the project properties only allow me to select .NET Framework 3.5 (hence even if I reference the new SP dll s, the build will fail, because these depend on other assemblies, such as mscorlib etc., whose version is defined automatically by the project target framework and cannot be tampered with.)
I have the feeling I am missing something here, but I do not know what. What is preventing my solution from targeting .NET 4.5 and is there any way to change this? I have already tried this with more than one SP 2010 solutions, (simple as well as more complicated), but so far no success.
Many thanks for any help or hints on the issue.