title: Biztalk project naming conventions
body: <p>When starting a BizTalk project I generally follow the naming conventions found <a href="http://www.traceofthought.net/misc/BizTalk%20Naming%20Conventions.htm" rel="nofollow">here</a>.  Where you name your projects and assembly's something like:</p>
  
  <pre><code>MyCompany.MyProject.Orchestrations.dll
  MyCompany.MyProject.Schemas.dll
  MyCompany.MyProject.Pipelines.dll
  MyCompany.MyProject.Transforms.dll
  MyCompany.MyProject.PipelineComponents.dll
  </code></pre>
  
  <p>A couple of questions for other BizTalk folks:</p>
  
  <p>1) I usually find myself having more than one project with schemas or a need to separate schemas.  Do you stick them in separate assemblies and if yes, what convention do you then follow for naming the project/assembly.  If no, do you stick them in a subfolder in one assembly.</p>
  
  <p>2) I believe, could be wrong, that it's been sort of a BizTalk convention to name the project and assembly the same, like above.  I've thought about getting away from naming the projects the same as the full assembly name, so I might have the project named Maps and it's assembly is named MyCompany.MyProject.Maps.  Do others do this?</p>