Research Triangle PowerShell Users Group User Group, 6 Jun 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: PowerShell Pro Tools: Take Your PowerShell to New Places with Tim Warner

Description

One of the greatest strengths of the PowerShell language is its flexibility. However, even though PowerShell is super adaptable, some tasks are still a challenge. Tasks such as creating a GUI front-end for your PowerShell function or packaging your PowerShell module as an EXE or DLL are not trivial tasks. That’s where 3rd party tools and add-ons can bridge the gap!

This month, Microsoft MVP Tim Warner @TechTrainerTim walks you through how to use Adam Driscoll’s PowerShell Pro Tools software suite. Tim will show you how you can create GUI’s, make EXE’s as well as convert PowerShell to C# and vice-versa with the help of PowerShell Pro tools. He’ll also dive into how you can use PowerShell Pro Tools in three different editors: Visual Studio, Visual Studio Code, and the PowerShell console.

A

Tonight's session is all about Adam Driscoll's, PowerShell, PowerShell, pro tools and Mike I. Don't know how deep we're going to get honestly. You know my Suites lattice of a teacher is beginner intermediate content, we'll see what happens. My main goal for tonight is to familiarize you with that tool set and I'm going to make sure as I show you each of its major features why you would want to use them I mean that's a really core principle of adult education. Isn't it. Why am I learning this? Why do I care?

A

What's in it for me, so, very briefly, before I stop my video and start the demo I'm don't have any slides for you tonight how I came to this tool set while the developer, Adam, Driscoll I, admire PowerShell community members for different reasons and Adam I've always admired for two reasons: one he's a developers developer he's probably forgotten more about dotnet development and I'll ever know in my life and number two he's balanced, I think really well: community giving community volunteer contribution on one hand and developing a business model in a livelihood for himself on the other.

A

So that's that's how he came on to my radar quite a long time ago, over the last ten years or so I've been writing product reviews for the forces, ops, technology, blog and I like doing that, because it gives me exposure to tools and platforms that I might not come across ordinarily and a few months ago, I was asked to review the toolset and I thought perfect opportunity to get into it and get under the covers.

A

Kick the tires insert whatever metaphor here, and it really put a lot of cool things together for me and, like I, said to kind of round out my introduction. That's my main goal is to show you how the Tool Works you know from soup to nuts. Why you care about installing it? How much does it cost? What's licensing like and then, of course, what can it do for you, when your powers shall work, think you'll be pretty impressed with it? I know that I am and also I'll show you that momentarily hey hold. That thought.

A

Let me stop my video and I will attempt to share my second monitor, let's see while you're sharing your second monitor, I will just give people a little preview, Adam Driscoll we were. We were requested from a community member to see if we can get Adam Driscoll to talk about his Universal dashboard. We will be having Adam speak sometime before the fall. We haven't settled on a date yet, but Adam and I are discussing that right now, so something to keep your eyes open for that's great news. Mike.

A

Can you see if my v/s code instance? Yes, sir okay good deal all right, so what you're seeing is a script? Slash demo file that I put together for us tonight and you can see there on line 8. If you want this file, you'll point your browser to Tim W dot info forward, slash summer 2019, and that URL will take you to one of my github repos and in there you'll find this file and a whole bunch of other doodads. Basically, all my presentations for the summer I'm, putting in just a single bucket.

A

Let's consider it a toy box of sorts. Okay, let's see, let me get my cursor over here, get my bearings okay, so posh tools.com is the project homepage and from a highest level. What we're talking about here initially is. This is a product that gives you power, shell capability and Visual Studio. Now you might be thinking well, I'm, a PowerShell person, I'm interested in administrative automation. What do I care about? Visual Studio? That's a developer tool! Well, not so fast I, don't know if you're doing anything with Azure yet!

A

