Welcome to the Windows PowerShell Community!

%3CLINGO-SUB%20id%3D%22lingo-sub-261971%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-261971%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20about%20Testing%20Powershell%20or%20Pester%20in%20Powershell.%26nbsp%3B%20An%20important%20topic%2Fspace%20for%20the%20community.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-20716%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-20716%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Anna%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20wondering%20if%20is%20possible%20to%20move%20my%20trend%20I%20previously%20posted%20under%20%22Windows%20Server%20PowerShell%22%20before%20this%20new%20section%20%22Windows%20PowerShell%22%20became%20available.%26nbsp%3B%20I%20got%20some%20post%20that%20will%20be%20interesting%20for%20poeple%20interested%20in%20PowerShell%20Open%20Souce.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EMaximo%20Trinidad%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16851%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16851%22%20slang%3D%22en-US%22%3E%3CP%3EPerhaps%20in%20the%20future%20when%20its%20officially%20released.%20Right%20now%26nbsp%3BPowerShell%20Core%20is%20still%20in%20Alpha%20I%20believe.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16675%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16675%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20we%20know%20there%20are%20two%20PowerShell%20areas%3A%20Windows%20PowerShell%20and%20PowerShell%20Open%20Source.%20They%20are%20different%20indeed%20but%20reaching%20the%20same%20goal%3A%20%22System%20Automation%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20dilemma%20might%20be%2C%20PowerShell%20Open%20Source%2C%20everyone%20can%20provide%20feedback%2Fissues%20and%20collaborate%20with%20development%20(no%20NDA%20restrictions).%26nbsp%3B%20Now%2C%20with%20Windows%20PowerShell%2C%20you%20can%20provide%20feedback%2C%20but%20it%20still%20remains%20under%20Microsoft%20NDA%20restrictions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20maybe%20having%20a%20Space%20for%20PowerShell%2C%20then%20under%20it%20we%20could%20possibly%20have%3A%3C%2FP%3E%3CP%3E1.%20Windows%20PowerShell%3C%2FP%3E%3CP%3E2.%20PowerShell%20Open%20Source%3C%2FP%3E%3CP%3E3.%20General%20Best%20Practice%3C%2FP%3E%3CP%3E4.%20Community%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20will%20still%20evolve%20to%20have%20more%20favorites!%3C%2FP%3E%3CP%3E%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16663%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16663%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9001%22%20target%3D%22_blank%22%3E%40Maximo%20Trinidad%3C%2FA%3E%26nbsp%3Basked%20the%20same%20thing%20over%20in%20the%20Windows%20Server%20PowerShell%20Community.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-Server-PowerShell%2FJust-wondering-if-there-is-a-chance-of-having-a-special-section%2Fm-p%2F8948%23M1%22%20target%3D%22_blank%22%3EJust-wondering-if-there-is-a-chance-of-having-a-special-section%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProbably%20a%20good%20idea%20to%20keep%20things%20a%20little%20seperate%2C%20but%20I'm%20even%20slightly%20confused%20why%20there%20are%20two%20different%20complete%20communities%20for%20POSH.%20Shouldn't%20the%20general%20'PowerShell'%20community%20be%20a%20top-tier%20with%20possibly%20seperate%20Spaces%20underneath%20as%20'level%202'%20sections%3F%20PowerShell%20is%20the%20base%20technology%20for%20both%20PowerShell%20communities%2C%20after%20all.%20The%20only%20thing%20that%20is%20different%20is%20the%20use%20cases.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16468%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16468%22%20slang%3D%22en-US%22%3EWould%20it%20be%20beneficial%20to%20have%20a%20space%20for%20Powershell%20for%20Linux%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-15919%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-15919%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F17731%22%20target%3D%22_blank%22%3E%40Mike%20Riston%3C%2FA%3E%26nbsp%3Bwe're%20using%20labels%20for%20now%20for%20that%20and%20if%20there%20is%20enough%20momentum%20for%20some%20of%20these%20labels%20we%20can%20create%20a%20specific%20space%20for%20them.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-13232%22%20slang%3D%22en-US%22%3EWelcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-13232%22%20slang%3D%22en-US%22%3E%3CP%3EBy%20popular%20demand%20we%20have%20created%20a%20Windows%20PowerShell%20community%20on%20the%20Microsoft%20Tech%20Community!%26nbsp%3B%20Please%20post%20questions%2C%20best%20practices%20and%20answer%20questions%20posted%20here!%26nbsp%3B%20Make%20sure%20you%20use%20labels%20suggested%20in%20each%20post%20to%20help%20people%20find%20your%20posts.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20looking%20for%20suggestions%20on%20new%20spaces%20to%20create%20here%20so%20let%20us%20know%20if%20you%20have%20recommendations%20on%20what%20we%20can%20do%20here%20to%20make%20this%20community%20a%20great%20place%20for%20everyone%20to%20learn%20more%20about%20Windows%20PowerShell.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-13232%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECommunity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-15239%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-15239%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20don't%20appear%20to%20be%20any%20%22Spaces%22%20in%20the%20PowerShell%20Community.%20I%20may%20be%20missing%20something%2C%20but%20I%20don't%20see%20how%20to%20start%20a%20topic%20without%20a%20%22Space%22%20and%20I%20don't%20see%20a%20way%20to%20create%20a%20%22Space%22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-15242%22%20slang%3D%22en-US%22%3ERE%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-15242%22%20slang%3D%22en-US%22%3EI%20think%20I%20figured%20out%20how%20to%20start%20a%20new%20topic%2C%20but%20it%20still%20doesn't%20quite%20show%20up%20correctly.%20Possibly%20since%20there%20are%20no%20spaces%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-15243%22%20slang%3D%22en-US%22%3ERE%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-15243%22%20slang%3D%22en-US%22%3EWe're%20ironing%20out%20a%20bug%20right%20now%20but%20a%20quick%20hack%20would%20be%20to%20click%20'Windows%20PowerShell'%20link%20next%20to%20my%20name.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-15249%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-15249%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20now%20fixed%20-ERR%3AREF-NOT-FOUND-%40Richard%20Benfield!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-15255%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-15255%22%20slang%3D%22en-US%22%3E%3CP%3EAwesome!%20Thank%20You!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-15903%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20to%20the%20Windows%20PowerShell%20Community!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-15903%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20may%20be%20a%20great%20start%20to%20have%20the%20Community%20have%20different%20'Spaces'%20each%20for%20some%20of%20the%20main%20things%20you%20mentioned%20in%20your%20post.%20Best%20Practices%2C%20Example%20Code%2FSituations%2C%20etc.%20Just%20thinking%20that%20may%20keep%20it%20from%20becoming%20too%20much%20of%20a%20'Everything%20in%20one%20pot'%20situation.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Community Manager

