Huddled Masses » .Net http://huddledmasses.org You can do more than breathe for free... Fri, 27 Apr 2012 05:42:40 +0000 en hourly 1 http://wordpress.org/?v=3.3.2 XamlReader and Resource Library fonts in WPF http://huddledmasses.org/xamlreader-and-resource-library-fonts-in-wpf/ http://huddledmasses.org/xamlreader-and-resource-library-fonts-in-wpf/#comments Thu, 30 Aug 2007 05:15:16 +0000 Joel 'Jaykul' Bennett http://HuddledMasses.org/jaykul/xamlreader-and-resource-library-fonts-in-wpf/ Microsoft has provided some very good documentation on how to package fonts with WPF applications, and I’ve been following it in several different ways in different apps I’ve written. Recently I provided a feature in Posh Console which allows you to load the startup banner from an external file: StartupBanner.xaml.

Loading the banner from an external XAML file means that users can configure their own startup banner and make it look however they like, but it broke our default banner. The startup banner we’ve been using has a logo and some text which are all defined in pure XAML and uses several fonts which we had embedded in a FontLibrary.dll resource assembly. It worked great as long as the XAML was defined in the application, but as soon as we removed it to an external file and loaded it in using the XamlReader.Load method, the fonts all went to the fallback default fonts instead of our embedded ones.

Normally this might not be a big deal, but since our logo is based on the “Q” in a Quake-like font … it looks really lame without fonts. :D Apparently, when you load external XAML, it can’t use the Font Resource Library resources. At this point, I can’t seem to find anything to indicate why this is the case, but I suspect it has to do with the fact that the external, loaded XAML only has partial trust, and since the font is in an external assembly instead of embedded in the partial trust content, it can’t get to it. However, it might be simpler than that: it might just be that the base URI for the externally loaded XAML is an actual file location rather than one of the pack://,,,application/ type URIs, so the slightly odd font path doesn’t resolve.

In any case, I found a way around it, which is of course, why I’m writing all of this down. :) If you declare WPF resources in your project, you can inject them into the WPF objects loaded from the XAML to make them available to them. So for instance, I have a font called “Quake” in the FontLibrary assembly. I can declare it as a resource in my application’s XAML (at the app level, window level, or wherever).

<Style x:Key="POSHFont">
  <Setter Property="TextElement.FontFamily" Value="/FontLibrary;Component/#QUAKE" />
</Style>

The font in that style gets resolved in full trust with the pack URI, and it works fine when used from my application. Having created that, I can do the same thing in the external XAML files, and apply the style to the text as a DynamicResource … and even feel free to override parts of the style if I want to. For instance, even though the style might specify a FontSize, if I refer to the style on this text block and specify my own FontSize, the one that’s on the TextBlock (or Paragraph, or Run, or whatever) will be used. Now, we’re not quite done yet, because although they look the same in source, the fonts won’t resolve properly in the externally loaded XAML.

<TextBlock TextAlignment="Center" Width="180" Style="{DynamicResource POSHFont}" FontSize="145" Foreground="#FF3275B9">
  <TextBlock.BitmapEffect>
    <BevelBitmapEffect BevelWidth="1" EdgeProfile="CurvedOut" LightAngle="258" Relief="0.03" Smoothness="0.565"/>
  </TextBlock.BitmapEffect>Q
 </TextBlock>

However, because the style is specified as a dynamic resource rather than a static one, I don’t have to define that resource at all in that XAML file, but even if I do, when I load the XAML into my application, I can simply set it’s resources from the resources that I’ve loaded in full trust and with the pack:// base URI... In my case, I have actually defined several fonts as resources on a Document element, so I just copy them all into the element I read in from the XAML file:

Paragraph banner = (Paragraph)XamlReader.Load(System.Xml.XmlReader.Create("StartupBanner.xaml"));
if (banner != null)
{
  // Copy over resources from my DOCUMENT to the BANNER
  foreach (string key in Document.Resources.Keys) {
      banner.Resources[key] = Document.Resources[key];
  }
  Document.Blocks.Add(_currentParagraph);
}

