<?xml version="1.0" encoding="UTF-8"?><rss version="0.92">
<channel>
	<title>David DeWinter</title>
	<link>http://blogs.rev-net.com/ddewinter</link>
	<description>A Developer's Melting Pot: LINQ to SQL, Entity Framework, .NET Security...</description>
	<lastBuildDate>Tue, 24 Aug 2010 14:37:10 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress/3.0.1" -->

	<item>
		<title>Persisting Collections of Scalar Properties in the Entity Framework</title>
		<description><![CDATA[Our team has done a lot of work over the past few years to bring the Entity Framework up as an enterprise-ready ORM, but there is a still a lot of work for us to do going forward, particularly in the area of object flexibility. Even though with POCO entities we allow some customization when [...]]]></description>
		<link>http://blogs.rev-net.com/ddewinter/2010/08/24/persisting-collections-of-scalar-properties-in-the-entity-framework/</link>
			</item>
	<item>
		<title>Viewing Generated Proxy Code in the Entity Framework</title>
		<description><![CDATA[This is one post that&#8217;s been on my to-do list for a while, and since I&#8217;ve seen some questions relating to it in our forums, I thought it appropriate to get it out the door before .NET 4 officially releases. As you may know, the Entity Framework supports mapping database information to POCO (Plain Old [...]]]></description>
		<link>http://blogs.rev-net.com/ddewinter/2010/04/08/viewing-generated-proxy-code-in-the-entity-framework/</link>
			</item>
	<item>
		<title>Tip #20 &#8211; Opting Out of Security Changes in .NET 4 in ASP.NET and Custom AppDomains</title>
		<description><![CDATA[Legacy CAS Policy in ASP.NET In a previous tip I discussed how you could re-enable CAS policy in applications running in .NET 4 by adding a switch to the application configuration file. However, Constantin Baciu brought up that even when using this configuration switch in a web.config, ASP.NET still threw the SecurityException: This method explicitly [...]]]></description>
		<link>http://blogs.rev-net.com/ddewinter/2010/03/02/tip-20-opting-out-of-security-changes-in-net-4-in-asp-net-and-custom-appdomains/</link>
			</item>
	<item>
		<title>We&#8217;re Hiring! Test Positions Open on Entity Framework and WCF Data Services (Astoria) Teams</title>
		<description><![CDATA[With work on Visual Studio 2010 winding down, both the Entity Framework and Astoria teams have test engineer positions open. Here are the job postings: Astoria Entity Framework Note: If the job descriptions above still say you need C/C++ experience, this is not true. If you don&#8217;t have experience in these areas, don&#8217;t let that [...]]]></description>
		<link>http://blogs.rev-net.com/ddewinter/2010/01/27/were-hiring-test-positions-open-on-entity-framework-and-wcf-data-services-astoria-teams/</link>
			</item>
	<item>
		<title>POCO Templates for Entity Framework v4 Beta 2 Released</title>
		<description><![CDATA[Today we have finally released an update to the POCO Templates that is compatible with Visual Studio 2010 Beta 2. Official announcement on the ADO.NET team blog. One thing I will highlight is that the templates won&#8217;t be released with the final version of Visual Studio 2010. Instead we will continue to push releases through [...]]]></description>
		<link>http://blogs.rev-net.com/ddewinter/2010/01/25/poco-templates-for-entity-framework-v4-beta-2-released/</link>
			</item>
	<item>
		<title>CAS Policy on 64-bit Machines &#8211; #19</title>
		<description><![CDATA[Well it’s been quite a while since my last post. I hope you all had a happy holiday season! Today I’m going to talk about an issue I saw recently with a 64-bit machine and the partial trust tests for the Entity Framework. Even though .NET 4 disables CAS policy, it is more interesting for [...]]]></description>
		<link>http://blogs.rev-net.com/ddewinter/2010/01/10/cas-policy-on-64-bit-machines-19/</link>
			</item>
	<item>
		<title>Asserting for Permissions in .NET 4 &#8211; #18</title>
		<description><![CDATA[Security asserts are a way to tell the CLR to stop checking for permissions past a certain point in the call stack. Of course, not all code is allowed to assert, or we&#8217;d have some big security problems to worry about. Specifically, partial trust code and security transparent code cannot assert for permissions. You may [...]]]></description>
		<link>http://blogs.rev-net.com/ddewinter/2009/06/25/asserting-for-permissions-in-net-4/</link>
			</item>
	<item>
		<title>How to Build APIs with Transparency in Mind &#8211; #17</title>
		<description><![CDATA[In the .NET Framework there are a few types which expose both &#34;safe&#34; and &#34;unsafe&#34; equivalents of the same method. Both methods achieve the same goal e.g. BinaryFormatter.Deserialize and BinaryFormatter.UnsafeDeserialize will both deserialize a stream into a .NET object, but the safe variant will do a full Demand for the appropriate permissions. This ensures that [...]]]></description>
		<link>http://blogs.rev-net.com/ddewinter/2009/06/23/how-to-build-apis-with-transparency-in-mind/</link>
			</item>
	<item>
		<title>Mixing Level 1 and Level 2 Transparency Rules – #16</title>
		<description><![CDATA[Today&#8217;s tip addresses how assemblies using different transparency rules (CLR v2 and CLR v4) interact with each other in the same AppDomain. Remember you can use the SecurityRulesAttribute to specify which level of security rules your assemblies adhere to. The default in .NET 4 is level 2. There are only two cases here—a level 1 [...]]]></description>
		<link>http://blogs.rev-net.com/ddewinter/2009/06/09/mixing-level-1-and-level-2-transparency-rules/</link>
			</item>
	<item>
		<title>The SecurityRulesAttribute &#8211; #15</title>
		<description><![CDATA[The SecurityRulesAttribute is a new attribute class introduced in .NET 4.0 to specify which set of security rules a particular assembly adheres to. The attribute is specified on the assembly level, and allows you to specify two pieces of information. The first and more important piece is the version of transparency that your assembly follows. [...]]]></description>
		<link>http://blogs.rev-net.com/ddewinter/2009/06/08/the-securityrulesattribute/</link>
			</item>
</channel>
</rss>
