<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>LifeCycle Solutions, LLC - Weblog - Documentation</title>
    <link>http://blog.lifecycle-solutions.com/</link>
    <description>Technical Writing</description>
    <language>en-us</language>
    <copyright>LifeCycle Solutions, LLC</copyright>
    <lastBuildDate>Tue, 20 Feb 2007 14:49:16 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 2.2.8279.16125</generator>
    <managingEditor>info@lifecycle-solutions.com</managingEditor>
    <webMaster>info@lifecycle-solutions.com</webMaster>
    <item>
      <trackback:ping>http://blog.lifecycle-solutions.com/Trackback.aspx?guid=5589150e-e518-45ff-a0a3-b74e8ddba757</trackback:ping>
      <pingback:server>http://blog.lifecycle-solutions.com/pingback.aspx</pingback:server>
      <pingback:target>http://blog.lifecycle-solutions.com/PermaLink,guid,5589150e-e518-45ff-a0a3-b74e8ddba757.aspx</pingback:target>
      <dc:creator>Daniel Root</dc:creator>
      <wfw:comment>http://blog.lifecycle-solutions.com/CommentView,guid,5589150e-e518-45ff-a0a3-b74e8ddba757.aspx</wfw:comment>
      <wfw:commentRss>http://blog.lifecycle-solutions.com/SyndicationService.asmx/GetEntryCommentsRss?guid=5589150e-e518-45ff-a0a3-b74e8ddba757</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <img style="FLOAT: right; MARGIN: 1em" src="http://blog.lifecycle-solutions.com/content/binary/ReflectorScreenshot.png" border="0" />
        <p>
One of the most useful tools for .NET development is <a href="http://www.aisto.com/roeder/dotnet/">Lutz
Roeder's .NET Reflector</a>, now in version 5.  It uses reflection to peek inside
.NET assemblies and disassembles the IL back into C# or VB code for those times that
you need an in-depth look into <em>any</em> .NET library.  Ever wonder what
the code for System.String looked like? This release adds some really nice
features:
</p>
        <ul>
          <li>
Formatted code comments- doubles as a documentation browser for XML code-commented
members 
</li>
          <li>
'Expand members' in disassembler lets you see code for an entire class at once-
previously you had to look at each method separately. 
</li>
          <li>
New analyzer features shows where classes are instantiated and exposed. 
</li>
          <li>
Search Google or MSDN for a member</li>
        </ul>
        <p>
In addition to helping you debug code, this is also a great learning tool.  What
better way to understand framework development than to peek inside The Framework itself?
</p>
        <p>
 
</p>
        <p>
 
</p>
        <img width="0" height="0" src="http://blog.lifecycle-solutions.com/aggbug.ashx?id=5589150e-e518-45ff-a0a3-b74e8ddba757" />
      </body>
      <title>Essential Tool: Lutz Roeder's .NET Reflector v5</title>
      <guid isPermaLink="false">http://blog.lifecycle-solutions.com/PermaLink,guid,5589150e-e518-45ff-a0a3-b74e8ddba757.aspx</guid>
      <link>http://blog.lifecycle-solutions.com/2007/02/20/EssentialToolLutzRoedersNETReflectorV5.aspx</link>
      <pubDate>Tue, 20 Feb 2007 14:49:16 GMT</pubDate>
      <description>&lt;img style="FLOAT: right; MARGIN: 1em" src="http://blog.lifecycle-solutions.com/content/binary/ReflectorScreenshot.png" border=0&gt; 
