Please note that some posts are in German, some in English.
A Sitecore config patch that is environment-server-specific will definitely require different versions, therefore, config transformation is necessary to avoid manual modification. Though, by default, transformation is only supported for the Web.config file there are many tools available that will help you achieve this. However, most of them require that your config transforms do not go beyond the limits of your configurations.
Read more With Visual Studio's publish functionality you can conveniently preview how your web project behaves and looks like on your local IIS web server. With that said, I believe publishing makes sense only if you've done significant changes since, depending on how big your project is, it may take some time to sync your deployable project files with the web site root folder, and deploying new DLLs and config files will definitely restart your website and flush your caches.
But what if you just did a tiny update and just wanted to sync the changed file(s)?
