Tag Info

New answers tagged

0

There's a lot of locations in your code that may fail with an NRE. For instance, it could be the group that is not found, or a group with no email address... You're only hope is to get more information on the error (like the Stack Trace). For that purpose, you may: Add try...catch blocks in your code (a best pratice anyway), and display detailed ...


-1

<SharePoint:DateTimeControl ID="dtControl" runat="server" DateOnly="true" DatePickerFrameUrl="../_layouts/15/iframe.aspx" />


0

Each WebPart should have its own ID, and you can iterate over all WebParts in the manager (I don't do backend, but conceptually the same as front-end) As for best pratice; don't mess with styles. Transfer all your display logic to CSS classes, and only set those Classes in your code. That way your presentation is a lot more loosly coupled with your backend ...


-1

I would also add to the list of the web parts that you can use to change your AD password within SharePoint environment is Virto SharePoint Change Password Web Part. It supports both AUTH methods - AD and Form-based. You can download it here. As I know boost has a similar web part too. Hope it will help you!


0

var linkItem = new SPFieldUrlValue(listItem["URL"].ToString()); SPFieldUrlValue value = new SPFieldUrlValue(linkItem.Description.ToString().Trim()); string URL = value.Url;


0

May be your href="#" is creating your problem. Try to replace it with href="javascript:void(0);". Best approach would be to use asp.net controls like asp:button or asp.LinkButton instead of pure html a, here you will not be required to place some extra efforts.


3

you can create a separate Project eg. "Common" where you include those classes. You can reference that assembly than from your other Projects. Of course, you have to ensure that this wsp is installed along your other wsps (which use that dll)



Top 50 recent answers are included