mkht / dscr_shortcut Goto Github PK

Hi, is it possible to pre-compile the ShellLink.cs and VKeyUtil.cs into a .dll? Currently, this module takes about 800 ms to load on my machine, which is quite slow.

It should be enough to just target netstandard2.0 and import the .dll instead of using Add-Type. Everything should work exactly as now, just with faster startup.

I can do a PR if you're ok with that.

発生条件は要調査

cShortcut GoogleChrome_DesktopShortcut_CreateToTargetUser
    {
        Ensure = 'Present'
        Path = Join-Path ('C:\Users\{0}' -f $TargetUser) '\Desktop\Google Chrome.lnk'
        Target = 'C:\Program Files (x86)\Google\Chrome\Application\chrome.exe'
    }

IconLocationの既定値が空文字ではなく,0のため

Method not found: 'System.Collections.Generic.List1 Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache.ImportClasses(System.String, System.Tuple2, System.Collections.ObjectModel.Collection`1)'.

Invoke-DscResourceを使ってGetを直接実行するとエラーが発生

Invoke-DscResource -ModuleName DSCR_Shortcut -Name cShortcut -Method Get -Property $para

プロパティの 'HotKey' 値を型 'STRING' から型 'STRING[]' に変換できませんでした
 行:15、文字:2
 バッファー:
irectResourceAccess";
};^
insta
    + CategoryInfo          : SyntaxError: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : MiClientApiError_Failed
    + PSComputerName        : localhost

WshShortcut.IconLocation

Hi,
Thank you for putting this together. Seeing something a little strange. I have a simple shortcut need that keeps failing the test process of DSC.

The DSC works, it creates the proper shortcut and the shortcut works, but it always fails the test with the following error "Target property is not matched"

I'm only specifying the following:

cShortcut "cShortcut_$($ConfigurationBaseName)_shortcut"

{
Path = "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Log Parser Studio.lnk" 
Target = "C:\Blah\IT\Infrastructure Services\SysAdmins\DSC\Download Cache\Microsoft\LogParser Studio\2.0.0.100\LPS.exe"
}

Any idea what i might be doing wrong? Like I said,the shortcut does work and it does exist, it just fails the test process.