Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

JohnLudlow

JohnLudlow JohnLudlow

Niner since 2011

  • Defrag Tools #94 - Sysinternals Strings, FindStr, !pde.ssz

    @olexiy:Also, the "Customize notification icons" screen Andrew was on has a "Turn system icons on or off" link at the bottom which also takes you to the same place.

  • Inside .NET Native

    @apardoe:Yeah I think the desktop is going to be around for a while. I missed that desktop wasn't currently supported, but I'm glad you're thinking about it.

    I gotta say, "the convenience of C# with the performance of C++" is one heck of a selling technique! :) 

  • Inside .NET Native

    So would this enable you to run .NET code without the .NET framework?

    I'm mainly thinking about C# code being used by installers, where a dependency on the .NET framework is less than desirable.

  • SideWaffle

    This is pretty cool. I didn't realise it was more than just web templates, or that the template builder existed, so I'd ignored it all until now.

    I can see us using templates to capture certain patterns, but as you guys mentioned the zipping and unzipping and tweaking and re-zipping every time you want to update a template has meant it's not really worth it. This 

    The UI's not too bad, you just have to remember to do a couple of things to get things working. I guess that could be made a little more streamlined and automated.

  • Defrag Tools: #80 - App-V

    FYI, Scintilla is the editor component that Notepad++ uses. It's quite a popular open source editor control.

    http://www.scintilla.org/

  • Auto History Extension

    Glad I could help :)

    I'll continue to play with the extension and will post back if I feel I have something more you might find useful.

    Thanks

  • Auto History Extension

    Actually, Mark, I realised I didn't 100% answer your question. The above comment describes how I use Visual Studio's ability to dock tool windows (which answers part of your question - whether I'd want it always visible) but the other part (whether a side-docked approach works) wasn't answered.

    To answer that, yes I think a side-docked arrangement does work, but you have to be very careful about using horizontal space because you're effectively in a thin vertical strip down the side, and currently I think it uses more horizontal space than is strictly necessary (meaning that I have to allow that strip to be wider than I'd like).

    I understand that this is still WIP, and the UI isn't final :), but I thought it was worth giving the feedback anyway.

    Thanks

  • Auto History Extension

    Hi Mark

    No, not exactly. Basically, because of my need to move between multiple contexts at once (for example, different projects), I keep a pane docked at the right hand side of my Visual Studio window. That's always open, and has the Solution Explorer, Team Explorer, Properties window etc in a tabbed arrangement. See http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-29-92/1854.Visual-Studio-11-Beta-Full.png

    Along the bottom of my VS window, I typically have things like the output pane and Error List, again in an always visible tabbed pane docked against the VS window. When they are pinned like this, I generally try and size the window so it doesn't steal my screen real estate.

    Depending on what I am doing, I will sometimes collapse these panes or close them altogether. However, even when I do that, I often want to see both the code and that pane at the same time, for example, I am comparing what I see in the code against something in Properties, or I am looking at an error in the error list and trying to locate the offending line in the code. Clearly, in that situation I will still want to size those panes so they don't hog the screen.

    I also don't want to have to dock AutoHistory differently to how I treat other windows. I like to treat things the same where possible.

  • Auto History Extension

    Good stuff

    I think you may need to take another look at the UI layout. If I dock it against the side of the VS window (as you have it in the video) then it takes up a large portion of the screen - if I shrink it down to a reasonable size the snapshot name boxes disappear. If I dock it against the bottom of the window (again, sized so it doesn't hog my screen real estate) then the ticks on the history timeline become almost invisible.

  • Defrag Tools: #73 - Message Analyzer - Part 3

    @PaulELong:That'd be great. Thanks

See more comments…