<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Upgrading 1.x Projects and Friend Assemblies</title><link>http://weblogs.asp.net/ahoffman/archive/2006/01/27/Upgrading-1.x-Projects-and-Friend-Assemblies.aspx</link><description>I'm finding that one new change required on upgrading a project from .NET 1.x to 2.0 occurs when wanting to make an assembly's internals accessible to another assembly i.e. creating a friend assembly . In .Net 1.x, one might have default project assembly</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Jason Haley - Interesting Finds</title><link>http://weblogs.asp.net/ahoffman/archive/2006/01/27/Upgrading-1.x-Projects-and-Friend-Assemblies.aspx#436743</link><pubDate>Sat, 28 Jan 2006 03:22:00 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:436743</guid><dc:creator>TrackBack</dc:creator><author>TrackBack</author><description>Jason Haley - Interesting Finds&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=436743" width="1" height="1"&gt;</description></item></channel></rss>