Posts Tagged ‘.net’

23 Feb

PowerCommands for Visual Studio 2008

Posted by Jamison White in Personal Blog. Tagged: , , .

Nathan, just sent out a reminder that if you reformat don’t forget this. It has some many little tools that just make sense with out getting in your way.

http://code.msdn.microsoft.com/PowerCommands

PowerCommands 1.1

PowerCommands 1.1 is a set of useful extensions for the Visual Studio 2008 adding additional functionality to various areas of the IDE. The source code is included and requires the VS SDK for VS 2008 to allow modification of functionality or as a reference to create additional custom PowerCommand extensions. Visit the VSX Developer Center at http://msdn.com/vsx for more information about extending Visual Studio.

The Releases page contains download files (MSI installation file, readme document, and source code project).


18 Jun

FileStream v/s StreamReader and StreamWriter

Posted by Jamison White in Programming. Tagged: , , , .

The AppRiver dev team is studying for MSTCS 70-536. These are some observations and notes from those classes.

FileStream v/s StreamReader & StreamWriter

  1. FS supports random access.
  2. FS returns byte arrays.
  3. SR/SW use strings.
  4. If SR/SW is created with a file path instead of a stream, a FS is implicitly created.

When to use them

If you are working with textual information, use a StreamReader/Writer. Use the FileStream for binary data.

If you need to eek out the maximum performance, the FileStream, StreamReader, and StreamWriter all offer optimiztion parameters, but generally you will not need them.

5 Jun

"The breakpoint will not currently be hit" "The source code is different then the original version"

Posted by Jamison White in Programming. Tagged: , , .

Big thanks to ThatOneDeveloper! His post about fixing ASP.Net debugger was a big help.

http://development.thatoneplace.net/2009/04/breakpoint-will-not-currently-be-hit.html

“The breakpoint will not currently be hit. The source code is different then the original version”

…

So to fix the problem:

  1. Close out Visual Studio and make sure any instances of ASP.NET development server are closed as well.
  2. Delete everything from “C:\Windows\Microsoft.NET\Framework\v.2.0.50727\Temporary ASP.NET Files” (where v.2.0.50727 is the version of the .NET Framework your site is running on.)

cat
see more Lolcats and funny pictures