But if you are it's not going to be too long before you start working with resource templates or really, the whole idea of infrastructure is code before long you'll, probably wind up in Visual, Studio and so you'll want I think. As far as I know, Adams project here PowerShell tools for Visual Studio is the de-facto way to unlock PowerShell language support and Visual Studio.

A

But, as you can see, on posh tools.com, a single user license of 60 bucks USD, it runs in full Pro mode for 21 days and then the features downgrade to the free tier. And if you go to doc, stop patch tools, com, that's the documentation, library and there's a feature comparison here between the paid version and the free version of PowerShell tools. You can see the atoms been pretty generous in terms of feature parity. Some things are paid only like c-sharp to powershell code conversion, the bundling and packaging.

A

Your powershell scripts and modules is executable, scoped, code, obfuscation and so on and so forth. Okay, another point I want to make about licensing and pricing just FYI to shorten your learning curve. Is that it's per user, which is really convenient if you work on multiple systems, so in other words, for 60 bucks, you've got your license code, and not only can you install it on all of your workstations, but the same code works in all three environments.

A

All three I mean Visual Studio Visual Studio code and then the PowerShell console and I'll show you and we'll differentiate those as we go along. Oh one point that I want to make clear before we begin. I am NOT and never have been and never will be a salesperson and I'm, not a shill.

A

That the reason I have a licensed version of PowerShell pro tools: I'd, happily pay the 60 bucks, but I received a free license from Adam by virtue of my Microsoft MVP award. So if there's any other MVP awardees on the call know that you can contact Adam and receive a complimentary license, so I'm not shilling when I share stuff, it's because I believe in it and like it and want to share it with others. Just wanted to make that super clear.

A

Okay, now, as far as installing and starting to rock and roll and getting into these features that you see on this bullet list, there's three ways to go. There, like I, said: there's three variants of the PowerShell Pro Tools and the first is we can just from our powershell get system saying I, don't even remember if we're on a server desktop system right now it doesn't matter, but we can query the powershell gallery we'll do a find module.

A

Powershell pro tools. Bottom line is adam, keeps the console, powershell tools up on the gallery, and if you install that, I actually have all this code written out here. So I can just select the appropriate commands once you install the module on your system, you want to update the help, as usual can do a manual import or just start tapping directly in on line 24. For instance, we can enumerate the commands in the module.

A

It's a you know, not a huge list of Commandments, but they cover all the different bases: code, conversion, profiling, script, performance, creating packages and stallers and creating gooeys. So that's one way to go. If you just want to get down to the ground floor and work with this Swiss Army knife toolkit, that's another way, you can look at powershell. Pro tools is the sort of Swiss Army knife, so it has a handful of special-purpose functionality.

A

So that's the PowerShell console version as far as visual studio has happened, to have Visual Studio 2019 installed here, and it's an interesting story here, as I mentioned a few minutes ago. As far as I know, correct me, if I'm wrong, Adams tools, Adams extension here is the de facto way to get PowerShell language support into Visual Studio, and he told me that, as of I, think Visual Studio, 2017 Microsoft for some inexplicable reason stopped, including it in the Installer Visual, Studio, 2015 and 2013.

A

You could actually install the PowerShell tools for Visual Studio in the installation process, but as of vs 2017 and 2019, it's a manual thing, but it's not a big deal. We can just go to extensions, manage extensions and I have it installed, but you would go online to the visual studio gallery and you would just do a search for PowerShell and you can pop in the extension right here. Powershell tools for visual studio, like I, said it's going to run in full unlock unlock. I can't speak, it's a workday.

A

You understand it runs in full mode for 21 days and then it downgrade. So you might be wondering well how the heck do you get a license? Honestly, I, don't know how to license it from the console. You have to check the documentation to license from Visual Studio you go to help and under about Microsoft Visual Studio, there's about about PowerShell Pro tool, say that three times quickly and assuming you've purchased the license go to patch tools. You pay your money within 10 minutes or so you'll get your license via email.

A

