Sergio Otoya discusses:
- SharePoint, Rapid fire and implementing custom site maps
- Tips and tricks on Dataviews
- How to use the new features in ASP 2.0 and custom site maps, no code required
- How to bind the dataview to the listname in SharePoint Designer
- How to create a remote list viewer, no code required
- How the largest public SharePoint site in Australia (WorleyParsons.com) got up and running.
About the speakers
King of Echo
Sergio specializes in building teams, research and development, Microsoft SharePoint, .NET, SQL Server, Biztalk, Software architecture and design and Microsoft Stack. He is the senior architect and Project Manager of the echo products and migration group at Axceler. Sergio previously worked as Technology Manager at Echo Technology for 8 years and as Technical Director at Livepoint for 13 years. He has PG Cert in Management and a BSc at Computer Science from Macquarie University.
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…