You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: PSModuleDevelopment/changelog.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,14 @@
1
1
# Changelog
2
2
##
3
3
- New: Export-PSMDString - Parses strings from modules using the PSFramework localization feature.
4
+
- Upd: Template PSFProject - Adding `-IncludAZ` switch parameter to `vsts-packageFunction.ps1`, making the template include the AZ module as managed dependency.
5
+
- Upd: Refactored module structure to comply with current Fred Reference Architecture
6
+
- Fix: Template PSFProject - Publish Folder created during build is created using `-Force`
7
+
- Fix: Template PSFProject - Cleaning up Azure Function conversion
8
+
- Fix: Template PSFTests - Encoding test no longer fails on core (#104)
9
+
- Fix: Template PSFTests - Referenced DLLs from GAC will fail as path cannot be found (#100)
10
+
- Fix: Template Module - RootModule | 3-element version | Module Import from UNC path
11
+
- Fix: Template-System - Bad default template store path on linux or mac. (#106)
4
12
5
13
## 2.2.6.72 (May 27th, 2019)
6
14
- New: Template AzureFunction - Creates a basic azure function scaffold
if (-not$Env:AppData) { $path_FileUserShared=Join-Path ([Environment]::GetFolderPath("ApplicationData")) "$psVersionName\PSFramework\Config" }
14
+
}
15
+
16
+
# The parameter identifier used to detect and insert parameters
2
17
Set-PSFConfig-Module 'PSModuleDevelopment'-Name 'Template.Identifier'-Value 'þ'-Initialize -Validation 'string'-Description "The identifier used by the template system to detect and insert variables / scriptblock values"
Set-PSFConfig-Module 'PSModuleDevelopment'-Name 'Template.BinaryExtensions'-Value @('.dll','.exe','.pdf','.doc','.docx','.xls','.xlsx') -Initialize -Description "When creating a template, files with these extensions will be included as raw bytes and not interpreted for parameter insertion."
10
25
11
26
# Define the default store. To add more stores, just add a similar setting with a different last name segment
12
-
Set-PSFConfig-Module 'PSModuleDevelopment'-Name 'Template.Store.Default'-Value "$env:APPDATA\WindowsPowerShell\PSModuleDevelopment\Templates"-Initialize -Validation "string"-Description "Path to the default directory where PSModuleDevelopment will store its templates. You can add additional stores by creating the same setting again, only changing the last name segment to a new name and configuring a separate path."
13
-
Set-PSFConfig-Module 'PSModuleDevelopment'-Name 'Template.Store.PSModuleDevelopment'-Value "$script:PSModuleRoot\internal\templates"-Initialize -Validation "string"-Description "Path to the templates shipped in PSModuleDevelopment"
27
+
Set-PSFConfig-Module 'PSModuleDevelopment'-Name 'Template.Store.Default'-Value "$path_FileUserShared\WindowsPowerShell\PSModuleDevelopment\Templates"-Initialize -Validation "string"-Description "Path to the default directory where PSModuleDevelopment will store its templates. You can add additional stores by creating the same setting again, only changing the last name segment to a new name and configuring a separate path."
28
+
Set-PSFConfig-Module 'PSModuleDevelopment'-Name 'Template.Store.PSModuleDevelopment'-Value "$script:ModuleRoot\internal\templates"-Initialize -Validation "string"-Description "Path to the templates shipped in PSModuleDevelopment"
14
29
15
30
# Define the default path to create from templates in
16
31
Set-PSFConfig-Module 'PSModuleDevelopment'-Name 'Template.OutPath'-Value '.'-Initialize -Validation 'string'-Description "The path where new files & projects should be created from templates by default."
Set-PSFConfig-Module PSModuleDevelopment -Name 'Wix.profile.path'-Value "$env:APPDATA\WindowsPowerShell\PSModuleDevelopment\Wix"-Initialize -Validation "string"-Handler { } -Description "The path where the wix commands store and look for msi building profiles by default."
2
-
Set-PSFConfig-Module PSModuleDevelopment -Name 'Wix.profile.default'-Value ""-Initialize -Validation "string"-Handler { } -Description "The default profile to build. If this is specified, 'Invoke-PSMDWixBuild' will build this profile when nothing else is specified."
1
+
#Set-PSFConfig -Module PSModuleDevelopment -Name 'Wix.profile.path' -Value "$env:APPDATA\WindowsPowerShell\PSModuleDevelopment\Wix" -Initialize -Validation "string" -Handler { } -Description "The path where the wix commands store and look for msi building profiles by default."
2
+
#Set-PSFConfig -Module PSModuleDevelopment -Name 'Wix.profile.default' -Value " " -Initialize -Validation "string" -Handler { } -Description "The default profile to build. If this is specified, 'Invoke-PSMDWixBuild' will build this profile when nothing else is specified."
# If there is no global override for the config path, use module default path
20
4
# Note: Generally, you shouldn't enforce checking on the global scope for variables. Since importing modules however is a global action, this is an exception
0 commit comments