&lt;p&gt;
One of the most useful tools for .NET development is&amp;nbsp;&lt;a href="http://www.aisto.com/roeder/dotnet/"&gt;Lutz
Roeder's .NET Reflector&lt;/a&gt;, now in version 5.&amp;nbsp; It uses reflection to peek inside
.NET assemblies and disassembles the IL back into C# or VB code for those times that
you need an in-depth look into &lt;em&gt;any&lt;/em&gt;&amp;nbsp;.NET library.&amp;nbsp; Ever wonder&amp;nbsp;what
the code for System.String looked like?&amp;nbsp;This&amp;nbsp;release adds some really&amp;nbsp;nice
features:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
Formatted code comments- doubles as a documentation browser for XML code-commented
members 
&lt;li&gt;
'Expand members' in disassembler lets you see code for&amp;nbsp;an entire class at once-
previously you had to look at each method separately. 
&lt;li&gt;
New analyzer features shows where classes are instantiated and exposed. 
&lt;li&gt;
Search Google or MSDN for a member&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
In addition to helping you debug code, this is also a great learning tool.&amp;nbsp; What
better way to understand framework development than to peek inside The Framework itself?
&lt;/p&gt;
&lt;p&gt;
&amp;nbsp;
&lt;/p&gt;
&lt;p&gt;
&amp;nbsp;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://blog.lifecycle-solutions.com/aggbug.ashx?id=5589150e-e518-45ff-a0a3-b74e8ddba757" /&gt;</description>
      <comments>http://blog.lifecycle-solutions.com/CommentView,guid,5589150e-e518-45ff-a0a3-b74e8ddba757.aspx</comments>
      <category>ASP.NET</category>
      <category>C#</category>
      <category>Documentation</category>
      <category>Patterns and Practices</category>
      <category>Training</category>
      <category>Visual Studio</category>
    </item>
    <item>
      <trackback:ping>http://blog.lifecycle-solutions.com/Trackback.aspx?guid=e0abb29b-997d-4b06-be56-7af26676d63d</trackback:ping>
      <pingback:server>http://blog.lifecycle-solutions.com/pingback.aspx</pingback:server>
      <pingback:target>http://blog.lifecycle-solutions.com/PermaLink,guid,e0abb29b-997d-4b06-be56-7af26676d63d.aspx</pingback:target>
      <dc:creator>Daniel Root</dc:creator>
      <wfw:comment>http://blog.lifecycle-solutions.com/CommentView,guid,e0abb29b-997d-4b06-be56-7af26676d63d.aspx</wfw:comment>
      <wfw:commentRss>http://blog.lifecycle-solutions.com/SyndicationService.asmx/GetEntryCommentsRss?guid=e0abb29b-997d-4b06-be56-7af26676d63d</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
Ever wondered what a secure ASP.NET 2.0 application should look like?  The <a href="http://blogs.msdn.com/jmeier/archive/2006/07/20/672959.aspx">ASP.NET
Internet Security Reference Implementation</a> rolls all of the <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/SecurityGuidanceIndex.asp">Patterns
and Practices Security Guidance</a> into real-world sample application, complete with
full documentation about all of the security features, why and how they were
implemented, and the drawbacks to doing so.
</p>
        <p>
If you are doing ASP.NET 1.1 or 2.0 web design, you should download this, read through
it, and check out the code.  While the code is 2.0, all of the security concepts-
and some of the solutions- map to 1.1 apps as well.
</p>
        <p>
One note: it installs into C:\Program Files\Microsoft\Internet Security Reference
Implementation by default.  It took me forever to find it!
</p>
        <img width="0" height="0" src="http://blog.lifecycle-solutions.com/aggbug.ashx?id=e0abb29b-997d-4b06-be56-7af26676d63d" />
      </body>
      <title>ASP.NET 2.0 Internet Security Reference Implementation</title>
      <guid isPermaLink="false">http://blog.lifecycle-solutions.com/PermaLink,guid,e0abb29b-997d-4b06-be56-7af26676d63d.aspx</guid>
      <link>http://blog.lifecycle-solutions.com/2006/08/23/ASPNET20InternetSecurityReferenceImplementation.aspx</link>
      <pubDate>Wed, 23 Aug 2006 21:51:30 GMT</pubDate>
      <description>&lt;p&gt;
