New answers tagged visual-studio-2012
0
Found a solution. This works:
SPWeb web=workflowProperties.Web;
SPList customwflist= workflowProperties.List;
string str="abcdeneme";
SPListItem listitem=workflowProperties.Item;
listitem["Address"]=str;
listitem.Update();
0
It will likely be a lot easier to develop these as 2010 sandboxed solutions and deploy them to the 2013 site. Almost all 2010 solutions still work in 2013 and it even still has the 14 hive. If you need to develop each as an app that will be a little more work but that is not required for it to work in 2013. Even then an app is mostly packaging around a ...
1
Since Visual Studio 2012 was released before the updated version of SharePoint there (were) some post install updates that had to be run. I believe at this point, everything is bundled into VS 2012 Update 2 which was released recently.
http://www.microsoft.com/en-us/download/details.aspx?id=38188
0
Same question here with some suggestions for a workaround. A workaround is not recommended, though.
By the way, I had the same problem, and installed SharePoint Foundation 2010. It does not have all the options like a "regular" SharePoint, but it is free, runs fast and matches the requirements to run a decent test. The installation is described here. Just ...
2
You can develop VS projects ONLY on the same server where SharePoint is installed.
By the way, if you're using SharePoint 2013, you can develop APPS on a remote Server but that's another story.
1
How to organize source control for multiple projects depending on common projects in Sharepoint 2013
For groups that do a lot of small projects, sometimes it's best to have a TFS project for the Team, and not multiple projects per development project. For example, perhaps you're using scrum, and your backlog has items from HR and other groups. But, even though there are different "projects" with different deadlines and even different technologies, it's ...
0
Your xsl file should be located here:
c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\XSL\
To map your xsl file to this folder you need to create Sharepoint Mapped Folder.
Here is explanation how to do that.
1
Make sure that in Visual Studio under "Project->xy Properties" under the "SharePoint" section the option "retract after debugging" is checked.
1
You need to retract or uninstall app, Simply stopping debugging won't going to retract or uninstall the app automatically.
If you tried to retract and uninstall app and got error then,
You need to change the ProductID in the appmanifest.xml file to
something else. This will deploy another app with the same name.
I guess this is a known issue and ...
0
You probably changed the name of the feature or a property of the feature.
Use the force attribute to explicitly re-install the feature.
Top 50 recent answers are included
