Manual deployments are NOT fun. In this presentation, Peter Gfader discusses:
- Continuous Delivery with msbuild and msdeploy
- How painful current deployments are
- What benefit we get through an automated deployment process
- How to automate the deployment with TFS 2010
- Best practices with Continuous Delivery.
About the speakers
Peter was born in South Tirol Italy, studied in Austria, and is now working in Sydney Australia as a consultant for SSW. Peter is an Agile Enthusiast, aspiring Software Craftsman, likes Clean Code and is a strong believer in improving in baby steps. Peter blogs about .NET development. On his blog, he covers many aspects of C# programming, usability tips & tricks, best practices in teams, problems and his solution approach.
He is also an athlete that likes running, mountain biking, rock climbing, and surfing.
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…