![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | make-shell What happened to the whole custom shells and make-shell tool in the RTM? I can't find any info on this anymore. (Oh God please tell me it's still around or I have a lot of code to rewrite to make all this work with snapins...) |
My System Specs![]() |
| | #2 (permalink) |
| | RE: make-shell Think is now part of the SDK which is downloadable from http://www.microsoft.com/downloads/d...displaylang=en -- Richard Siddaway Please note that all scripts are supplied "as is" and with no warranty "fuzzy333" wrote: > What happened to the whole custom shells and make-shell tool in the RTM? I > can't find any info on this anymore. (Oh God please tell me it's still around > or I have a lot of code to rewrite to make all this work with snapins...) |
My System Specs![]() |
| | #3 (permalink) |
| | Re: make-shell Hi Fuzzy; These are still available in the PowerShell SDK, which is part of the Windows SDK. That said, we designed the snapin model to make your life significantly /easier/ , not harder. Custom shells are designed for situations when you want to lock down your environment and bake the functionality into it. If that's what you're trying to do, then great. If you just want to develop your own custom cmdlets and providers into your shell, then a snapin is the best way to go. When you implement your functionality as a snapin instead of a custom shell, you still have the ability to use and install other snapins. And perhaps more importantly, you can easily share your snapin with other PowerShell users without having to package and distribute your entire custom shell. You don't have to rewrite any code in order to transform your current Cmdlet / Provider DLL into a snapin. All you need to do is define an additional class to help PowerShell and .NET install and manage your snapin. The additional class extends the PSSnapinClass, and needs only to provide a Name, Vendor, and Description. This article on CodeProject is a helpful introduction to that: http://www.codeproject.com/vista/getfromcopernic.asp (although the name should be related to the DLL name, not the cmdlet contained inside of it.) -- Lee Holmes [MSFT] Windows PowerShell Development Microsoft Corporation This posting is provided "AS IS" with no warranties, and confers no rights. "fuzzy333" <fuzzy333@discussions.microsoft.com> wrote in message news:976B0370-EB00-4E30-ACE9-D443FEDB8377@microsoft.com... > What happened to the whole custom shells and make-shell tool in the RTM? I > can't find any info on this anymore. (Oh God please tell me it's still > around > or I have a lot of code to rewrite to make all this work with snapins...) |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Can parent shell monitor run/crash status of Child shell/exe ? | PowerShell | |||
| ps scripting newbie - how to make functions/scripts available in the shell? | PowerShell | |||
| make-shell | PowerShell | |||
| make-shell.exe | PowerShell | |||