Hot answers tagged visual-studio
Since CSOM supports Request Batching that allows to minimize the number of messages that are passed between the client and the server, it matters how operations are submitted to the server using ClientContext.ExecuteQuery method: ClientContext.ExecuteQuery method performs the actual request to the server, it could contain single or multiple operations. So, ...
You should watch out, that solutions don't get messy or too big. Don't put too many projects inside a solution, it will be impossible to find a webpart then if you have many of them with many projects inside. I always make one solution for like one page, with all the webparts in it inside one project and every "item" of them is in a separate feature. Because ...
you can do: Server.Transfer("Page2.aspx", true);
If you're on on-prem environment, you can customize the SuiteBar, there's a delegate control for the SuiteBar which you can override. For SP2013 online environment, you'd need to use jQuery to add links to it and CSS for changing color, font and styles.
If you want your own Error message, you have to make an application page (e.g. "error.aspx") and design it as per your requirement. Then set some properties like: properties.Status = SPEventReceiverStatus.CancelWithRedirectUrl; properties.RedirectUrl = "Error.aspx page's url"; Then this page will be displayed instead of the server error page.
Only top voted, non community-wiki answers of a minimum length are eligible