XML for Designers: From Syndication to Web Services -- Visual Studio Magazine

XML for Designers: From Syndication to Web Services

Learn how you can use XML to simplify your Web development processes.

By Joe Marini
07/01/2006

This video is no longer available on this site.

About the Author

Joe Marini has been active in the web and graphics industry for more than 15 years. He was an original member of the Dreamweaver engineering team at Macromedia, and has also held prominent roles in creating products such as QuarkXPress, mFactory's mTropolis, and Extensis QX-Tools. He is a regularly featured speaker at industry conferences and has authored or co-authored several books on web development. His book, The Document Object Model, is widely regarded as the definitive resource for working with the DOM.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.