docs: Fix wrong folder name to change PostBuildEvents to PostBuildScripts

Author: deadlydog

AutoUpdateProjectsMinimumRequiredClickOnceVersion.sln

@@ -0,0 +1,51 @@
+
+Microsoft Visual Studio Solution File, Format Version 12.00
+# Visual Studio Version 17
+VisualStudioVersion = 17.5.002.0
+MinimumVisualStudioVersion = 10.0.40219.1
+Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "src", "src", "{522E6653-AA2F-4080-AB14-0FA4E6E84382}"
+EndProject
+Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "1 - TestProject - Before turning on automatic updates and enforce min version", "src\ChangesVisualStudioMakesToProjectFileThatNeedToBeMimicked\1 - TestProject - Before turning on automatic updates and enforce min version.csproj", "{09A4A572-9C19-4DB6-AE7F-613B62B0C535}"
+EndProject
+Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "2 - TestProject - After turning on min version", "src\ChangesVisualStudioMakesToProjectFileThatNeedToBeMimicked\2 - TestProject - After turning on min version.csproj", "{068ADA5A-54EB-4142-8C02-B949387F675C}"
+EndProject
+Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "3 - TestProject - After turning on automatic updates and enforce min version", "src\ChangesVisualStudioMakesToProjectFileThatNeedToBeMimicked\3 - TestProject - After turning on automatic updates and enforce min version.csproj", "{156C17E1-A9B0-4C17-B801-68F90FF49D7F}"
+EndProject
+Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "4 - TestProject - Already on the latest version", "src\ChangesVisualStudioMakesToProjectFileThatNeedToBeMimicked\4 - TestProject - Already on the latest version.csproj", "{C0D0E0E6-8303-41B0-82FC-303CF58EE74C}"
+EndProject
+Global
+	GlobalSection(SolutionConfigurationPlatforms) = preSolution
+		Debug|Any CPU = Debug|Any CPU
+		Release|Any CPU = Release|Any CPU
+	EndGlobalSection
+	GlobalSection(ProjectConfigurationPlatforms) = postSolution
+		{09A4A572-9C19-4DB6-AE7F-613B62B0C535}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
+		{09A4A572-9C19-4DB6-AE7F-613B62B0C535}.Debug|Any CPU.Build.0 = Debug|Any CPU
+		{09A4A572-9C19-4DB6-AE7F-613B62B0C535}.Release|Any CPU.ActiveCfg = Release|Any CPU
+		{09A4A572-9C19-4DB6-AE7F-613B62B0C535}.Release|Any CPU.Build.0 = Release|Any CPU
+		{068ADA5A-54EB-4142-8C02-B949387F675C}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
+		{068ADA5A-54EB-4142-8C02-B949387F675C}.Debug|Any CPU.Build.0 = Debug|Any CPU
+		{068ADA5A-54EB-4142-8C02-B949387F675C}.Release|Any CPU.ActiveCfg = Release|Any CPU
+		{068ADA5A-54EB-4142-8C02-B949387F675C}.Release|Any CPU.Build.0 = Release|Any CPU
+		{156C17E1-A9B0-4C17-B801-68F90FF49D7F}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
+		{156C17E1-A9B0-4C17-B801-68F90FF49D7F}.Debug|Any CPU.Build.0 = Debug|Any CPU
+		{156C17E1-A9B0-4C17-B801-68F90FF49D7F}.Release|Any CPU.ActiveCfg = Release|Any CPU
+		{156C17E1-A9B0-4C17-B801-68F90FF49D7F}.Release|Any CPU.Build.0 = Release|Any CPU
+		{C0D0E0E6-8303-41B0-82FC-303CF58EE74C}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
+		{C0D0E0E6-8303-41B0-82FC-303CF58EE74C}.Debug|Any CPU.Build.0 = Debug|Any CPU
+		{C0D0E0E6-8303-41B0-82FC-303CF58EE74C}.Release|Any CPU.ActiveCfg = Release|Any CPU
+		{C0D0E0E6-8303-41B0-82FC-303CF58EE74C}.Release|Any CPU.Build.0 = Release|Any CPU
+	EndGlobalSection
+	GlobalSection(SolutionProperties) = preSolution
+		HideSolutionNode = FALSE
+	EndGlobalSection
+	GlobalSection(NestedProjects) = preSolution
+		{09A4A572-9C19-4DB6-AE7F-613B62B0C535} = {522E6653-AA2F-4080-AB14-0FA4E6E84382}
+		{068ADA5A-54EB-4142-8C02-B949387F675C} = {522E6653-AA2F-4080-AB14-0FA4E6E84382}
+		{156C17E1-A9B0-4C17-B801-68F90FF49D7F} = {522E6653-AA2F-4080-AB14-0FA4E6E84382}
+		{C0D0E0E6-8303-41B0-82FC-303CF58EE74C} = {522E6653-AA2F-4080-AB14-0FA4E6E84382}
+	EndGlobalSection
+	GlobalSection(ExtensibilityGlobals) = postSolution
+		SolutionGuid = {F12AB66E-08EA-4BA8-A53E-A3709EF46B72}
+	EndGlobalSection
+EndGlobal

ReadMe.md

@@ -31,11 +31,11 @@ Unfortunately the PackageReference format does not support NuGet packages runnin
 Instead of using the NuGet package, you will instead need to manually add the PowerShell script to your project, and add the post-build event to the project file.
 The steps to do this are:
 
-1. In Visual Studio, right-click on your project and add a new folder called `PostBuildEvents`.
-1. Download [the latest AutoUpdateProjectsMinimumRequiredClickOnceVersion.ps1 PowerShell script](https://github.com/deadlydog/AutoUpdateProjectsMinimumRequiredClickOnceVersion/releases) and save it to the `PostBuildEvents` folder.
-1. You should now see the PowerShell script in the `PostBuildEvents` folder in Solution Explorer.
-   1. If you do not see the PowerShell file in Visual Studio, right-click on the `PostBuildEvents` folder and choose `Add` > `Existing Item...`.
-   Select the PowerShell script that you downloaded and saved to the `PostBuildEvents` folder.
+1. In Visual Studio, right-click on your project and add a new folder called `PostBuildScripts`.
+1. Download [the latest AutoUpdateProjectsMinimumRequiredClickOnceVersion.ps1 PowerShell script](https://github.com/deadlydog/AutoUpdateProjectsMinimumRequiredClickOnceVersion/releases) and save it to the `PostBuildScripts` folder.
+1. You should now see the PowerShell script in the `PostBuildScripts` folder in Solution Explorer.
+   1. If you do not see the PowerShell file in Visual Studio, right-click on the `PostBuildScripts` folder and choose `Add` > `Existing Item...`.
+   Select the PowerShell script that you downloaded and saved to the `PostBuildScripts` folder.
 1. In Visual Studio, right-click on the project and choose `Properties`.
 1. Navigate to the `Build` > `Events` tab, and paste the following code into the `Post-build event` text box: