Exec Inline AddIn for Visual Studio 2005 -- Get It Now
 I still use the Exec-Inline addin now and then -- so I've updated it to work for VS 2005. To install it: - unzip this file -- ExecInline.zip -- into the folder:
"C:\Documents and Settings\{Your Username}\My Documents\Visual Studio 2005\Addins" (If the folder doesn't exist -- create it!) - Next time you start visual studio 2005 the tools menu should contain a new item: '
ExecInline' with a smiley face icon. (if not, check the Addins menu to see that it's loaded)
Select a snippet of your code, press 'ExecInline' -- and KAPOW! The snippet is executed all by itself.
Illustration:
As I've said before:
...all credit for this invention goes to these four places: Code compilation retyped from jconwell's Dot Net Script Project at CodeProject. Wrapper around compilation via dstang2000's DynamicCompileAndRun project. Help with writing a VS Add-in: Scott Swigart, PasteAs Visual Basic Add-in And help with getting the currently selected text from the IDE, via Kevin McFarlane's VS Csharp Macros page.
Also, the idea was partially inspired by Don Syme's F# interactive which I first saw mentioned on John Lam's website -- but mostly inspired by Ctrl-E from SQL Query Analyzer. In fact the more I look into this little side project the less credit I deserve. I am a flea on the back of bigger fleas, ad infinitum.
'Scott' on Sun, 22 Jul 2007 08:40:52 GMT, sez: thanks Leon! Works great.
'Oran' on Sun, 22 Jul 2007 20:03:14 GMT, sez: Cool tool! Somewhat similar (but different) is TestDriven.NET's ad-hoc testing feature that lets you run arbitrary methods. Once you hook up a keyboard shortcut to the "Run Test" command, you're just a keypress away from running the method your cursor is in. Add another shortcut for Test With Debugger, and now it's just F9, shortcut, and you're at your breakpoint in an arbitrary method.
http://www.testdriven.net/quickstart.aspx#Ad%20Hoc%20Tests
and
http://www.testdriven.net/quickstart.aspx#Debug
'Eric D. Burdo' on Mon, 23 Jul 2007 09:53:15 GMT, sez: Nice! I have been wanting something like this for awhile now.
'thienpnguyen' on Mon, 07 Jan 2008 00:19:42 GMT, sez: Leak memory bug : the generated assembly is never unloaded.
Prove : run the following line code many time, you will see that #assemble is always increased.
MessageBox.Show("#assembly : " + AppDomain.CurrentDomain.GetAssemblies().Length);
How to fix : create an other AppDomain for running generated assembly, after that unload that AppDomain.
Note : if you want the example code, please send email to me thienpnguyen@hotmail.com
|