3 packages tagged with “Automatically”
Automatically creates a NuGet package from your project each time it builds. The NuGet package is placed in the project's output directory. If you want to use a .nuspec file, place it in the same directory as the project's project file (e.g. .csproj, .vbproj, .fsproj). This adds a PostBuildScripts folder to your project to house the PowerShell script that is called from the project's Post-Build event to create the NuGet package. If it does not seem to be working, check the Visual Studio Output window for any errors that may have occurred.
Automatically force your ClickOnce app to update itself without prompting the user, making a less obtrusive end-user experience, and guaranteeing they are always using the latest version of the application. Adds a post-build event to the project to run a PowerShell script that updates the ClickOnce project's minimum required version in the .csproj/.vbproj file to the latest published version. Because the PowerShell script modifies the .csproj/.vbproj file outside of Visual Studio, the first time you do a build after publishing a new ClickOnce version, if you have any files from that project open you will be prompted to reload the project. In order to prevent this from closing your open tabs, I recommend installing Scott Hanselman’s Workspace Reloader Visual Studio extension. If it does not seem to be working or causes the build to fail, check the Output window for any errors that may have occurred.
Automatically adjust textarea width/height based on user input.