And that’s it: PoshConsole Banner

]]> http://huddledmasses.org/xamlreader-and-resource-library-fonts-in-wpf/feed/ 4 PowerShell Host and Custom Formatting http://huddledmasses.org/powershell-host-and-custom-formatting/ http://huddledmasses.org/powershell-host-and-custom-formatting/#comments Thu, 30 Aug 2007 00:01:09 +0000 Joel 'Jaykul' Bennett http://HuddledMasses.org/jaykul/powershell-host-and-custom-formatting/ So, I’ve been working on PoshConsole for awhile now, and with the help of some of the guys in #PowerShell@irc.freenode.net have been playing with trying to find ways to enhance output, like using ANSI escape sequences, and even creating an Out-WPF cmdlet which can output objects as databound WPF controls which look really good.

We have been trying to find a way to incorporate the colored and even bold/italic formatting in a way that would be compatible with the existing format-* cmdlets, and we’ve even looked at replacing out-default with a cmdlet that would be compatible with the default PowerShell host. But today I finally locked in on the import of this post on the PowerShell blog. It’s just not possible.

The format cmdlets (Format-List, Format-Custom, Format-Table, Format-Wide) output data in the form of undocumented .Net objects which are “subject to change without notice,” and are therefore basically useless. Of course, that means that if you want to replace Out-Default you have to not only replace the output, but you have to replace the formatting cmdlets, and of course the Update-FormatData cmdlet too — in fact, you have to either parse the largely undocumented format data files, or create some replacement for them to allow users to specify formatting for types you haven’t thought of…

All of this amounts to what many of you probably already knew: it’s a lot of work to create a complete PowerShell host, but it’s at least as much work to create a replacement PowerShell formatter.

]]> http://huddledmasses.org/powershell-host-and-custom-formatting/feed/ 0 A quick progress update on PoshConsole http://huddledmasses.org/a-quick-progress-update-on-poshconsole/ http://huddledmasses.org/a-quick-progress-update-on-poshconsole/#comments Tue, 21 Aug 2007 05:10:43 +0000 Joel 'Jaykul' Bennett http://HuddledMasses.org/jaykul/a-quick-progress-update-on-poshconsole/ Click for a teaser screenshot

This is actually a bit scary, because you can load sort-of … anything ;-) To prove it (you’re gonna love this … I should take a video, really, but it’s time for bed, so this will have to do): check this out Beat that! ;)

So yeah, I have this control written from an earlier project which creates a task list with live preview images. When I say “live previews” I mean actually live, like on the Vista Alt+Tab: if there’s a video playing, you can watch it in there (of course, it dies a horrible death on XP, but I have other code for that).

As a side note the TaskBar2.panel stuff is from the TINS release I made months ago, there’s several fun .panel files in there … but you have to load a bunch of the TINS assemblies first, I didn’t distinguish which ones, I just did:


cd C:\Users\Joel\Projects\TechDemos\TINS\bin\Release
ls *.dll,*.exe | % { [System.Reflection.Assembly]::LoadFrom($_) }
$Host.PrivateData.XamlUI.LoadXaml("C:\Users\Joel\Projects\TechDemos\TINS\bin\Release\Panels\TaskBar2.panel");
 

Of course, in .Net 3.5 the RichTextBox has the ability to go ContentEnabled="true" which should allow those things to be actual controls you can click to switch active task, right-click to get a task menu, etc (although I haven’t tried that yet). We might just have to upgrade ;-)

Anyway, it’s past time for bed, so I’ll preempt complaints about how this isn’t ready for release yet with this quote:

I don’t have to take this abuse from you; I’ve got hundreds of people waiting to abuse me. — Bill Murray, “Ghostbusters”

]]> http://huddledmasses.org/a-quick-progress-update-on-poshconsole/feed/ 0 Extending strings, and secure strings, in PowerShell. http://huddledmasses.org/extending-strings-and-secure-strings-in-powershell/ http://huddledmasses.org/extending-strings-and-secure-strings-in-powershell/#comments Wed, 06 Jun 2007 03:40:07 +0000 Joel 'Jaykul' Bennett http://HuddledMasses.org/jaykul/extending-strings-and-secure-strings-in-powershell/ One of the coolest things about scripting in PowerShell is that they’ve enabled the addition of extension methods to any class (object). Essentially, this means that you can add whatever methods This enables all sorts of utility functions that would normally end up in a library to instead be added to the base objects. Just for example, this week I was working on a script that needed to do HTTP basic authentication, which requires Base64 encoding a string. Now, that’s not very hard to do, really:


