GitVersion.MSBuild Runtimes #4627
Replies: 1 comment 4 replies
-
@arturcic Do you have an answer on this question? |
Beta Was this translation helpful? Give feedback.
-
We actually embed the cli tool in order to be able to call it and then consume the json output |
Beta Was this translation helpful? Give feedback.
-
|
So why does it not work in visual studio 6.x.x and beyond for GitVersion.MsBuild? |
Beta Was this translation helpful? Give feedback.
-
|
The reason was, as far as I remember, the processing of the json output and enabling the features in that package is requiring GitVersion.Core, which is targeting .net 8.0. To make it usable in Visual Studio, the package should target .net Framework instead, or net standard. This limits the API surface we can use, that's why it's not enabled in Visual Studio |
Beta Was this translation helpful? Give feedback.
-
|
Aw okay, that make sense. it might be something I toy around with to see if I can get working in a sensible way. Thanks for the info! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey folks,
First off, honestly great work with this project and I have been using it for years.
One thing I came across was how version 6.x.x does not support Visual Studio anymore. While not having the version set should be fine, because our product is released with ci. If you reference GitVersionInformation, the project will no longer compile. That is quite the deal breaker.
Looking into it and bugs, it looks like it is caused by the issues with the different runtimes. The question is, why does it have a runtime dependency at all? Can't you just run the cli version of GitVersion and parse the output rather then requiring the net runtimes?
I have written quite a few msbuild custom tasks in the past and have not come across the issue seen here. So the question comes from part of improving my knowledge.
Thank you !
Beta Was this translation helpful? Give feedback.
All reactions