PowerShell In GUI Blog

PowerShell GUI Box Just In A Few Clicks

A Very Simple Object Browser

with 4 comments

As I again decided to continue writing for the PowerGUI platform, which I’m personally user of, here is one another teaser. This object browser was written while the ScriptEditor object model had been developing and nothing promised that the thing would be living long. However, I used the thing several times after stopping of development, so that I understood it may be needed for somebody else.

I revised what has been done by now and the facts are:

– collecting data from the CurrentDomain, the GAC and from several manually loaded libraries

– displaying public members as well as private.

There are some bugs including broken search across asssemblies.

Features to do list includes

– creating snippets of code for selected definitions

– bookmarks

– rearranging controls and menu

– all other data sources 🙂


Written by Alexander Petrovskiy

June 14, 2010 at 1:34 pm

4 Responses

Subscribe to comments with RSS.

  1. I’m interested in seeing an Object Explorer for PowerGUI Script Editor. When will this be released?


    March 2, 2011 at 6:27 pm

    • Well, it’s wrapped as ObjectBrowser_20100712.zip and put into the bin at the right.

      The add-on is comprised of two modules (that were slightly renovated after PowerGUI 2.1 or later has been brought out), suite core and the browser itself.
      The latter should call and load the former, but it, of course, hasn’t been tested with the latest PowerGUI versions.
      Such a ‘complexity’ was the reason I was told not to publish multi- (namely, two-)tier construction as a PowerGUI plug-in, just not to expose behavior occurencies of the PowerShell Libraries window, so that all the additions done to it after the last summer belong to the project based on ISE and bare Powershell.

      On doing a small acceptance test of it before put it out to the world, I noticed that ObjectBrowser may not be loaded on apllication’s start, because PowerGUI 2.4 searches by default paths like %userprofile%\Documents\…, but as a result of upgrade or regular system locale rotation that I’m practising, the path it really needs is %userprofile%\My Documents\… .

      The normal way to load this module package is to put it into Modules folder (I obstinately use the standard path only, but custom one should work too I suppose),
      load SuiteCore or both at a time, or load ObjectBrowser after SuiteCore is loaded.
      On loading, the module reports its startup time to the embedded PowerGUI console, expunging all that’d been written there before. Time to load may vary depending on the hardware used, from ten to twenty seconds, as this time the add-on loads a number of libraries.

      ObjectBrowser literally does what is mentioned in its name: it browses assemblies. Abilities to copy properties’ or methods’ names have not been added yet. The only option you have here is to load PowerGUI application domain’s assemblies or the entire GAC content. The error browser is almost fake feature.

      Good luck with it and enjoy … if you can. 🙂

      Alexander Petrovskiy

      March 10, 2011 at 5:48 pm

  2. […] ObjectBrowser_20100712.zip requested here I’m interested in seeing an Object Explorer… […]

  3. Wer täglich 2 – 3 Kiwis isst, führt seinem Körper nicht
    nur gesunde Vitamine zu, sondern kann damit auch den Blutdruck senken.

    Gesundheit Tv Sendung

    July 28, 2016 at 4:07 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: