Several bloggers are commenting today about Microsoft's acquisition of Winternals and Sysinternals. Ed Bott and a post on Slashdot, among others, both suggest downloading the latest versions of Sysinternals' free utilities while you can, 'cause it's not certain how long they'll remain available. The Sysinternals.com website is, predictably, jammed this afternoon with traffic I assume is from people heeding this advice.
Mark Minasi, author of several books in the Mastering(TM) series from Sybex, comments on this acquisition in his monthly newsletter. Minasi, who discloses that he's been a friend of Winternals' Mark Russinovich for years, says of Russinovich: "This is a good move for him and, I think, in the long run for us all. His presence in Redmond has to be a force for sound architecture, openness and innovation."
Tags: Microsoft, Winternals, Sysinternals, Ed Bott, Slashdot, Mark Minasi
7.18.2006
Microsoft acquires Winternals and Sysinternals
Mark Russinovich blogs this morning that Microsoft has acquired Sysinterals and Winternals. Sysinternals is known for a wide variety of popular system utilities such as FileMon, RegMon, Process Explorer, and Rootkit Revealer. Winternals focuses on system recovery and management tools, including the Administrators' Pak. See the press release for more information.
Tags: Sysinternals, Winternals, Microsoft
Tags: Sysinternals, Winternals, Microsoft
7.12.2006
No guts, no glory
... and in this case, no glory. In yesterday's post about Execute Selection in VFP, I got a bit carried away and tried to achieve a specific layout involving three images and several paragraphs of text. Two of the images were supposed to be side by side, with text above and below but not next to them.
Unfortunately, I failed to anticipate how blogger.com would treat the HTML when it published the post. The result was that the paragraph following the first two images didn't start below the images as intended, but instead flowed inline to the right. How much (if any) of the first part of that paragraph you could see depended on the width of your browser window. It was, to say the least, not very readable.
This morning I fixed the layout and republished the post. To avoid creating a duplicate, the republished post has the same publication date/time and item ID as the original, meaning that if your feed reader already retrieved the original it won't detect the updated one as being new. In some feed readers, such as FeedDemon, you can delete the original item and the reader will pick up the updated version when you refresh the feed.
Unfortunately, I failed to anticipate how blogger.com would treat the HTML when it published the post. The result was that the paragraph following the first two images didn't start below the images as intended, but instead flowed inline to the right. How much (if any) of the first part of that paragraph you could see depended on the width of your browser window. It was, to say the least, not very readable.
This morning I fixed the layout and republished the post. To avoid creating a duplicate, the republished post has the same publication date/time and item ID as the original, meaning that if your feed reader already retrieved the original it won't detect the updated one as being new. In some feed readers, such as FeedDemon, you can delete the original item and the reader will pick up the updated version when you refresh the feed.
7.11.2006
Execute Selection in VFP
If you're a VFP developer, you probably already know you can run a line or lines of code in the Command window by selecting them and choosing Execute Selection from the shortcut menu. But did you know you can do this in a VFP editing window, too?
This can be useful for testing selected chunks of code during development, but it also gives you a VFP equivalent to the SQL Server Query Analyzer. In SQL Server, you can store several batches of T-SQL statements in a single query file and run them independently of one another using the Query Analyzer. In VFP, you can store several groups of SQL statements in a single program file and run them independently of one another using the Execute Selection command in a VFP editing window.
As in the Query Analyzer, you can revise the code in the VFP editing window and execute it without having to save the file. Unlike the Query Analyzer, though, the F5 key does not execute the selection in a VFP editing window. Neither does VFP recognize the GO command that signals the end of a batch in the Query Analyzer (GO has a different meaning in VFP); if you need a way of ending a batch of statements in VFP, use RETURN.
VFP's Execute Selection feature can be useful during development and testing of almost any kind of VFP code, but it's particularly handy when you're working with lengthy SQL statements. While you could use the VFP Command window for the same purpose, an editing window is much more usable when individual statements run into several lines of code, which is typically the case with SQL statements. A program file is of course also more useful than the command window when you want to save your work and return to it later.
This can be useful for testing selected chunks of code during development, but it also gives you a VFP equivalent to the SQL Server Query Analyzer. In SQL Server, you can store several batches of T-SQL statements in a single query file and run them independently of one another using the Query Analyzer. In VFP, you can store several groups of SQL statements in a single program file and run them independently of one another using the Execute Selection command in a VFP editing window.
As in the Query Analyzer, you can revise the code in the VFP editing window and execute it without having to save the file. Unlike the Query Analyzer, though, the F5 key does not execute the selection in a VFP editing window. Neither does VFP recognize the GO command that signals the end of a batch in the Query Analyzer (GO has a different meaning in VFP); if you need a way of ending a batch of statements in VFP, use RETURN.
VFP's Execute Selection feature can be useful during development and testing of almost any kind of VFP code, but it's particularly handy when you're working with lengthy SQL statements. While you could use the VFP Command window for the same purpose, an editing window is much more usable when individual statements run into several lines of code, which is typically the case with SQL statements. A program file is of course also more useful than the command window when you want to save your work and return to it later.
07/12/2006 - Republished this post with corrected image and text layout.
Tags: Visual FoxPro, VFP, SQL Server, Query Analyzer
Tags: Visual FoxPro, VFP, SQL Server, Query Analyzer
Subscribe to:
Posts (Atom)