You just paste it in and you're good to go all right now. What does that give you well you're, seeing some of it right now. Number one you've got the PowerShell interactive window, so this is the way to get a console host running in Visual Studio itself.

A

That's essentially what it is, and if we echo the host automatic variable, we can scroll up a little bit.

A

Yeah, so it's custom hosts powershell engine hosts that Adam created for this purposes. For this purpose, and you get all of your code completion, you know, get a serve so you're able to complete commandlets and parameters and I bet it would even do enumeration. So let me clear the screen and let me do a set execution policy.

A

Yeah, so so it's giving us full intellisense code completion that we would expect another thing that you get when you load up the powershell tools in Visual Studio. Is this command Explorer add-on that you see on the right and what this is doing is loading up all of your modules and you can search if you're looking for a particular command connect, AZ account, for instance, if you're an azure person, they'll show you the module and then the command.

A

If you right-click, you can copy it, that's kind of ho-hum it just copies and pastes it out onto your surface your script. The other thing it can do is, if you view the details, it essentially just connects to the help. You know- and you know- and you can jump right to the examples using the search filter up on top I found that, to be mildly, unstable. In fact, it's a little unstable right now, unfortunately, but I'm just walking you through this a step at a time come on now let go.

A

I will say that Adams super responsive about bug, reports, I found that he's super responsive in terms of addressing you know, feature requests feedback. All that kind of stuff huh looks like I dumped out a visual studio. That's fine! Let's just restart it I'm going to continue without code yeah, so the command Explorer. That's you know, that's what it is really I find that the powershell interactive window host the intellisense, the code complete stuff and then finally, we have in the file new project dialog.

A

The powershell tools give you a couple: powershell related project templates. You've got a module project, script project and the module template project is pester, aware and gives you the scaffolding and so far so forth, yeah as far as that goes okay.

A

So, let's see I'm just get service as far as running code in your scripts, the debugging experience- that's something I haven't really played around with yet in here, but because you're in Visual, Studio I presume that you've got full debugging support when you right-click a selection, for instance, how you could force that to run in your interactive window down below you, have execute selection, execute script, execute script with parameters, so that I think is the long story short about visual studio and the PowerShell tools. Now, of course, there's far more to this toolset.

A

This is just our initial first run-through in terms of installation and licensing. Now, then, what about vs code, which you're hopefully using, given that the PowerShell ISE is rapidly going the way of the dodo? We can install it in Visual Studio code through again the marketplace here. So if we bring out the marketplace and do a search for PowerShell tools, PowerShell pro tools, here we go. It's just a you know it first flush, a garden-variety extension install it and that unlocks some stuff, like this sidebar item, called the module Explorer.

A

If you don't want a sidebar item, for instance, you can always right click in that little gutter and turn it off just FYI. It took me a long time before somebody turned me on to that and the module Explorer I find is kind of useful. It gives you a full enumeration of all of your modules on that system and also shows the versioning. So, as you know, PowerShell for couple versions now has allowed side-by-side multiple versions of the same module. So we can take a look at that history here.

A

Let's see if it allows us to do anything else, I don't think it really does anything else. It's just a simple browser, but that's the module Explorer. Another way we can go here is to open the good old command palette and type pro tools that will list at least some of the options available directly in the command palette. So, let's see show power. Show pro tools install license key right.

A

So the question of how to license this again 21-day trial in it downgrades you get your key just open the command palette, come down to PowerShell pro tools install license key. You will open up an input box paste your key in and you're good to go. Okay, there's a welcome screen that looks a lot like the universal dashboard and Mike I'm, glad that that Adams going to present that because that's his other main project and I know nothing about the dashboard.

A

It's been on my to-do list for months to take a look and see of some of its capabilities, so I'm looking forward to learning more about that all right proceeding. Let's take a look as far as some of the specific functionalities. Now that the empower shell tools can offer one is going beyond measure command.

A

