SeeAlso: EDRAWiki

Summary: Validating your EDRA schema

As you know EDRA uses configuration files to support declarative specification of pipeline configurations etc. Troubleshooting misconfigurations of this file can be timeconsuming, so I wanted to ensure that people were familiar with the validation tools that we have in place at the moment - and some ideas we are thinking of for the future:

Validation Tool:
The EDRA Architecture Document has a section called Framework Utilities that describes tools that accompany the EDAF. One such tool is called the ConfigurationValidator.exe. This tool should be your first resource should you run into troubles debugging this soltion. Configuration of this tool is managed by modifying the data in the configurationvalidator.exe.config file. The config that ships with the validator does need to be be modified to your suit your environment. If you have used the default installation directory you should be able to replace the appSettings section with following section with the section to get started with the template application...

<appSettings>
<add key="MSMQTargetName" value="msmq"/>
<add key="BusinessActionTargetName" value="businessAction"/>
<add key="instrumentationConfigFile" value="C:\Program Files\Microsoft EDRA\CS\ReferenceArchitecture\Template\Solution Items\EnterpriseInstrumentation.config"/>
<add key="ConsoleHostPath" value="C:\Program Files\Microsoft EDRA\CS\ReferenceArchitecture\Transports\Hosts\Console\bin\Debug"/>
<add key="ServiceHostPath" value="C:\Program Files\Microsoft EDRA\CS\ReferenceArchitecture\Transports\Hosts\Service\bin\Debug\"/>
<add key="WebServiceDispatchingHostPath" value="C:\Program Files\Microsoft EDRA\CS\ReferenceArchitecture\Transports\Dispatching\WebService\bin"/>
<add key="DCOMDispatchingHostPath" value="C:\Program Files\Microsoft EDRA\CS\ReferenceArchitecture\Transports\Dispatching\DCom\bin\Debug"/>
<add key="WebServiceInterfaceHostPath" value="C:\Program Files\Microsoft EDRA\CS\ReferenceArchitecture\Template\BusinessLayer\Services\TransportInterfaces\WebServiceInterface\bin"/>
</appSettings>

Ideas:
We have posted some tools on GotDotNet for:
- Config Editor - ideally used in environments such as QA and Production that do not have Visual Studio installed. Probably used by operations folks.
- Visual Studio wizards - to help generate code based upon input data

We are looking for feedback on these tools - either in the Suggestions section of this Wiki or on GotDotNet. Let us know if you want these tools...