$name = "Joel Bennett"
$encoded = [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes( $name ))
 

But really, that’s kind of a pain to remember, nevermind type each time. I mean, tab-completion helps, but what with all the square brackets and double-colons … So, instead, wouldn’t it be cool if I could just take my original string and call $name.AsBase64? Well, I can, with a pretty simple custom type.


<Types>
  <Type>
    <Name>System.String</Name>
    <Members>
      <ScriptProperty>
        <Name>AsBase64</Name>
        <GetScriptBlock>
          [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes($this))
        </GetScriptBlock>
      </ScriptProperty>
      <ScriptProperty>
        <Name>FromBase64</Name>
        <GetScriptBlock>
          [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($this))
        </GetScriptBlock>
      </ScriptProperty>
    </Members>
  </Type>
</Types>
 

We take this XML, put it in a file with the .ps1xml extension, and then call Update-TypeData MyTypes.ps1xml … Now we can call .AsBase64 or .FromBase64 on any string.

So then I ran into this simple problem. I wanted (in my script) to have the user type a password in… but not have it show up in their console. It turns out there’s a very over-engineered, and extremely elegant solution for this in PowerShell: Read-Host -AsSecureString "Prompt". It’s exactly what I wanted, in that it results in the console showing ***** as you type your password in. The only problem is, what you get out is a System.Security.SecureString which is essentially … well, useless. ;)

Honestly, I know that there are times when you need to store a string in such a way that it’s encrypted even in memory … but the fact is that it’s complicated to get the text value back out, so it really isn’t very useful. Anyway, you could add this to your custom types file:


  <Type>
    <Name>System.Security.SecureString</Name>
    <Members>
      <ScriptProperty>
        <Name>AsInsecureString</Name>
        <GetScriptBlock>
          $BSTR = [System.Runtime.InteropServices.marshal]::SecureStringToBSTR($this)
          [System.Runtime.InteropServices.marshal]::PtrToStringAuto($BSTR)
          [System.Runtime.InteropServices.Marshal]::ZeroFreeBSTR($BSTR)
        </GetScriptBlock>
      </ScriptProperty>
    </Members>
  </Type>
 

But then, of course … it wouldn’t be very secure anymore. The point of extending types instead of writing script libraries is that you want things to be discoverable, and a property that exposes a secure string as a regular string probably isn’t really something you wanted to make discoverable ;) .

For my purposes, I decided that was a bad idea, and settled on adding this function to my regular library of functions:


function Read-HostMasked([string]$prompt="Password") {
  $password = Read-Host -AsSecureString $prompt;  
  $BSTR = [System.Runtime.InteropServices.marshal]::SecureStringToBSTR($password);
  $password = [System.Runtime.InteropServices.marshal]::PtrToStringAuto($BSTR);
  [System.Runtime.InteropServices.Marshal]::ZeroFreeBSTR($BSTR);
  return $password;
}
 

That lets you take advantage of the in-console masking, but returns a plain old string into your script so you can use it easily. (In my case, I wanted to handle HTTP Basic Authorization using System.Net.WebClient so I did something like: $webclient.Headers.Add("Authorization", "Basic "+((Read-Host Username)+':'+(Read-HostMasked Password)).AsBase64). Hopefully that makes it obvious how that Read-HostMasked function works and why it’s useful.

So. If anyone knows a better way to get a password from the user interactively without showing it on the console, I’m all ears! I’m not worried about having it in memory, in this case — in fact, I’m not even storing it, just passing it to the Base64 encoding … and I can’t avoid that.

Technorati Tags: , , ,

]]> http://huddledmasses.org/extending-strings-and-secure-strings-in-powershell/feed/ 0 PowerShell speaks http://huddledmasses.org/powershell-speaks/ http://huddledmasses.org/powershell-speaks/#comments Thu, 03 May 2007 03:34:00 +0000 Joel 'Jaykul' Bennett http://HuddledMasses.org/jaykul/powershell-speaks/ So, a buddy was showing off the “say” command in the Mac OS X terminal the other day (my 3 year old daughter was vastly entertained) and I wondered what it would take to do the same thing in Windows PowerShell … it turns out the answer is, not much. :) You just type this into the console:


