Added PowerShellAccessControl module
Added PSGet

It's definitely a V1 product but it will load modules from PowerShellGet
using the default provider.
Initial resources

Just opening the first commit.  Need to test the resource.
Module works in test
Added Readme

the readme contains a warning about the existing bug with PowerShellGet.
Converted files to ASCII

Implemented recommendations from Dave Wyatt
Merge pull request #34 from rohnedwards/master

Added PowerShellAccessControl module
Merge pull request #35 from JasonMorgan/master

cRDPEnabled - Updated
Converted cPSGet to ASCII

Based on recommendation of Dave Wyatt.
Merge branch 'master' of https://github.com/PowerShellOrg/DSC
Merge pull request #36 from JasonMorgan/master

Converted cPSGet to ASCII
Removed old DSC folders
Update README.md

Adding a note for the required modules needed to run some of the code.
Test-cDscResource fix for Embedded Instances

DSC Resources which contain properties that are embedded instances can now be tested by cDscResource without generating errors due to mismatched type names.

This could have been approached by adding a new entry to the $TypeMap hashtable for CimInstance and CimInstance[] , but other parts of the module also use $TypeMap, and I wasn't sure if that would create some new bug.

Instead, I added a flag to the DscResourceProperty class which indicates whether it's an "EmbeddedInstance" property, and ignored the type mismatch test when this flag is set.  This way the change is localized to fixing the one bug, and shouldn't have any other undesirable effects.

Because of this change, the old $ValidEmbeddedResource array and $AdditionalInvalidEmbeddedResource parameter are no longer necessary, and have been removed from the code.  (This is a breaking change for any current unit tests which try to pass in a value for -AdditionalInvalidEmbeddedResource).

MSFT_KeyValuePair and MSFT_Credential still have some hard-coded special treatment, because they map to properties of type hashtable and PSCredential.  All other EmbeddedInstance types are assumed to be of type CimInstance or CimInstance[] in the psm1 file, at this point.
Adding output types to Website.psm1

This was causing warnings when running invoke-dscbuild as it didn't have the correct output type.
Merge pull request #37 from rohnedwards/master

Removed old DSC folders
Merge pull request #39 from ArtWDrahn/patch-1

Update README.md
Merge pull request #43 from ArtWDrahn/patch-2

Adding output types to Website.psm1
Merge pull request #42 from dlwyatt/TestResourceWithEmbeddedInstance

Test-cDscResource fix for Embedded Instances
Last updates from Stack Exchange.. more help and a bit of renaming