AppVeyor not detecting .NetStandard / Core project in multi project solution
I have a solution with 4 projects. (Seen here: https://github.com/AdysTech/InfluxDB.Client.Net/tree/NetCoreSupport)
1. a classic .Net 4.5 class library
2. netstandard class library targeting 1.6 (using csproj syntax supported by latest dotnet)
3. MS Test project linking to .Net 4.5
4. netcore test project referencing netstandard project. (again csproj file)
I am using dotnet-dev-1.0.0-preview2.1-003177 included with Visual Studio 2017 RC. I am using the appveyor.yml from same branch. For some reason AppVeyor only detects .Net 4.5 part of the solution and works fine. Could you please guide me to enable building both solution projects, and executing both test projects?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Ilya Finkelshte... on Mar 09, 2017 @ 12:37 AM
Hello,
I enabled
Visual Studio 2017 RC
build worker image for you and sent PR to configure it. This should help.Ilya.
2 Posted by Ilya Finkelshte... on Mar 09, 2017 @ 12:39 AM
Note that you may need to do the same changes in
NetCoreSupport
branch to test it first.3 Posted by mvadu on Mar 09, 2017 @ 03:38 AM
Thank you.. I merged the PR, and have few problems:
1. Initially it was still using
Nuget restore
, which made it to fail2. Changed it to
dotnet restore
and it still failed in the build stage as msbuild is not able to compile the core projectIn my dev machine, running the same commands on the solution folder works just fine:
How do I force the build to use
dotnet build
instead ofmsbuild
4 Posted by Ilya Finkelshte... on Mar 10, 2017 @ 03:54 AM
As I said you need this change in
NetCoreSupport
branch too. I sent another PR, I hope you get the idea.As you can see this build went OK in my fork.
I would not recommend
dotnet build
for mixed solution, but if you really want it, you can run any command you like asbuild_script
. Note that automatic build and nuget packaging will not work if you choosebuild_script
. To get right syntax you can set it in UI, and then useExport YAML
. But again for your case automatic msbuild should be just fine.Ilya Finkelshteyn closed this discussion on Aug 25, 2018 @ 02:15 AM.