Step 2: Re-Assemble using your strong-name key
        ilasm myTest.il /res:myTest.res /dll /key:myTest.snk /out:myTestSN.dll

This code work perfectly to assign strong name.

for verification you can use following command,
sn -vf myTestSN.dll

Interesting list of VS 2008 code extensions:

http://unhandled-exceptions.com/blog/index.php/2008/07/16/confessions-of-a-developer-tool-hound/

Check these out:

http://www.summerofnhibernate.com/

"Although I feel perfectly comfortable in a set-based world writing SQL, it has traditionally been one of my least favorite areas of coding. Besides being relatively repetitive and tedious, at least when it comes to basic CRUD operations, sprocs are much more difficult to handle when it comes to source control, versioning, debugging, and unit testing."

and

"Regardless of the approach taken, I definitely no longer believe that sprocs should play any significant role in any application."

I couldn't agree more!  Read the full article: http://www.caffeinatedcoder.com/just-say-no-to-manual-crud/

Barry

This is cool:

http://code.google.com/appengine/docs/whatisgoogleappengine.html

<browsers>

   <!--

   Browser capability file for the w3c validator


   sample UA: "W3C_Validator/1.305.2.148 libwww-perl/5.803"

   -->

   <browser id="w3cValidator" parentID="default">

   <identification>

   <userAgent match="^W3C_Validator" />

   </identification>


   <capture>

   <userAgent match="^W3C_Validator/(?'version'(?'major'\d+)(?'minor'\.\d+)\w*).*"
   />

   </capture>


   <capabilities>

   <capability name="browser" value="w3cValidator" />

   <capability name="majorversion" value="${major}" />

   <capability name="minorversion" value="${minor}" />

   <capability name="version" value="${version}" />

   <capability name="w3cdomversion" value="1.0" />

   <capability name="xml" value="true" />

   <capability name="tagWriter" value="System.Web.UI.HtmlTextWriter" /> 
   

   </capabilities>

   </browser>

   </browsers>


   read the whole article at http://idunno.org/archive/2005/01/01/216.aspx 
   

When you add a WMS:Lister control to the actual article template (e.g. a "News Detail" template) the lister may break.  This is because the "ItemIdentifier" attribute is repeated twice on the page!

For example: Say you have an article page that uses <!-- item --> to identify the region of the page the PatternFile refers to, if you then add an actual lister control to the page you end up with two <!-- item --> comments (see below). Once in teh new lister and once for the article!

  <ez:Lister ID="scrollingNews" runat="server" PageSize="4" 
   

        SortBy="Date" SortDirection="Desc" PatternFile="~/NewsPattern.txt"
   ItemFileExtension="*.aspx" 
   

        ItemDirectory="~/News" PagerStyle="None" ItemIdentifier="<!--
   item -->"

        CreateCacheIndex="true" FilterKey="Section" FilterValue="">

        <HeaderTemplate><span id="news_listing"></HeaderTemplate>

        <ItemTemplate>

          <a href="<%# ((ListerItem)Container.DataItem).Link
   %>">

           <wg:PlainText MaxLength="80" Text='<%#
   ((ListerItem)Container.DataItem).GetValue("text") %>' runat="server" />...

          </a>

        </ItemTemplate>

       <FooterTemplate></span></FooterTemplate>

     </ez:Lister>

The fix is simply to leave the ItemIdentifier attribute out of any Lister control.  The default value is <!-- item -->, so you only need the attribute if you need a different value.

:)

Article on:

How to Use Gmail Filters to Organize and Manage your Email Accounts

http://www.dilbert.com/strips/comic/2007-07-30/