April 2006 - Posts

[Cool Tool] WackGet download manager

WackGet Home Page

With WackGet you can select part or all of a web page, hit a hotkey and it will download everything it finds to a user defined download folder.

Posted by dotnetboy2003 | with no comments

Windows PowerShell: The product formerly known as Monad and MSH

[via Greg]

Monad (aka MSH) is now known as Windows PowerShell.

p.s. You can find the MSDN Windows PowerShell Blog here.

Posted by dotnetboy2003 | with no comments

Remove a RootKit... Go to Jail.

[via Michael K. Campbell’s Blog]

Apparently under proposed changes to the DMCA, you might be facing a 10 years of hard time if you attempt to remove copyright protection. 

<snip>

Likewise, any user attempting to remove that rootkit on their own would be violating a law packing 10 years of punishment - whether they succeeded or not. (i.e. just TRYING to remove copyright protection would be a crime, whether you succeeded or not - and in the case of these rootkits, you wouldn't be allowed to even DISCUSS removing them from your machine without technically breaking the law.)

</snip>

Posted by dotnetboy2003 | with no comments

Sharing a Strong Name Key File Across Projects

[via .Net Security Blog]

By default when you add a Strong Name Key to your project, it copies it locally.  Using the “Add as Link” option on the Add Existing Item dialog will allow you to use a shared key with a relative path.

 

Posted by dotnetboy2003 | with no comments

Kirk Allen Evans talks about sorting XML with System.Xml.XPath.XPathExpression

[via Kirk Allen Evan’s Blog]

<snip>

This question came up twice this week, so I thought it warranted a quick post.  If you want to retrieve a sorted list of nodes from an XmlDocument instance, there are a couple ways to do this.  You can use XSLT, or you can write your own sorting algorithm.  The .NET Framework provides capability to provide sort orders to the result of an xpath query through the System.Xml.XPath.XPathExpression::AddSort method.  Here is a simplistic demo:

   20       static void Main( string[] args )

   21       {

   22 

   23          XmlDocument doc = new XmlDocument();

   24          doc.LoadXml( "<a><b>5</b><b>3</b><b>6</b><b>1</b></a>" );

   25          XPathNavigator nav = doc.CreateNavigator();

   26          string path = "/a/b";

   27          XPathExpression expression = nav.Compile( path );

   28          expression.AddSort( "text()", XmlSortOrder.Ascending, XmlCaseOrder.None, string.Empty, XmlDataType.Number );

   29          XPathNodeIterator iterator = nav.Select( expression );

   30          while( iterator.MoveNext() )

   31          {

   32             Console.WriteLine( iterator.Current.Value );

   33          }

   34       }

 

Dan Wahlin maintains an excellent resource site, XML For ASP.NET, to find quick HowTo's on various XML technologies.

</snip>

Posted by dotnetboy2003 | with no comments

Felice Pollano is integrating a debugger in reflector

[Via Mike Stall’s .NET Debugging Blog]

Felice Pollano is building a debugger that leverages Reflector and MDBG.  Check out his screenshot below.  I will  be watching this for when he releases the binaries for this!

<snip>

This post just to share an idea and a work in progress. Leveraging Reflector and MDBG ( a complete managed debugger provided by Microsoft as a sample ) i'm writing a tool that allow to debug without *any* debug infos and use the Reflector disassembler to provide more readable infos on the code. Very useful if we want to dig inside the framework functions.
I cannot yet post the source and the binary, cause the stuff is very poor until now, but let's have a screenshot:
Deblector.png

Please notice that:

  • This is not a Reflector AddIn, but a standalone application using Reflector
  • The debugging API is used wrapped by MDBG classes
  • The actual version need a too extensive uses of manual commands in the shell windows
  • Some times I have some deadlock ( this is the reason I cannot yet post the code )
  • IL Istruction pointer is sometimes MAPPING_APPROXIMATE ( this is a flag returned by the debugger core itself, not my error ) standing for "I cannot say exactly wich il instruction I'm executing at this IP" ( or at least this is actually my interpretation
  • The upper view is IL only, but I guess I will manage to have a mixed one ( Disassembled - IL )
  • When a process is attached, all assemblies were loades in the reflector assembly tree
  • When a breakpoint is detected, the proper function is automatically showed in the reflector disassembler view and in the IL view.
  • Of course, I used Composite UI Application Block to organize the application.

</snip>

Posted by dotnetboy2003 | with no comments
More Posts « Previous page - Next page »