By popular demand we have created a Windows PowerShell community on the Microsoft Tech Community!  Please post questions, best practices and answer questions posted here!  Make sure you use labels suggested in each post to help people find your posts. 

 

We are looking for suggestions on new spaces to create here so let us know if you have recommendations on what we can do here to make this community a great place for everyone to learn more about Windows PowerShell.

13 Replies
Highlighted

There don't appear to be any "Spaces" in the PowerShell Community. I may be missing something, but I don't see how to start a topic without a "Space" and I don't see a way to create a "Space".

Highlighted
I think I figured out how to start a new topic, but it still doesn't quite show up correctly. Possibly since there are no spaces?
Highlighted
We're ironing out a bug right now but a quick hack would be to click 'Windows PowerShell' link next to my name.
Highlighted
Highlighted

Awesome! Thank You!

Highlighted

It may be a great start to have the Community have different 'Spaces' each for some of the main things you mentioned in your post. Best Practices, Example Code/Situations, etc. Just thinking that may keep it from becoming too much of a 'Everything in one pot' situation.

Highlighted

Hi @Mike Riston we're using labels for now for that and if there is enough momentum for some of these labels we can create a specific space for them.

Highlighted
Would it be beneficial to have a space for Powershell for Linux?

@Maximo Trinidad asked the same thing over in the Windows Server PowerShell Community. Just-wondering-if-there-is-a-chance-of-having-a-special-section

 

Probably a good idea to keep things a little seperate, but I'm even slightly confused why there are two different complete communities for POSH. Shouldn't the general 'PowerShell' community be a top-tier with possibly seperate Spaces underneath as 'level 2' sections? PowerShell is the base technology for both PowerShell communities, after all. The only thing that is different is the use cases.

Highlighted

As we know there are two PowerShell areas: Windows PowerShell and PowerShell Open Source. They are different indeed but reaching the same goal: "System Automation".

 

The dilemma might be, PowerShell Open Source, everyone can provide feedback/issues and collaborate with development (no NDA restrictions).  Now, with Windows PowerShell, you can provide feedback, but it still remains under Microsoft NDA restrictions.

 

So maybe having a Space for PowerShell, then under it we could possibly have:

1. Windows PowerShell

2. PowerShell Open Source

3. General Best Practice

4. Community

 

This will still evolve to have more favorites!

:)

 

Highlighted

Perhaps in the future when its officially released. Right now PowerShell Core is still in Alpha I believe.

Highlighted

Hi Anna,

 

Just wondering if is possible to move my trend I previously posted under "Windows Server PowerShell" before this new section "Windows PowerShell" became available.  I got some post that will be interesting for poeple interested in PowerShell Open Souce.

 

Thanks,

Maximo Trinidad

Highlighted

How about Testing Powershell or Pester in Powershell.  An important topic/space for the community.