You know the built-in command lit for doing some basic benchmarking and profiling performance command, pipeline performance, script, performance, there's an extension to that built into the tools here so for an example, I have a sample file here, I'm going to right click this and pop it into a different tab. It's just Thai code that iterates 1 to 100 and sleeps and so forth. So it serves as an okay test case and to run a trace on that a performance trace. We can just do a search should just be trace.

A

Let's know, profile, I think it is yeah PowerShell profile script, something I observed in my testing that I'll just pass along to you. It's funny, normally extensions. The commands in the command palette will always start with the extension name and I showed you a moment ago that if you do a search for Pro, Tools or PowerShell Pro tools, there are commands that use that. But then there are others like the one that we were just looking at I, keep forgetting what it's called profile.

A

Yeah I need to ask Adam I'm going to send them a message tonight or tomorrow about this, because this makes me think PowerShell profile script that it's part of the PowerShell extension and not part of Adams. In fact, maybe it is but I don't think so, and you know what it's supposed to do. This is again I, don't know if this is a bug I doubt it's a bug.

A

It's probably the typical problem that I have each day, which is where, when I run into a problem, you know where it turns out to be between my keyboard and my chair.

A

For some reason, that seems to be the predominant source of my problems, but when, when I start, this correctly slash if the features working as expected for each call for each pipeline for each command, you'll get a metric of how long it took to run and how many calls were made within that command, and you can see in the documentation the results of that, but that that's kind of ongoing on my workbench to try to learn more about that fact. Let me click this link here to show you come on now: control click.

A

There we go yeah. In fact, I used the exact same code, trying to think well, if I replicate exactly what Adam had. Maybe that would help, but this is the expected result. As I said, you see an overall percentage of execution time that was occupied by each of these procedures and then how many calls now, in terms of diving deeper into that? What those calls are I'm, not sure it can go deeper. There are some limitations.

A

As you see here, you can only profile a single script at a time and when you're profiling a pipeline, it gives you just one summary metric as opposed to breaking out each segment in the pipeline, and it says here: Adam says that in a future version, individual commands will be able to be profiled. Okay, so again the use case there is you want to see what, if anything, is slowing down your script performance? You just want to put some numbers to your script.

A

Performance show me something that is the use case for this profile script feature next on our trolley. Let ride is packaging. Now. This is interesting on one hand, you might think what part of PowerShell command line automation. Don't you understand? Why would you want to create an executable out of a PowerShell function or a PowerShell script, and a good use case that I've seen and perhaps you have as well- is where you have automation?

A

You have help or utilities whatever the case may be already recorded in PowerShell, but you want to share that with users who may not yet be proficient with PowerShell, or maybe it's not in their job description and they don't care whatever the case may be. This allows us to package up individual script files or full robust modules as executables, and you wind up not only with an XE file but with potentially dll libraries and other dependencies that come along for the ride and what's happening under the hood.

A

When you use the PowerShell tools to package your code as an executable, it runs one of the command in the toolkit called merge script and the idea there is that you can either launch you load up your script, that you want a package. In fact, let me pick another one besides this one.

A

Let's see new user new form, hello, yeah. This is again it's all toy code, but this simple function calculates uptime and, as you can see, it's pretty old we're not even using the sim commandlets yet, but that doesn't matter for our purpose. We load up the script or the module project that we want a package and we can either come in through the command palette and there's a command again. It doesn't say powershell pro tools. It just says powershell, which confuses me as a user package is executable, but I think the recommended.

A

What I would recommend you do is to do the call to merge script, and then you can pass in all of your configuration parameters as a hash table, as you see here and essentially without getting deep into the weeds, because we're going to reach the limits of my knowledge, we've got the route of where your script or your module project exists, you're out directory, where you want the results to go and then there's a secondary hash table, which is just a collection of key-value pairs, recall where you can customize the packaging.

A

