tag:help.appveyor.com,2012-11-13:/discussions/suggestions/1138-add-a-visual-studio-2017-rc-environmentAppVeyor: Discussion 2018-10-19T08:18:06Ztag:help.appveyor.com,2012-11-13:Comment/412457512016-11-17T18:43:19Z2016-11-17T18:43:19ZAdd a Visual Studio 2017 RC environment<div><p>Absolutely, will be working on that next week. There is an item:
<a href="https://github.com/appveyor/ci/issues/1179">https://github.com/appveyor/ci/issues/1179</a></p>
<p>Thinking about doing a fresh image with VS 2017 and based on
Windows Server 2016. Does it make sense?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/412457512016-11-17T20:53:31Z2016-11-17T20:53:31ZAdd a Visual Studio 2017 RC environment<div><p>+1</p></div>desautelsjtag:help.appveyor.com,2012-11-13:Comment/412457512016-11-28T22:43:59Z2016-11-28T22:43:59ZAdd a Visual Studio 2017 RC environment<div><p>Sounds great. Just got added to it, testing it now.</p></div>Daniel Cazzulinotag:help.appveyor.com,2012-11-13:Comment/412457512017-01-17T10:20:14Z2017-01-17T10:20:17ZAdd a Visual Studio 2017 RC environment<div><p>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?</p></div>ellipticalwebtag:help.appveyor.com,2012-11-13:Comment/412457512017-01-18T21:41:28Z2017-01-18T21:41:28ZAdd a Visual Studio 2017 RC environment<div><p><strong>@ellipticalweb</strong> Could you please drop your YAML
configuration?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/412457512017-01-19T08:38:55Z2017-01-19T08:38:57ZAdd a Visual Studio 2017 RC environment<div><p>example:</p>
<p><a href="https://github.com/RevStackCore/Pattern/blob/master/appveyor.yml">https://github.com/RevStackCore/Pattern/blob/master/appveyor.yml</a></p></div>ellipticalwebtag:help.appveyor.com,2012-11-13:Comment/412457512017-01-19T22:16:46Z2017-01-19T22:16:46ZAdd a Visual Studio 2017 RC environment<div><p><strong>@ellipticalweb</strong> When <code>publish_nuget:
true</code> is set, AppVeyor tries to pack nuget packages and
publish them as artifacts. However we still rely on existence of
<code>.nuspec</code> files to make a decision what project to run
<code>nuget pack</code> against.</p>
<p>We are working on adjusting to the current reality. Here are 2
workarounds for you:</p>
<ul>
<li>Add <code>.nuspec</code> file(s) just to make AppVeyor think
about project as a nuget package.</li>
</ul>
<p>or</p>
<ul>
<li>Do packaging explicitly:
<ul>
<li>Call <code>nuget pack</code> or <code>dotnet pack</code> as
part of post build script</li>
<li>Add resultant files to artifacts with <code>artifacts</code>
section in YAML or with <code>appveyor PushArtifact</code> command.
<a href="https://www.appveyor.com/docs/packaging-artifacts/">More
info</a></li>
</ul>
</li>
</ul></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/412457512017-01-22T00:18:44Z2017-01-22T00:18:47ZAdd a Visual Studio 2017 RC environment<div><p>Thanx for the response...</p>
<p>Currently, I'm just doing dotnet pack -c to generate the package
and then manually upload as the workaround.</p></div>ellipticalwebtag:help.appveyor.com,2012-11-13:Comment/412457512017-01-22T18:18:28Z2017-01-22T18:19:04ZAdd a Visual Studio 2017 RC environment<div><p>Hmmm, encountered one build problem in this repo:</p>
<p><a href="https://github.com/RevStackCore/Extensions.Net">https://github.com/RevStackCore/Extensions.Net</a></p>
<p>with the error message:</p>
<p>"The type or namespace name 'Resources' does not exist in the
namespace 'System' (are you missing an assembly reference?)"</p>
<p>No issue with local build nor with the local nuget package
generation.</p>
<p>
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]</p></div>ellipticalwebtag:help.appveyor.com,2012-11-13:Comment/412457512017-01-23T20:15:33Z2017-01-23T20:15:33ZAdd a Visual Studio 2017 RC environment<div><p>What Visual Studio version this solution was created in? Please
check <a href="https://github.com/RevStackCore/Extensions.Net/blob/master/RevStackCore.Extensions.Net.sln#L3">
this</a> line. Did you open in in VS 2017?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/412457512017-01-24T02:22:13Z2017-01-24T02:22:13ZAdd a Visual Studio 2017 RC environment<div><p>I sent <a href="https://github.com/RevStackCore/Extensions.Net/pulls">PR</a> with
the fix. I cannot understand how it could build locally though.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/412457512017-01-24T03:59:30Z2017-01-24T03:59:31ZAdd a Visual Studio 2017 RC environment<div><blockquote>
<p>What Visual Studio version this solution was created in? Please
check this line. Did you open in in VS 2017?</p>
</blockquote>
<p>Visual Studio for Mac, preview 3. The referenced line is in
every VS 2017 solution file. E.g</p>
<p><a href="https://github.com/RevStackCore/Redis.Client/blob/master/RevStackCore.Redis.Client.sln">
Example with no build problem</a></p></div>ellipticalwebtag:help.appveyor.com,2012-11-13:Comment/412457512017-01-24T04:15:34Z2017-01-24T04:15:35ZAdd a Visual Studio 2017 RC environment<div><blockquote>
<p>I sent PR with the fix. I cannot understand how it could build
locally though.</p>
</blockquote>
<p>I merged the pull request and the subsequent build passed.
Thanx.</p>
<p>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.</p></div>ellipticalwebtag:help.appveyor.com,2012-11-13:Comment/412457512018-03-14T03:20:22Z2018-03-14T03:20:22ZAdd a Visual Studio 2017 RC environment<div><p>Feel free to close this issue, although latest & greatest previews are shipping all the time ;)</p></div>Daniel Cazzulino