$Voice = new-object -com SAPI.SpVoice
$Voice.Speak( "Hello World!", 1 )
 

The cool thing about this is that it’s async, unlike the Mac “say” command, so you can go on typing the next command while it’s speaking. On top of that, you can have it read a text file by just changing that 1 to a 5:


$Voice = new-object -com SAPI.SpVoice
$Voice.Speak( "C:\Text\HolyGrail.txt", 5 )
 

Now, being who I am, and what I am, I wasn’t content with that, so I wrote myself up a script, Out-Speech, that will speak whatever it’s given (an array of objects as an argument, or the pipeline objects … ) and exposes most of the options of the underlying Speech API.

I’ll post the code here, but I thought I’d just mention … I’m not really using this in very many places, but it’s really fun with the Select-Random script I posted earlier. I alias that to “rand” and this to “say” ... so I can do: cat quotes.txt | rand | say How fun is that? Yeah, well, or you could use it to report on the progress of long-running scripts, or something else more useful. :-|


# Out-Speech
param([array]$Collection, [switch]$wait, [switch]$purge, [switch]$readfiles, [switch]$readxml, [switch]$notxml)

begin
{  
  if ($args -eq '-?') {
''
'Usage: Out-Speech [[-Collection] <array>]'
''
'Parameters:'
'    -Collection : A collection of items to speak.'
'    -?          : Display this usage information'
'  Switches:'
'    -wait       : Wait for the machine to read each item (NOT asynchronous).'
'    -purge      : Purge all other speech requests before making this call.'
'    -readfiles  : Read the contents of the text files indicated.'
'    -readxml    : Treat input as speech XML markup.'
'    -notxml     : Do NOT parse XML (if text starts with "<" but is not XML).'
''
'Examples:'
'    PS> Out-Speech "Hello World"'
'    PS> Select-RandomLine quotes.txt | Out-Speech -wait'
'    PS> Out-Speech -readfiles "Hitchhiker''s Guide To The Galaxy.txt"'
''
      exit
  }
   
   
  # To override this default, use the other flag values given below.
  $SPF_DEFAULT = 0          # Specifies that the default settings should be used.  
    ## The defaults are:
    #~ * Speak the given text string synchronously
    #~ * Not purge pending speak requests
    #~ * Parse the text as XML only if the first character is a left-angle-bracket (<)
    #~ * Not persist global XML state changes across speak calls
    #~ * Not expand punctuation characters into words.
  $SPF_ASYNC = 1            # Specifies that the Speak call should be asynchronous.
  $SPF_PURGEBEFORESPEAK = 2 # Purges all pending speak requests prior to this speak call.
  $SPF_IS_FILENAME = 4      # The string passed is a file name, and the file text should be spoken.
  $SPF_IS_XML = 8           # The input text will be parsed for XML markup.
  $SPF_IS_NOT_XML= 16       # The input text will not be parsed for XML markup.
 
 
  $SPF = $SPF_DEFAULT
  if(!$wait){ $SPF += $SPF_ASYNC }
  if($purge){ $SPF += $SPF_PURGEBEFORESPEAK }
  if($readfiles){ $SPF += $SPF_IS_FILENAME }
  if($readxml){ $SPF += $SPF_IS_XML }
  if($notxml){ $SPF += $SPF_IS_NOT_XML }
 
  $Voice = new-object -com SAPI.SpVoice
 
  if ($collection.count -gt 0) {
    foreach( $item in $collection ) {
      $exit = $Voice.Speak( ($item | out-string), $SPF )
    }
  }
}

process
{
  if ($_)
  {
    $exit = $Voice.Speak( ($_ | out-string), $SPF )
  }
}

 
]]> http://huddledmasses.org/powershell-speaks/feed/ 0 Silverlight Streaming, Silverlight CLR, Data Services, Ozzie, and IE 8 http://huddledmasses.org/silverlight-streaming-silverlight-clr-data-services-ozzie-and-ie-8/ http://huddledmasses.org/silverlight-streaming-silverlight-clr-data-services-ozzie-and-ie-8/#comments Tue, 01 May 2007 21:40:36 +0000 Joel 'Jaykul' Bennett http://HuddledMasses.org/jaykul/silverlight-streaming-silverlight-clr-data-services-ozzie-and-ie-8/ Microsoft made several big announcements today at MIX07…

