Summary of the issue

Currently powershell is unable to implement [Composition Over Inheritance](https://www.makeuseof.com/tag/basic-programming-principles/#composition-over-inheritance) because of a lack of support for custom interfaces, which prevents multiple inheritance of behavior interfaces

There is a way to get it to work, but it only works when running the code by hand, not in automated scripts

Proposed technical implementation details (optional)

The issue with the workaround boils down to a problem in the parser error: InterfaceNameExpected
It fails to recognize that using Add-Type will add types, instead it incorrectly assumes the given type will not be available

I think we should either allow a keyword to override this error, or educate the parser on the usage of Add-Type

Examples

I have included 3 examples (each has a readme.txt with relevant details):
A single file script that fails when run as a whole, but works if you manually run it line by line
A split that works, but is forced to have an incorrect dependency tree
A split that fails, because it's using a correct dependency tree

Note: The splits use dot sourcing, you'll need to adjust the paths to the appropriate folders on your computer

Files

(the click to upload isn't working [on chrome or edge] so here are dropbox links)

Fail - Single File: https://www.dropbox.com/s/xuava34s1dglqyh/Fail%20-%20Single%20File.zip?dl=0

Success - Bad Dependency Layout: https://www.dropbox.com/s/sz17020w56mtjpx/Success%20-%20Bad%20Dependancy%20layout.zip?dl=0

Fail - Good Dependency Layout: https://www.dropbox.com/s/fr38uj6b45jhqk4/Fail%20-%20Good%20Dependency%20Layout.zip?dl=0

Please allow us to define the install path when installing modules.

By default this seems to point to my $Home directory, but my $Home directory is on a network share at my office, and I am working remotely. I have time to make this suggestion because I am currently updating the AZ module on my computer, which means I download the module from the repository and write it to a network share across a Direct Access link/VPN, then proceed to "Install the dependency module" for each module within the AZ module - once again reading and writing to a network share across a DA link. Once this completes I will copy the updated modules directory to my local OneDrive folder, and then have to repoint my $env:psmodulepath variable to the OneDrive folder instead of my $home path every time I open powershell. Why are you forcing me to store my modules in my $Home directory instead of allowing me to choose where they go?

This issue is a problem I'm having using Add-VMHardDiskDrive.

I am not able to use a WSL path as argument. It seems the cmdlet can't access paths located in other network devices.

Steps to reproduce


Add-VMHardDiskDrive -VMName test -Path \\wsl$/Ubuntu/home/<image path>


Expected behavior

The cmdlet returns the success message describing that the disk was mounted successfully in the hyper-v virtual machine specified.

Actual behavior

```
Add-VMHardDiskDrive : 'test' failed to add resources to
'test'.
An unexpected error occurred: The network name cannot be found. (0x80070043).
'test' failed to add resources. (Virtual machine ID
4F4777B2-4DFD-4A07-89B6-44FFC5BE2D3F)
'main-image-1611598805' encountered an unexpected error: The network name cannot be
found. (0x80070043). (Virtual machine ID 4F4777B2-4DFD-4A07-89B6-44FFC5BE2D3F)
At line:1 char:1
+ Add-VMHardDiskDrive -VMName test -Path \wsl$/Ubunt ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : NotSpecified: (:) [Add-VMHardDiskDrive], Virtualizatio 

nException

+ FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.A 

ddVMHardDiskDrive
```

Environment data

```
Name Value

PSVersion 5.1.19041.610

PSEdition Desktop

PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}

BuildVersion 10.0.19041.610

CLRVersion 4.0.30319.42000

WSManStackVersion 3.0

PSRemotingProtocolVersion 2.3

SerializationVersion 1.1.0.1
```

If you convert your exchange ost file data in to pst file. Try stella ost to pst converter software to convert your ost file info in to pst file. Stella ost to pst converter software convert all of the items of this ost file. Stella ost to pst converter software convert all the ost file information like email products, contacts items, calendars things, activity items, notes items, log items and all the items of the user specify folders. Stella ost to pst converter software support all the edition of the exchange ost file. Stella ost to pst converter software convert all the items of the office 365 account. Stella ost to pst converter software convert all the items of their eml, emlx, msg, mbox, so many other structure. Stella ost to pst converter program support all of the corrupted ost file data into pst file. For more information visit this link https://www.stelladatarecovery.com/ost-to-pst.html

Download Vartika EDB to PST Converter that can help to export EDB to PST Outlook and also convert EDB file into five different file options such as- HTML, PST, MSG, EML, and EMLX. The Software has special features and techniques to transfer the EDB file and supports all editions of the Exchange server up to 2016 and gives free trial version software for free to use and convert emails from the Exchange server.
Some of its Features are
- Repairs Corrupted EDB files
- Ultra-fast export of mails from EDB files into PST file
- Allow Saving of EDB files in different Format
Note: Free version is only for limited mail export operation. (up to 30 mails export)
Get more info: - https://www.vartikasoftware.com/product/vs-edb-to-pst-converter-software.html

Add-DnsServerResourceRecord has flags like -A, -MX, -PTR, etc. However it doesn't have a -NAPTR flag. Therefore we can't create NAPTR records from PowerShell.

The NAPTR is a little-known DNS record type however it is an important part of most corporate SIP-based phone systems. Being able to rapidly set up NAPTR records using PowerShell would be great.

(More important than speed is accuracy: a lot of SIP setup time is spent debugging typos which would be easy to prevented if we could set our NAPTR records with PowerShell scripts.)

FYI: Remove-DnsServerResourceRecord's --RRType flag doesn't support NAPTR, therefore removing such records is difficult too, however there is a workaround for that. (Remove all records at the label.)