Tag Info

New answers tagged


using Microsoft.SharePoint; using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; using System.IO; namespace DownloadDoc { class Program { void DownloadDocs() { } static void Main(string[] args) { string siteUrl = "siteUrl"; using (SPSite site ...


I have finally found my own personal resolution to this issue. You need to install Office 2013 and use the InfoPath designer that comes with Office 2013. That with all your other pre req's will allow you to debug in VS2012. I have been trying to get out of the VSTA since it's compiler runs C# 2.0. This has personally enhanced my experience with InfoPath ...


This one worked for me: Highlight YourControl.ascx file in solution explorer. In properties window locate "Custom Tool" property and set it to SharePointWebPartCodeGenerator If your *.ascx file is valid, the ascx.g.cs should be generated as a result In my case mentioned, the property was empty and there was no sign of a g.cs file.


Yeah, it is pretty common problem. No matter how you try to edit your code it will be difficult to read, debug, manage, and update, when it is written inside elements.xml. I know that question is about the editor itself, but sometimes it is much better to write your JavaScript code in another .js file, and use only reference in CommandAction. You can load ...

Top 50 recent answers are included