You should check out Doc's top posh tools comm here, because there's some really slick things you can do in here. If it's a console application, you can suppress or show the console window. You can do a custom icon I mean that's kind of ho-hum. You can target a particular dotnet version, but guess what else you can do if you're interested in targeting powershell core and making your resulting package as portable as possible, you can actually bundle the.net, core runtime and PS core runtime all in the single monolithic package. Isn't that cool?

A

There's an example on the docs page that actually shows that let's quickly check that out so on docks top posh tools.com, let's see if we go down to visual studio code and then packaging and visual studio code goes out to another docks page yeah. This is it and there's a couple interesting examples here. The one I used is just creating a simple console app, but you could create a service from your PowerShell code or what this is showing us. Bundling the PowerShell core engine with your script.

A

You'd need to have the dotnet core SDK installed on the system, but and of course the resulting executable is going to balloon in size, but it's a pretty cool way to do a fully independent executable. You know, so let me see I've done that. Let me go back to my vs code. I've run this sample code here and created it. Let me do it again. Let me select this block right click and run the selection air it out, probably because in my out folder it may already have the stuck the results in it.

A

Let me see: no I, don't I mean. Let me check that again. Hello, dat ps1 is the source file out, is the out file, enabled hide console window. I commented out the dotnet version and the app icon path. Maybe I missed a closing parenthesis.

A

You think that's what it was.

A

Yeah, so let's come up to out, let me right-click and reveal that folder and explore, and so you've got a config file here. If you look in the documentation, you can really do quite a bit of customization in terms of packaging, your PowerShell code, and that this is just a simple call. Basically, all this does is runs that function. I have in the function source code. Let's go back to hello dot, ps1 I've got my function, definition that calculates uptime and all I'm having it do is clear.

A

The host run the function with no parameters and then sleep. So again, it's toy, but hopefully I'm hoping anyway, that it's getting your mind thinking yeah, actually I, do have some PowerShell code and it would be nice to perhaps make it an executable to be run by non PowerShell proficient folks and something that I I'll leave to your homework. That I didn't get to and preparing this. For us tonight is the code obfuscation. That would be another layer that I could imagine.

A

You've got PowerShell code well in one hand, if you're working in a DevOps or DevOps friendly shop. You don't want to hide code from your colleagues, but maybe you're, creating a put a tool for customers, that's already in PowerShell, so the engine of the tools already there you could obfuscate the poke code and then package is an executable on top of that to preserve your intellectual property and also make the code more portable and universally available. So just an idea that popped off the top of my head.

A

So it then close up the Explorer here and come back to our script file here next on the docket is code conversion. This is interesting. I found in my work with the PowerShell community and I talked to a lot of people about this at the PowerShell summit. This year of when you reach a certain level of familiarity with PowerShell, and you just realize wow, there's so much that I do with my powershell scripts. That's very much like object, oriented programming.

A

What's to stop me from just going a little bit further and say: learning the c-sharp language and accessing the full dotnet framework. Dotnet standard dotnet core. So to that point you may have C sharp source code available that you may want to convert to PowerShell and vice-versa.

A

You may have a powershell function that in your development work moving to c-sharp, you want a head start on your c-sharp development, so wouldn't it be nice to be able to convert powershell source code to c-sharp, and so that's what we have here and the powershell pro tools is bi-directional: conversions from powershell to c-sharp c-sharp to powershell, and as this comment on line 60 says we're just going to open up the source code and then directly from the command palette. We can either call convert to powershell or convert to c-sharp.

A

So let me select I've got hello dot PSone already up there. So why don't I load up line 61? They tend while you're doing it. We had a quick question: that's actually a real console application. This is a c-sharp source file that creates a simple console: calculator in Visual Studio code ever helpful. As you see in the lower right corner of the screen, visual studio detects based on your file type.

A

What language that you're likely using vs code sees that we're using a CS file, so it's asking us: do we want to install the c-sharp, extend what it actually sounds like a pretty good idea, come to think of it question and it's happening automagically down below anyway, back to our regularly scheduled programming. What does this look like if we convert it to powershell? Let's just open up the command boa and do convert to powershell, so c-sharp convert to power Shaboom should pop open right in place. That's something I! Guess I would warn you about.

