Home/ Questions/Q 6099543
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T13:17:06+00:00

I am developing a nuget package which will set up the current project to

  • 0

I am developing a nuget package which will set up the current project to use my company’s assembly versioning standard. I’ve got it doing everything I want (so far) smoothly apart from adding in a custom build step.

Historically this has been done manually by editing the .csproj file directly and adding in a couple of new tags into the xml. These are …

  • Property Group
  • Target

It actually adds them in successfully, but i’ve done it by editing the xml rather than via the EnvDTE object in the $project parameter in install.ps1. But I get a message popping up asking my if I want to discard my changes.

I’ve added $project.Save() to my script just before I make the changes and that gets rid of the popup, and I just get the one telling me the project has changed and asking me if I want to reload it. Which is better, but still not quite perfect.

Is there a better way to do this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can also use the NuGetPowerTools package written by David Fowler (NuGet lead developer). 

    Install-Package NuGetPowerTools

    Add it as a dependency to your package, then in the install.ps1 script, you can call:

    Add-Import "\Path\To\Import.targets" $project.ProjectName
Set-MSBuildProperty "MyPropertyName" "MyPropertyValue" $project.ProjectName

$value = Get-MSBuildProperty "MyPropertyName" $project.ProjectName

    Check out the code at https://github.com/davidfowl/NuGetPowerTools for more info.

    • 0