dahall / intentionalsolutionversion Goto Github PK

Any plans to make this extension available for Visual Studio 2022?

Error message changed! But problem is not solved - still fails on start...

Google says that in english error looks like "System.InvalidCastException"

When trying to install this extension in Visual Studio 2019, I get a message that says "The following references must be present before installation can continue: Visual Studio MPF 15.0" and it does not allow me to install the extension.

Thank you for the extension. I appreciate it's transparency about where the changes are being made.

I noticed, however, that If AssemblyInfo.cs contains commented lines and they are before non-commented line - the commented line is displayed and changed instead of actual line:

// [assembly: AssemblyVersion("1.0.0")]
[assembly: AssemblyVersion("1.1.1.0")]

Only the first line will be displayed in Update solution versions window and after changing the version it will be the only line that changed.

When updating version info empty lines are removed. I don't know if anything else is affected but it should only touch version tags.

Thanks

Now it works fine with changing version from 2.12.1 to 2.12.2 for example, BUT there is 4-th part of project version (build). I really need to change version from 2.12.1.2 to 2.12.1.3.

Help please!

Currently (version 1.1.2) Update solutions window displays xmlns=".." text which is not actually part of the line representing the relevant Version field (i.e. line 3 in the example below):

Actual line looks like:

<ApplicationVersion>1.2.2.0</ApplicationVersion>

The latest release (1.2.0) changed some functionality...

BTW, I love this tool and really appreciate all that you do! This makes our versioning much easier especially since we use VersionPrefix in our .csproj files (which allows us to specify a version suffix from our pipeline).

This is the Version that we are wanting to upgrade to 2.11.0 (this is a snippet from the .csproj file)
<VersionPrefix>2.10.0</VersionPrefix>

After running the tool with these settings:

These are the results after running the tool with those setting:
<VersionPrefix>2.11.0.0</VersionPrefix>

As you can see it appended on a .0 to the version number. I did not expect this behavior since I did not select Use 4th version segment.

Recently (last month or two), the extension quit recognizing existing version information in my projects. Everything is recognized as version number 0.0.0. It used to display the version numbers in the .csproj files and would show both the values in the ApplicationVersion and Version tags. I'm using .NET Standard and .NET Core projects in Visual Studio 2022.

I get an error as soon as I press the menu item to update the version info.

I am using:

• Visual Studio 2017 with a couple of important plugins that may possibly affect the world.
• ReSharper
• Vsvim
• Supercharger

I have tried it on three solutions and get the same problem:

Solution 1

• Two csproj projects
• Both projects are class library projects
• Both projects are .NET Framework 4.6.1
• Both project names have periods in the name like "x.y.z"

Solution 2

• Several csproj project projects
• Some projects are nested under solution folders
• All projects are .NET Framework 4.6.1
• All project files are named similar to Solution 1

Solution 3

• Three csproj projects
• Simple names in the projects (no periods in the name)
• .NET Framework 4.6.1

The code is proprietary so, unfortunately, I can not make it available. :(

I really want this to work so I can try to do different things to help. If you can provide a version with lots of debug lines or something, I will be more than happy to install it and get some output for you. I have done that before to help plugin developers.

In the project files the version of referenced NuGet packages is changed. This messes up the referenced NuGet packes. This version number must be managed by the NuGet package Manager.

    <PackageReference Include="Microsoft.EntityFrameworkCore.Sqlite">
      <Version>2.2.6</Version>     <==== DO NOT CHANGE THIS!
    </PackageReference>

I expect this tool to update the AssemblyVersion and AssemblyFileVersion. I.e., the version number I publish, not imported version numbers.