<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Entity Designer CTP2 Comments</title>
	<atom:link href="http://www.primedigit.com/2007/12/07/entity-designer-ctp2-comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.primedigit.com/2007/12/07/entity-designer-ctp2-comments/</link>
	<description>Thoughts on ASP.NET, Visual Design, SQL Server 2005, C# and much more...</description>
	<lastBuildDate>Sat, 11 Jun 2011 20:01:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Sanjay Nagamangalam</title>
		<link>http://www.primedigit.com/2007/12/07/entity-designer-ctp2-comments/comment-page-1/#comment-44</link>
		<dc:creator>Sanjay Nagamangalam</dc:creator>
		<pubDate>Mon, 17 Dec 2007 05:50:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.primedigit.com/2007/12/07/entity-designer-ctp2-comments/#comment-44</guid>
		<description>Hey Will,

Thanks for your suggestions on the Entity Designer CTP2. Here are some responses to your feedback.

RE suggestion #1: Ignore the sysdiagrams table when importing by default. Those of us who actually want this can check this box when we import the tables. SQL2005 is kind enough to hide it in the System Tables folder, please do something similar.

&gt;&gt; We recently fixed a bug in the designer where we do not select any tables, views or stored procedures by default. Thus, sysdiagrams will be unchecked by deault to make this experience easier.

RE suggestion #2: How do I view the XML code? The only time I can easily get access to it is when there is an error. I can’t view it by right clicking on the .edmx file. (Like one can with a Data Access Layer .xsd file.) 

&gt;&gt; You can right-click the EDMX file in Solution Explorer and choose &quot;Open With...&quot; and select XML Editor.

RE suggestion #3: Return types of Navigation Properties are not displayed at all in the designer and difficult to ascertain without plowing through generated code. 

&gt;&gt; Yes, we want to make this better and are looking into some ideas

RE suggestion #4: Foreign key naming conventions are completely ignored for imported tables. Please don&#039;t ignore them, or make it easier to see what they were. 

&gt;&gt; We have filed a bug to make this better 

Please let us know if you have more feedback.

Regards,
Sanjay Nagamangalam
Lead PM, Entity Designer
Microsoft Corporation</description>
		<content:encoded><![CDATA[<p>Hey Will,</p>
<p>Thanks for your suggestions on the Entity Designer CTP2. Here are some responses to your feedback.</p>
<p>RE suggestion #1: Ignore the sysdiagrams table when importing by default. Those of us who actually want this can check this box when we import the tables. SQL2005 is kind enough to hide it in the System Tables folder, please do something similar.</p>
<p>&gt;&gt; We recently fixed a bug in the designer where we do not select any tables, views or stored procedures by default. Thus, sysdiagrams will be unchecked by deault to make this experience easier.</p>
<p>RE suggestion #2: How do I view the XML code? The only time I can easily get access to it is when there is an error. I can’t view it by right clicking on the .edmx file. (Like one can with a Data Access Layer .xsd file.) </p>
<p>&gt;&gt; You can right-click the EDMX file in Solution Explorer and choose &#8220;Open With&#8230;&#8221; and select XML Editor.</p>
<p>RE suggestion #3: Return types of Navigation Properties are not displayed at all in the designer and difficult to ascertain without plowing through generated code. </p>
<p>&gt;&gt; Yes, we want to make this better and are looking into some ideas</p>
<p>RE suggestion #4: Foreign key naming conventions are completely ignored for imported tables. Please don&#8217;t ignore them, or make it easier to see what they were. </p>
<p>&gt;&gt; We have filed a bug to make this better </p>
<p>Please let us know if you have more feedback.</p>
<p>Regards,<br />
Sanjay Nagamangalam<br />
Lead PM, Entity Designer<br />
Microsoft Corporation</p>
]]></content:encoded>
	</item>
</channel>
</rss>

