New answers tagged visual-web-part
Adding attachments to list items is completely different than uploading files to a doc lib. You first need to get a reference to the SPPListItem you want to attach to, and then you use myListItem.Attachments.Add. Here's a sample of code that may help you: it attaches multiple files (from local drive instead than from the UplaodFile control, but the story is ...
You have to store a string that serializes all your values. Obviously, since the string has now a special meaning, WebBrowsable only won(t do the magic to translate it into a nice selection UI. To handle the UI to display/set values in this string, you'll need to develop your own Tool part. You'll find a lot of examples on the Web, e.g.: ...
You will need to create Custom ToolPart to dynamically populate the dropdown values.You will need to create a class file in the WebPart and Inherit the ToolPart class and then create the dropdown and populate the dropdown and override the child controls and apply changes method of WebPart. Below is an example where i populated the DroppDown with all the ...
I am going to go ahead an answer this to save some poor soul in the future. The problem was with the App Manifest file. I had the Permissions => Scope set to Site Collection. This needs to be changed to 'Web'.
In addition to add/install the WSP package, you need to activate the feature that contains the Web part on each site collection you want it. Open your site collection root in a browser, go to "Site settings", "Site collection features" and activate your feature. After that, your Web part should be provisionned and visible in the WP galery.
There's not a huge difference for all of them. 3 out of 4 of them are server-side controls. And the SharePoint:InputFormTextBox and wssawc:InputFormTextBox are the exact same, only the prefix namespace (i.e. SharePoint, wssawc) is the difference. SharePoint/wssawc:InputFormTextBox has built-in co-operative field validation, the others don't. That's the ...
Top 50 recent answers are included