Ever wondered what a secure ASP.NET 2.0 application should look like?&amp;nbsp; The &lt;a href="http://blogs.msdn.com/jmeier/archive/2006/07/20/672959.aspx"&gt;ASP.NET
Internet Security Reference Implementation&lt;/a&gt; rolls all of the &lt;a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/SecurityGuidanceIndex.asp"&gt;Patterns
and Practices Security Guidance&lt;/a&gt; into real-world sample application, complete with
full documentation about all of the security features, why and how&amp;nbsp;they were
implemented, and the drawbacks to doing so.
&lt;/p&gt;
&lt;p&gt;
If you are doing ASP.NET 1.1 or 2.0 web design, you should download this, read through
it, and check out the code.&amp;nbsp; While the code is 2.0, all of the security concepts-
and some of the solutions-&amp;nbsp;map to 1.1 apps as well.
&lt;/p&gt;
&lt;p&gt;
One note: it installs into C:\Program Files\Microsoft\Internet Security Reference
Implementation by default.&amp;nbsp; It took me forever to find it!
&lt;/p&gt;
&lt;img width="0" height="0" src="http://blog.lifecycle-solutions.com/aggbug.ashx?id=e0abb29b-997d-4b06-be56-7af26676d63d" /&gt;</description>
      <comments>http://blog.lifecycle-solutions.com/CommentView,guid,e0abb29b-997d-4b06-be56-7af26676d63d.aspx</comments>
      <category>ASP.NET</category>
      <category>Documentation</category>
      <category>Patterns and Practices</category>
    </item>
    <item>
      <trackback:ping>http://blog.lifecycle-solutions.com/Trackback.aspx?guid=ee0fc947-ac38-4406-8b27-0f1416fcdae6</trackback:ping>
      <pingback:server>http://blog.lifecycle-solutions.com/pingback.aspx</pingback:server>
      <pingback:target>http://blog.lifecycle-solutions.com/PermaLink,guid,ee0fc947-ac38-4406-8b27-0f1416fcdae6.aspx</pingback:target>
      <dc:creator>Daniel Root</dc:creator>
      <wfw:comment>http://blog.lifecycle-solutions.com/CommentView,guid,ee0fc947-ac38-4406-8b27-0f1416fcdae6.aspx</wfw:comment>
      <wfw:commentRss>http://blog.lifecycle-solutions.com/SyndicationService.asmx/GetEntryCommentsRss?guid=ee0fc947-ac38-4406-8b27-0f1416fcdae6</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">Rumor is going around the blogosphere that <a href="http://www.charliedigital.com/PermaLink,guid,95b2ab68-ba92-413a-b758-2783cde5df9c.aspx"><i>the </i>.NET
Documentation application is no longer going to be developed</a>.  There's still
a chance that someone could pick it up, but Microsoft is planning to release the application
they use internally to do MSDN documentation.  Watch the <a href="http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=66&amp;SiteID=1">Developer
Documentation Forum</a> for more news on 'Sandcastle'.<br /><p></p><img width="0" height="0" src="http://blog.lifecycle-solutions.com/aggbug.ashx?id=ee0fc947-ac38-4406-8b27-0f1416fcdae6" /></body>
      <title>NDoc Project Dead (or Stalled)</title>
      <guid isPermaLink="false">http://blog.lifecycle-solutions.com/PermaLink,guid,ee0fc947-ac38-4406-8b27-0f1416fcdae6.aspx</guid>
      <link>http://blog.lifecycle-solutions.com/2006/07/27/NDocProjectDeadOrStalled.aspx</link>
      <pubDate>Thu, 27 Jul 2006 16:06:20 GMT</pubDate>
      <description>Rumor is going around the blogosphere that &lt;a href="http://www.charliedigital.com/PermaLink,guid,95b2ab68-ba92-413a-b758-2783cde5df9c.aspx"&gt;&lt;i&gt;the &lt;/i&gt;.NET
Documentation application is no longer going to be developed&lt;/a&gt;.&amp;nbsp; There's still
a chance that someone could pick it up, but Microsoft is planning to release the application
they use internally to do MSDN documentation.&amp;nbsp; Watch the &lt;a href="http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=66&amp;amp;SiteID=1"&gt;Developer
Documentation Forum&lt;/a&gt; for more news on 'Sandcastle'.&lt;br&gt;
&lt;p&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://blog.lifecycle-solutions.com/aggbug.ashx?id=ee0fc947-ac38-4406-8b27-0f1416fcdae6" /&gt;</description>
      <comments>http://blog.lifecycle-solutions.com/CommentView,guid,ee0fc947-ac38-4406-8b27-0f1416fcdae6.aspx</comments>
      <category>Documentation</category>
    </item>
  </channel>
</rss>