CLR in Silverlight

The most exciting announcement I’ve today is that Silverlight will include the Common Language Runtime (CLR) on both Windows and Mac … which means that it will allow development using any .NET-supported languages. They’re even including the open source Dynamic Language Runtime and thus IronRuby (which like IronPython is also open source).

On top of that, these features, plus support for Language Integrated Query language (LINQ) and cross-platform debugging capabilities, are available now in the Silverlight 1.1 Alpha (and will be released more publicly after Silverlight 1.0 comes out this summer?).

Silverlight Streaming

They also announced today that they will offer a media-hosting service for free called Silverlight Streaming! In a move that targets both Adobe’s flash and other media-hosting sites like YouTube and Revver … they will allow developers to stream high -quality video (up to DVD quality) into their Silverlight apps from Microsoft’s servers without any restrictions on branding or embedding (including use in “rich internet applications” — i.e.: outside the browser).

The current package in pre-release offers only 4GB of storage and unlimited bandwidth delivery of up to DVD quality video (700 Kbps), but their plan calls for Microsoft to provide hosting for unlimited Silverlight content and up to a million minutes of free video streaming at 700 Kpbs per site per month … that’s over 5,000 Gigabytes of bandwidth)+*+700+Kbps)+in+gigabytes of streaming per month, for free! They’ll also offer unlimited streaming for a fee, or free, but supported by advertising…

Jasper and Astoria CTPs

Astoria builds on ADO.NET and WCF to allows you to expose a data service for the web which can be consumed via HTTP and since it uses standard HTTP verbs (GET, POST, DELETE, etc) you can even make it accessible as a REST-style resource collection with unique URIs … and simple formats like JSON or plain XML ...

Jasper is another ADO.NET incubation project … aimed at dynamically typed .Net languages like VB.Net or IronPython … it dynamically generates data classes (instead of requiring manual, static configuration … or even code generation which must be kept up to date). It’s built on the Entity Framework (which was postponed until some time in 2008 … after Orcas ships), so it supports rich queries and object-relational mapping and automatic databinding.

Ozzie speaks on Services and Clients…

The orchestration of announcements has many people buzzing about strong leadership and strategy … and the keynote by Ray Ozzie left no doubt about who’s behind that, highlighting the work Microsoft is doing to integrate all the various aspects of their strategy. Ozzie pitched Software-as-a-Service (SaaS) 2.0: web and hosted services which have “grown to embrace the uniquely valuable role of the client.”

IE 8 will require Standards Mode

In a move that only the undisputed king of browsers could hope to pull off, Microsoft has announced that they’ll be requiring web developers to opt in to standards-compliant web design … feel free to take a moment to check for flying pigs.

They’re also planning on making the IE object model more interoperable with other browsers and provide more client-side APIs — including local storage for AJAX apps and more extensibility in the form of a plugin API. Look for it in 2008.

]]> http://huddledmasses.org/silverlight-streaming-silverlight-clr-data-services-ozzie-and-ie-8/feed/ 0 What I learned today [17-Apr-2007] about [PowerShell] http://huddledmasses.org/what-i-learned-today-about-powershell/ http://huddledmasses.org/what-i-learned-today-about-powershell/#comments Tue, 17 Apr 2007 18:42:53 +0000 Joel 'Jaykul' Bennett http://HuddledMasses.org/jaykul/what-i-learned-today-about-powershell/ I’ve been playing more with PowerShell lately, and there’s some really cool stuff in there! I though I’d post a few of my favorite discoveries. Generally speaking these are PowerShell user tips and tricks, because I’ve already been using PowerShell for a while, but since this is a “what I learned today” post, I’m not going to go back and write about the basics (besides, lots of other people are doing that already).

When you’re writing a PowerShell function, there is a method param which you can use to specify the parameters that the function accepts, including specifying their type, and their default value(s).

