Book Adam Now
Adam Cogan discusses SharePoint:
- Why would companies choose SharePoint?
- Overview of SharePoint (features)
- Reducing use of tables via ASP.NET control adapters
- Cross-browser compatibility the easy way with JQuery
- Customizing SharePoint web parts
- The yellow brick road to SharePoint delivering Australia’s largest website
- Why companies want to use SharePoint
- How you can make a website sexy implementing jQuery
- Removing the tables
- Using devs
- Giving it a live feeling
- Development tips
- Debugging tips
About the speakers
Adam Cogan is the Chief Architect at SSW, a Microsoft Certified Partner specializing in SharePoint and .NET Solutions. At SSW, Adam has been developing custom solutions for businesses across a range of industries such as Government, banking, insurance and manufacturing since 1990 for clients such as Microsoft, Quicken, and the Fisheries Research and Development Corporation.
SSW Chief Architect Adam Cogan shows how to categorize your YouTube channel with playlists and custom thumbnails to maximize user engagement.
Do you know how to get the best performance from your EF Core projects? SSW Senior Software Architect Andreas Lengkeek speaks with SSW Solution Architect Jernej (JK) Kavka about common mistakes on EF Core projects and how to fix them. || Subscribe for more content from SSW TV || || Press like and leave a…
https://www.ssw.com.au/rules/return-on-investment SSW Chief Architect Adam Cogan reviews Chewing The Fat feedback from the SSW team on Return on Investment (ROI) best practices. He is joined by SSW Solution Architect Jean Thirion. || Subscribe for more content from SSW TV || || Press like and leave a comment below to let us know how we’re doing…
https://www.ssw.com.au/rules/best-trace-logging SSW Solution Architect JK is a battle scared logging in .NET Core veteran. He shows Andreas Lengkeek his best practices for logging, gathered through his years of experience. When setup correctly, logging can save you hours in those moments when your code don’t run as planned. So take some notes on these best practices…
Sometimes you may not know what the backend technology for your API could be… perhaps it is a serverless Azure Functions App, a Logic App, or even a set of services running in Kubernetes. These questions may take time to answer, but you already made a choice on the frontend technology. You may already have…
Having a documented and discoverable API is fantastic. Your API consumers are able to easily understand and reason about your API to build their own integrations. Azure API Management provides us with everything we need to publish our APIs to the world. We can import one or more OpenAPI Spec docs, Swagger, WSDL, and other…