Timeline for asp.net project and sharepoint project
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2014 at 8:28 | comment | added | Robert Lindgren | SharePoint 2013 support .Net 4.5, 2010 is in .Net 3.5, so your only solution there is to either upgrade Sharepoint to 2013 or downgrade your ASP.Net app | |
| Jun 17, 2014 at 8:26 | comment | added | user29701 | the problem is that SharePoint project does not support .NET 4.0 ! it only support .Net 3.5 . that's why my solution work fine in ASP.NET and not in SharePoint Project. Is there any solution to SharePoint Project support .NET 4.0 ?– | |
| Jun 16, 2014 at 19:35 | comment | added | Robert Lindgren | You will only be able to use client object model in an asp.net application. Otherwise you would have to work on SharePoint, creating Webparts and / or application pages directly in SharePoint. That way you will be able to use the more (for 2010 at least) complete server side object mode | |
| Jun 16, 2014 at 18:57 | comment | added | user29701 | Hi and thanks for your reply; I'm using Sharepoint 2010 and as I see that CSOM is too limited. what I really need is to have a methode that can get a form of infopath(xml) as an xmldocument and work with it in my asp project and after update it in my sharepoint library. I think I really need to use this two project in the same solution unfortunatlly, is that possible?? and if yes how can I do it?? Thanks in advance | |
| Jun 16, 2014 at 18:46 | comment | added | user29701 | but I'm using sharepoint 2010. Is that possible in 2010 | |
| Jun 16, 2014 at 18:19 | history | answered | Robert Lindgren | CC BY-SA 3.0 |