A

If you want to preserve your original source file, make a copy and then do the conversion on a copy. So what happened here it looks like we are now using the fun action keyword and because c-sharp uses main as its entry point. That's what we're calling the function here until we change it, we've got the familiar paramah and a bunch of calls. I mean the quality of the conversion. I'm, not really the right person to ask, but I would hope and trust that it's at least going to get you farther down the path.

A

If you are facing having to refactor c-sharp code to powershell or powershell to c-sharp, so let's see I wonder just for grins. If we run this file, what will happen? How do you want to open this file.

A

I, haven't actually run this code, so I'm not exactly sure what it's going to do. I would hazard the uneducated guess that you're going to have to do some refactoring, it's not just hit, convert and then run and you're happy. Maybe in a super simple case like let's try this one here so in a PowerShell source file, we can do a convert to powershell or no I'm sorry.

A

It would be a convert to c-sharp powershell convert to c-sharp yeah, so I mean we don't have using or namespace declarations which we may or may not need um object. Query ax, searcher, yeah I mean you know you could be picky I guess you could say wow, that's pretty verbose, I might say in response, isn't c-sharp a super verbose language anyway, but anyway at least I showed you how it works.

A

That's the code conversion from c-sharp to powershell powershell, to c-sharp, understand that when you run the command it actually modifies that current file, so I would make a copy before working with us. Also remember that you you're likely having to do some cleanup and some additional refactoring after you do your conversion.

A

Alright last piece here is the GUI thing, and what do I mean by that similar to that notion of packaging? Your PowerShell code, you may want a more agile approach, that is, where you're sharing your PowerShell source code, with maybe support desk or help desk personnel that are not PowerShell, proficient it's not in their scope and their job scope. Unfortunately, and you find that maybe packaging your code isn't agile enough, because I mean let's face it once you turn a cucumber into a pickle, you can't go from pickle to cucumber you like that.

A

Similarly, once you have your binary you're going to have to just recompile the binary, when you make code updates, maybe this, what we're seeing here might be a little more agile where you can generate a WinForms, a standard, win32 forms, application from your power, show function or module or the WPF. The windows, presentation, foundation, I believe the WPF design is limited to visual studio and Visual Studio code.

A

It uses the win32, which is the traditional windows forms and from what I've read on Adams blog heed is planning, because I think last I knew PowerShell core is beginning to support WinForms, initially I guess it was a total no-go, but I think that that support is forthcoming. So this gooey stuff I imagine, will work and PowerShell core eventually, but right now it only works in PowerShell, desktop or Windows PowerShell and, as you can see in the lower right corner of my vs code, my PowerShell engine is in fact 5.1 desktop.

A

So in vs code the way to generate a GUI from your source code, your PowerShell source, there's a fast way in a more complex way, checked the time. Ok, we're doing well on time. It looks like what, if tops, of the questions, have a single function like I have here this new user dot? Ps1 excuse me and I grabbed this from the Posche tool site very simple toy code, where we have a string parameter for username switch, enabled or not, and then there's a Department parameter that has a validate set.

A

So you can choose administrator, IT or HR and then the output. It just echoes that you know so. You've got a file with just a single function, definition in it, and then we can do a view command palette and then we've got PowerShell generate windows form and a couple things happen when you do that, you probably should put the source file in a separate folder.

A

Otherwise, I've got everything in my summer 2019 it's a bit gnarly to try to find the other files, but you've got besides the source file, new user dot, ps1 notice that there's a new user dot form dot ps1 and a new user dot form dot designer new user dot form. Let's take a look at what it's doing here. It's creating a type, a Windows form type object, and it looks like it's generating controls here, based on the parameters that you have in your function, definition, and eventually it does a show dialog.

A

