3

Looking for an answer to this question since I heard of .NET 4.5.1, I've nearly given up the hope. Looks like no one has written anything about this anywhere. So now that 4.5.1 and VS2013 were released... Is it possible to switch SP to the new .NET Framework and use this long awaited feature, Edit & Continue, in SharePoint? It works in ASP.NET too.

Update: Just installing VS2013 and testing a previous solution did not work. Obviously you have to change SP to somehow use 4.5.1.

Creating a new SP Project targetting 4.5.1 does not work.

  • Have you tried it? After some research, it looks like that is possible, or at least Visual Studios 2013 is compatible with SharePoint 2013. – Mike Nov 11 '13 at 18:50
  • @Mike Yes I tried to edit the code in a simple SP Solution, but it told me that edit&continue is not available in x64. I guess you need to change SP so that it uses 4.5.1 because that is what you need for edit&continue to work afaik. – Kirschi Nov 12 '13 at 8:03
  • seriously? no one knows about or is interested in this life changing feature? – Kirschi Jan 24 '14 at 9:10
  • Add a bounty to it! You'll be sure to get some good answers, but this is something I have not personally have expertise in. – Mike Jan 24 '14 at 14:50
  • It seems as though edit and continue is strictly for 4.5.1, and sharepoint is strictly 4.5. Maybe the SP1 will include support for 4.5.1 and its features. – Mike Jan 24 '14 at 14:55
1

You have limited edit and continue when developing apps for SharePoint. Changes to markup, JavaScript, and CSS will get pushed up to SharePoint when you save the source file. Developing and Debugging Apps for SharePoint with Visual Studio 2013 shows an example of this around the 24 minute mark.

I don't think it's possible to get edit and continue to work for SharePoint solutions. If it was possible, it would require significant changes to the Visual Studio tooling. Right now, you update assemblies by rebuilding the solution package and deploying. This causes a reset of the IIS web application hosting SharePoint. I can't see any way this could happen during a Visual Studio debug session.

| improve this answer | |
0

Is this a standalone development environment? or are you deploying your app to the SharePoint production?

If this application is being deployed to SharePoint farm production environment, see if updating the .NET Framework in the SP farm from 4.5 to 4.5.1 or 4.5.2 will fix the issue.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.