See this discussion: http://entityframework.codeplex.com/discussions/432652
Comments: From the Discussion, be aware of the following note when working on this issue. From: ajcvickers Hi hintzen, This sounds like a reasonable idea and we have had similar thoughts in the past. The main thing to be aware of is that Code First already uses "normal" connection strings and we use this differentiator as a way to decide whether to run the Code First pipeline to build a model verses loading from metadata files. Any convention to find metadata must be robust enough that it doesn't cause something that would previously have built a Code First model to now use metadata files or fail.
Comments: From the Discussion, be aware of the following note when working on this issue. From: ajcvickers Hi hintzen, This sounds like a reasonable idea and we have had similar thoughts in the past. The main thing to be aware of is that Code First already uses "normal" connection strings and we use this differentiator as a way to decide whether to run the Code First pipeline to build a model verses loading from metadata files. Any convention to find metadata must be robust enough that it doesn't cause something that would previously have built a Code First model to now use metadata files or fail.