So the idea is once the powershell ProTools creates your assets. You would then run the form file which we'll do in just a second to actually see and interact with the GUI. If we look at the form designer, what is that doing, let's see yeah it looks like this is fully defining the GUI wow. It's a pretty robust file and let's select the form and do a terminal run active file.

A

Hey Tim. Can you hear me display a little bit, so this generate form from function has just met and that's an interesting turn of phrase. Isn't it you talk about form and function here, we're generating a form from a function, but anyway it doesn't give us a whole lot of flexibility on the front end. It's just a quick GUI layer that creates controls based on your parameters and creates an event handler here.

A

As you can see on lines three and four, when we select items here, our user name, the enabled is a switch, so it's an on/off departments and enumeration, so we can select one or the other when we click Submit it fires off this button, click event handler and what does that do? Well, it calls our function and it passes in our content that we added to the form as parameter values, pretty neat huh I.

A

Suppose you could combine this, that is the function and this GUI layer and then combine that with the packager to create an XE hmm I. Just had that idea now, I'm sure I'm, not the first or last person to have that idea, but there you go alright.

A

So that's that that's the quick way to generate a GUI from a function and, lastly, there's what's called the windows form designer, so here we can start from an existing file or we can create a new blank ps1 file, because the idea here is that we're literally going to build as we go along, so we can go view command palette there. It is down here, show windows, form designer and a couple things happened there.

A

It starts to populate the file immediately by creating and Stan Shi ating a forms object, invoking the dialog and it's basically going to code behind as you work through this design surface, which is very much like visual studio. Isn't it you've got your drag-and-drop surface on the Left. You've got your window as controls over here on the right and let's see you can select it. Do you double click? It? No right click drag come on now.

A

Did this just a few hours ago, come on. Oh, you draw it. Okay, so you select it and you draw it and then you set your properties down below, as you can see. So, if I select the form, we can name it, and then we can set the label of the button.

A

So the idea here is that, instead of having to know the zamel or whatever is happening to actually build work, I guess sam'l would be a WPF form, but all of the code behind creating the surface and aligning the controls. You can do it graphically and if you double left-click a control like the button, it should create a handler for us here. Let's see, we've got new form that ps1 we've got new form.

A

There should be some other assets in here as well um that yeah new form dot designer I think no I'm confused here, everybody. Sorry, let me close everything, but that one file may bring this over here. I don't make close to the right. Yeah I should have put this in another.

A

Another folder because I'm getting all mugged up here, ah never mind I told you I'd be a little clumsy on this a again. The idea is you're creating the surface, and then you will have to go into the code behind and write out your event handlers. What happens when you click buttons and choose controls, but it's just meant to short and I think. The main selling point here is instead of having to know XY, coordinates and do all that kind of nonsense with raw code.

A

You can build your interface more graphically and then dive in in terms of fetching textbox, values and event, handlers for buttons and that kind of stuff if you've used sapiens tools before particularly PowerShell studio. That's what this reminds me of and I've got to say: 60 bucks is a heck of a lot less expensive than the license cost for PowerShell studio, but your mileage may vary as they say so.

A

The terms of summing up, let's see if we missed anything, let's come back here we bring out my PowerShell pro tool script. One more time can hear us yeah. That looks like the end. Let me scroll up to the top clear the screen and let me just say in summary: what we've got here again is a Swiss Army knife toolset. That's got a number of different abilities, creating a GUI for your code, packaging obfuscating, your code, profiling code performance.

A

You install it pay for your license. You can install on as many machines as you have and you can also install in as many hosts as you want. Powershell console, visual studio, visual studio code think that's really the long and the short of it everybody any questions, comments, concerns or curiosities about this or anything else.

A

Hey Tim. Can you hear us Bueller? Anyone Tim can hear them somehow Tim lost audio.

A

Well, I think that's about it. I could sing. I've got my guitar here, but as far as operational Pro, Tools I think that's the end of the old road Thank You Ann for having me Tim. Are you there.