Hmm, tried adding  --self-contained true  -r win10-x64 to my publish .net core 
step in build pipeline on Devops.
Builds ok and seems to deploy but I still am getting a web page timeout with 
message
"HTTP Error 503. The service is unavailable."

Might have some other runtime start issue. Am logging but not sure if its 
happening before logging kicks in, will see if I can find the logs. Azure 
logging seems weird, I think I need to turn it on and then it turns off 
automatically after a time period.
________________________________
From: ozdotnet-boun...@ozdotnet.com <ozdotnet-boun...@ozdotnet.com> on behalf 
of Nick Randolph <n...@builttoroam.com>
Sent: Sunday, 29 September 2019 8:39 PM
To: ozDotNet <ozdotnet@ozdotnet.com>
Subject: RE: Core 3.0 and C# 8


Hey have you tried adjusting the packaging options when publishing to Azure 
–There’s an option where it doesn’t rely on the shared runtime which should 
mean that v3 will work even prior to Azure being updated.



I just tried it with a new ASP.NET Core v3 project. On initial publish I was 
getting a 500 error. When I changed the Deployment Mode to Self Contained it 
published and ran fine.



Hope this helps



[cid:image001.jpg@01D57716.CDE1F0A0]



Nick Randolph | Built to Roam Pty Ltd | Co-Founder, Technical Lead | +61 412 
413 425 | 1300 613 140 | www.builttoroam.com<https://www.builttoroam.com/>
| The information contained in this email is confidential. If you are not the 
intended recipient, you may not disclose or use the information in this email 
in any way. Built to Roam Pty Ltd does not guarantee the integrity of any 
emails or attached files. The views or opinions expressed are the author's own 
and may not reflect the views or opinions of Built to Roam Pty Ltd.



From: ozdotnet-boun...@ozdotnet.com <ozdotnet-boun...@ozdotnet.com> On Behalf 
Of Stephen Price
Sent: Sunday, 29 September 2019 12:17 PM
To: ozDotNet <ozdotnet@ozdotnet.com>
Subject: Re: Core 3.0 and C# 8



I've upgraded a project with some minor changes (method calls no longer needed, 
AddDefaultUI() for example) and all works locally.

Deployed to Azure and entirely broken. Turns out all of Azure web apps seem to 
be running core 2.2. There is an Azure status dashboard which shows all of the 
current versions on the various regions. Link to that tweeted by Damian Edwards 
recently. (Don't have it handy on my phone right now).

Apparently it's being rolled out in the next week. Seems odd that core 3.0 is 
released but Azure isn't ready, but you get that.

I didn't see preview extensions on my web app, they looked like SDK 3.0 
Extentions so no idea why site isn't running. It doesn't even start so can't 
debug it. Will try again after Azure shows 3.0

The actual upgrade was trivial, so that's good.

Cheers

Stephen



________________________________

From: ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com> 
<ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com>> on behalf 
of ste...@malikoff.com<mailto:ste...@malikoff.com> 
<ste...@malikoff.com<mailto:ste...@malikoff.com>>
Sent: Sunday, September 29, 2019 8:08:04 AM
To: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>
Subject: Re: Core 3.0 and C# 8



I have Core 3.0 in VS2019CE Preview, but not available in VS2019CE (out of the 
box - I have
not touched any project files etc) as per the comments on
https://stackoverflow.com/questions/55032756/asp-net-core-3-0-not-showing-on-visual-studio-2019

Steve.



---------------------------- Original Message ----------------------------
Subject: Core 3.0 and C# 8
From:    "Greg Keogh" <gfke...@gmail.com<mailto:gfke...@gmail.com>>
Date:    Fri, September 27, 2019 2:18 pm
To:      "ozDotNet" <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>>
--------------------------------------------------------------------------

> Folks,
>
> I'm keen to experiment with C# 8 features and get familiar early, but I
> can't get any project to use it. In Visual Studio 2019 16.2.3 I've tried to
> create Standard, Core and Framework projects of all the latest versions,
> then set the Build Advanced Language Version to 8 or preview, but it's
> never available.
>
> I thought Core 3.0 projects could use C# 8, but the highest choice I have
> is 2.2. So I installed 3.0 manually and dotnet --list shows me the
> following (truncated) as installed, but I never see 3.0 list in target
> frameworks.
>
>>dotnet --list-runtimes
> Microsoft.AspNetCore.App 3.0.0 [C:\Program
> Files\dotnet\shared\Microsoft.AspNetCore.App]
> Microsoft.NETCore.App 3.0.0 [C:\Program
> Files\dotnet\shared\Microsoft.NETCore.App]
> Microsoft.WindowsDesktop.App 3.0.0 [C:\Program
> Files\dotnet\shared\Microsoft.WindowsDesktop.App]
>>dotnet --list-sdks
> 3.0.100 [C:\Program Files\dotnet\sdk]
>
> So I have two issues: (1) I can't pick Core 3.0 Framework (2) How on earth
> do I coax C# 8 into action?
>
> Any advice would be most welcome. Perhaps there are really strict
> conditions or dependencies I'm not aware of.
>
> Cheers,
> *Greg*
>
> P.S. Public holiday in Melbourne for some sort of ball game. A horse race I
> can understand, but this?
>

Reply via email to