The heavy lifting tends to be handled in the project files themselves -- the build script just references those, we don't try and recreate that wheel.Overall it works great and it isn't really much duplicated code. SLN file as your 'build process', the file itself really doesn't constitute a build process.
Even with these checklists, when building large sites with hundreds of pages, the job of checking each item off against your encyclopaedia of pages can be hard to stomach.
This very need has lead to the creation of many different tools to help you scan your site to validate it against these lists – Visual Studio is one of these tools thanks to a nifty little feature that, though not many developers know it, allows you to check your site against the WCAG list without having to leave your favourite IDE. I suggest against this and instead suggest you cut & paste out of the actual output of your page as there can be differences that you miss when validating against a pre-run time page.
Adding Accessibility to a website for access by sight or hearing impaired users is a thought that many developers have post build.
Along with this, when you’re tasked with the job of building an accessible website, Visual Studio probably wouldn’t initially be a tool that comes to mind, but Visual Studio has everyone fooled on this topic as it has this functionality covered, you just need to look a little below the surface.
The Visual Studio tool I show you below can be used in a couple of different ways. New File Select HTML Page and click OK Open the Source View of the new HTML page in Visual Studio Paste the source code that you copied above in your web browser into the source code of your new HTML page Check Accessibility to open the WCAG checker Now select all the Priority items you want to validate the page against and click Validate In the Error and Warning pane at the bottom of your IDE pane you can review all the WCAG Priority exceptions individually.
Clicking on one of the items will take you to the exception in your page’s HTML.
That is to say, the build process is so reliable that no matter the build configuration, you will get a predictable build output. The result of a predictable and reliable build is that the test, deployment, and release process can then be highly automated, further reducing the risk of human error.
Establishing a build process requires an investment, but in certain cases, the investment is required.
The bigger concern is that now we'd have to maintain Is it safe to say that the and .csproj are consumed/maintained as usual from within the Visual Studio IDE GUI while the custom msbuild script is hand-written and usually consumes the already existing individual .csproj "as-is"?
That's one way I can see reduce overlap/duplicate in maintenance...
So, why should we bother migrating from solution files to an MSBuild 'makefile'?