GithubHelp home page GithubHelp logo

Comments (5)

pms1969 avatar pms1969 commented on July 22, 2024

ah-ha. doesn't work at the solution level.... but seems to be working at a project level. How do I do this at a solution level?

from dotnet-setversion.

pms1969 avatar pms1969 commented on July 22, 2024

And additionally, if i run this in the microsoft/dotnet:2.0-sdk docker image, I get the following error:

root@79f59544b01b:~/app/implementation/Configuration# dotnet setversion 0.0.1
It was not possible to find any compatible framework version
The specified framework 'Microsoft.NETCore.App', version '1.0.4' was not found.
  - Check application dependencies and target a framework version installed at:
      /
  - Alternatively, install the framework version '1.0.4'.
root@79f59544b01b:~/app/implementation/Configuration#

from dotnet-setversion.

TAGC avatar TAGC commented on July 22, 2024

The dotnet:2.0-sdk thing is a separate issue (can be reposted as a new issue). For the solution level thing, I'm not sure it's possible to create solution-level CLI tools (what I've inferred from reading this).

I just include the tool in each project within a solution. At the solution level I have a bash script that cd's into each project directory and invokes the CLI command:

for d in src/* test/*
do
    cd $d
    dotnet setversion $1
    cd ../..
done

This assumes you want each project in a solution to have identical versions.

from dotnet-setversion.

pms1969 avatar pms1969 commented on July 22, 2024

Pretty much what I did. Thanks. I'll post the dotnet:2.0-sdk issue separately for you.

This is sooooo handy, that you might want to thing about contributing it back to the cli tool main branch, then it would be solution level.

from dotnet-setversion.

TAGC avatar TAGC commented on July 22, 2024

Since .NET Core transitioned back to *.csproj format, it's allowed doing things like $ dotnet build /property:"Version=1.2.3", and this works at a solution level. My tool works a little differently, and doing it the "official" way caused issues for me when I tried it out, but my guess is the in-built way would work okay for most people.

Unless it turns out otherwise, I don't think there's a major need to integrate this tool into the official .NET Core CLI repo.

from dotnet-setversion.

Related Issues (19)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.