Home → Suggestions →

Add a Visual Studio 2017 RC environment

• Edit

Daniel Cazzulino

17 Nov, 2016 06:05 AM

Now that it's finally publicly available since yesterday ;)

1. Support Staff 1 Posted by Feodor Fitsner on 17 Nov, 2016 06:43 PM

   

   Absolutely, will be working on that next week. There is an item: https://github.com/appveyor/ci/issues/1179

   Thinking about doing a fresh image with VS 2017 and based on Windows Server 2016. Does it make sense?

   • Edit

2. 2 Posted by desautelsj on 17 Nov, 2016 08:53 PM

   

   +1

   • Edit

3. 3 Posted by Daniel Cazzulin... on 28 Nov, 2016 10:43 PM

   

   Sounds great. Just got added to it, testing it now.

   • Edit

4. 4 Posted by ellipticalweb on 17 Jan, 2017 10:20 AM

   

   No issues w/ VS 2017 RC image building projects. However, packages aren't getting pushed to nuget. .net core no longer uses nuspec file, instead relying on PropertyGroup tag in the .csproj file. Is there a specific instruction in the appveyor file that needs to be included to ensure packages get pushed up?

   • Edit

5. 5 Posted by Ilya Finkelshte... on 18 Jan, 2017 09:41 PM

   

   @ellipticalweb Could you please drop your YAML configuration?

   • Edit

6. 6 Posted by ellipticalweb on 19 Jan, 2017 08:38 AM

   

   example:

   https://github.com/RevStackCore/Pattern/blob/master/appveyor.yml

   • Edit

7. 7 Posted by Ilya Finkelshte... on 19 Jan, 2017 10:16 PM

   

   @ellipticalweb When publish_nuget: true is set, AppVeyor tries to pack nuget packages and publish them as artifacts. However we still rely on existence of .nuspec files to make a decision what project to run nuget pack against.

   We are working on adjusting to the current reality. Here are 2 workarounds for you:

   • Add .nuspec file(s) just to make AppVeyor think about project as a nuget package.

   or

   • Do packaging explicitly:
     • Call nuget pack or dotnet pack as part of post build script
     • Add resultant files to artifacts with artifacts section in YAML or with appveyor PushArtifact command. More info
   • Edit

8. 8 Posted by ellipticalweb on 22 Jan, 2017 12:18 AM

   

   Thanx for the response...

   Currently, I'm just doing dotnet pack -c to generate the package and then manually upload as the workaround.

   • Edit

9. 9 Posted by ellipticalweb on 22 Jan, 2017 06:18 PM

   

   Hmmm, encountered one build problem in this repo:

   https://github.com/RevStackCore/Extensions.Net

   with the error message:

   "The type or namespace name 'Resources' does not exist in the namespace 'System' (are you missing an assembly reference?)"

   No issue with local build nor with the local nuget package generation.

   obj\Release\netstandard1.5\RevStackCore.Extensions.Net.AssemblyInfo.cs(23,19): error CS0234: The type or namespace name 'Resources' does not exist in the namespace 'System' (are you missing an assembly reference?) [C:\projects\extensions-net\RevStackCore.Extensions.Net\RevStackCore.Extensions.Net.csproj]

   • Edit

10. 10 Posted by Ilya Finkelshte... on 23 Jan, 2017 08:15 PM

    

    What Visual Studio version this solution was created in? Please check this line. Did you open in in VS 2017?

    • Edit

11. 11 Posted by Ilya Finkelshte... on 24 Jan, 2017 02:22 AM

    

    I sent PR with the fix. I cannot understand how it could build locally though.

    • Edit

12. 12 Posted by ellipticalweb on 24 Jan, 2017 03:59 AM

    

    What Visual Studio version this solution was created in? Please check this line. Did you open in in VS 2017?

    Visual Studio for Mac, preview 3. The referenced line is in every VS 2017 solution file. E.g

    Example with no build problem

    • Edit

13. 13 Posted by ellipticalweb on 24 Jan, 2017 04:15 AM

    

    I sent PR with the fix. I cannot understand how it could build locally though.

    I merged the pull request and the subsequent build passed. Thanx.

    Should note: I'm using the visual studio alpha channel and recently upgraded to preview 3 from 2. Preview 3 behaves a bit differently than 2 in terms of the .csproj file. It doesn't add in a package reference to the .net standard library nor the sdk. It builds fine locally and other repos coded with preview 3 have built successfully on appveyor using the same Visual Studio 2017 RC image.

    • Edit

14. 14 Posted by Daniel Cazzulin... on 14 Mar, 2018 03:20 AM

    

    Feel free to close this issue, although latest & greatest previews are shipping all the time ;)

    • Edit

15. Daniel Cazzulino closed this discussion on 14 Mar, 2018 03:56 AM.