When you’re specifying types, you do so in square brackets like [System.Int32] but there are Type Shortcuts defined for the most common types, and even better, if you’re typing in PowerShell, you get tab-completion for them (even for the .Net types).

PowerShell includes a special type: [switch] which is for functions and scripts to take a command line parameter that is false by default (ie: it defaults to $false) and which doesn’t require any value on the command line (if you specify it, then it’s true). So for instance, if you had a script named “RandomLine” that looked like this:


param([switch]$Quiet, [string]$fileName='C:\Users\Joel\Documents\Quotes\attributed quotes.txt')

$line = Get-Content ( $fileName ) | Select-Random
Set-Clipboard -Text $line
if(!$Quiet) { "Clipboard set to:`n$line" }
 

You could call it by just writing RandomLine or you could suppress the message at the end (a plain string in PowerShell is equivalent to C# Console.WriteLine or a bash echo) by just specifying RandomLine -Quiet without needing to specify the value as $false.

Parameter names are not case sensitive, and don’t have to be fully typed out (as long as you type enough that the system can tell which one you mean), so you can actually call that script earlier as: RandomLine -q or RandomLine -q:$true -f:"C:\Users\Joel\Documents\Quotes\children's wisdom.txt"

Oh, and that script … depends on this other script:



param([array]$Collection)
 
begin {
    $result = $Seed
   
    if ($args -eq '-?') {
        ''
        'Usage: Select-Random [[-Collection] <array>]'
        ''
        'Parameters:'
        '    -Collection : The collection from which to select a random entry.'
        '    -?          : Display this usage information'
        ''
        'Examples:'
        '    PS> $arr = 1..5; Select-Random $arr'
        '    PS> 1..5 | Select-Random'
        ''
        exit
    }
 
    $coll = @()
    if ($collection.count -gt 0) {
        $coll += $collection
    }
}
 
process {
    if ($_) {
        $coll += $_;
    }
}
 
end {
    if ($coll) {
        $randomIndex = Get-Random -Min 0 -Max ($coll.Count)
        $coll[$randomIndex]
    }
}
 

Which actually depends on Get-Random, which is one of the PowerShell Community Extensions available on CodePlex.

Technorati Tags: , , , ,

]]> http://huddledmasses.org/what-i-learned-today-about-powershell/feed/ 0 Downloads for Visual Studio http://huddledmasses.org/downloads-for-visual-studio/ http://huddledmasses.org/downloads-for-visual-studio/#comments Mon, 18 Dec 2006 21:04:03 +0000 Joel 'Jaykul' Bennett http://HuddledMasses.org/jaykul/downloads-for-visual-studio/ Well, the latest news is that Visual Studio 2005 SP1 is available, which finally includes official support for running Visual Studio on Windows Vista [o.o], as well as for “Web Application” projects in VS2005 — which means you have to uninstall the previous web application project add-in.

While I’m writing about Visual Studio, and since I just had to reinstall Visual Studio and all my other tools on my new computer (yes, in Windows Vista), I figured I would point out some of the other add-ins that I depend on, as well as a few cool new downloads.

The Visual Studio Power Toys are a collection of addins and developer tools including ILMerge, VS Command Shell, the XML Notepad and more. In fact, MSBee — which I use regularly at work — is a one of the power toys. It allows you to develop applications that target the .NET Framework 1.1 in Visual Studio 2005. VS Window Manager is also a power toy, it allows you to save named layout presets which remember your window positions and auto-hide status… and even change automatically between layouts. There’s also a new power toy which sounds really nice, but that I haven’t had a chance to try yet: the Resource Refactoring tool which lets you extract hard-coded strings from code into resource files in C#, VB.NET and even web projects.

Anyway, the reason I started to mention the power toys is that they now have a Power Toys Pack Installer which aims to let you install some or all of these from a single installer interface. I just wish other people could publish their add-ins so they could be included in this thing — it sure would make this new setup process easier, especially if they could check for updates…

Another add-in I depend on is Roland Weigelt’s GhostDoc which makes keeping my documentation up-to-date much easier, especially because of his support for interfaces and inheritance. One pointer: if you install GhostDoc on Vista, (actually, this applies to 90% of these developer tools) make sure you run the installer as administrator or from a console with administrator access, because otherwise the installers sometimes fail, or worse, they appear to work but result in non-functioning installs.

I also use:

  • TestDriven.NET which is an nUnit unit testing addin which I use at home, and actually still use at work, because we haven’t upgraded to the full Team Studio versions and testing.
  • SmartPaster is for pasting string literals into code, and I find it particularly useful for pasting in SQL queries.
  • CopySourceAsHTML does what it says … with lots and lots of options. Although it’s invaluable when you need it … I don’t use it as much as the others, so I tend to forget to install it until weeks later when I suddenly try to use it and it’s not there.c
  • ImageVisualizer lets you see the image contained in a bitmap during debugging.
  • RegexVisualizer lets you visualize and edit “Regex”, “Match” and “MatchCollection” objects at debug-time. Very nice.

Oh, and while I’m at it … there’s a short stack of other add-ins that I still need to try out (in rough order of how excited I am about them).

  • XPathMania adds proper XPath query support to Visual Studio so you can test your XPath statements against the current document in the XML editor, this is something I’ve been needing for a while.
  • SiteMap Editor provides a structured UI for editing sitemap XML.
  • SmartOutline enhances the “region” capability of Visual Studio to allow regions that weren’t possible before, even creating regions from if statements, and it also persists the collapsed state.
  • CodeKeep is the ultimate collection of source-code snippets, with a corresponding add-in for Visual Studio 2005 so you can drag-and-drop snippets into the editor
  • The ControlTree Visualizer lets you see the control hierarchy on a web page during debugging, which should prove invaluable with some of my ASP.NET AJAX bugs…
  • Control Visualizer is another ASP.NET debugging visualizer from the same guy that wrote the by-now-famous Cache Visualizer
  • PInvoke.net is actually a website — which I find very valuable (especially when I’m working on shell-related stuff in .NET) — I generally look up API calls on the website, but they also have an add-in for looking things up from within Visual Studio. I may just have to install this when I start coding for fun (instead of for school) again.

Oh, and a random little link to Regulazy a regular expression tool for the rest of you (who can’t tell a \d{2} from a \w+). This isn’t an add in, but it is a really clever way to build regular expressions from a sample string that you want to match.

Technorati Tags: , , , , ,

]]> http://huddledmasses.org/downloads-for-visual-studio/feed/ 0 MSDN Wiki to expand http://huddledmasses.org/msdn-wiki-to-expand/ http://huddledmasses.org/msdn-wiki-to-expand/#comments Fri, 08 Sep 2006 23:44:18 +0000 Joel 'Jaykul' Bennett http://www.huddledmasses.org/jaykul/msdn-wiki-to-expand/ According to the SandCastle blog, the response to the beta of msdnwiki.microsoft.com has been very positive, with the main request being that they import more documentation (I know several of my developer friends have commented that none of the platform SDK is available there, which is where community sample code would be most appreciated). The good news is that:

Based on this feedback, MSDN is working to migrate the community content feature to their main site so that it can be expanded to the entire library, including other localized versions of the Whidbey documentation in MSDN2 by the end of this calendar year.

At that point, the only stuff that will remain on the MSDNWiki site is the machine-translated content — they offer machine translated documentation in Wiki format so that native speakers can improve the translations in languages where the market isn’t big enough for MSDN to offer an official translation of the documentation.

]]> http://huddledmasses.org/msdn-wiki-to-expand/feed/ 0 LINQ and Blinq http://huddledmasses.org/linq-and-blinq/ http://huddledmasses.org/linq-and-blinq/#comments Tue, 11 Jul 2006 14:39:59 +0000 Joel 'Jaykul' Bennett http://www.huddledmasses.org/jaykul/linq-and-blinq/ Microsoft’s ASP.NET team has created a tool based on the May CTP of LINQ (see the very cool what’s new video) for generating websites that display, create, and manipulate data. All you do is point Blinq at a database, and it creates a website that displays the data, allows sorting and paging and updating, deleting and creating new records, including following the relationships between tables.

The reason that’s impressive is because there’s no SQL queries to write, LINQ generates optimized queries and Blinq generates web forms and pages from the database schema. Of course, this is all in beta, and for developers only (you can’t use it in production yet).

]]> http://huddledmasses.org/linq-and-blinq/feed/ 0