New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Discussion] Prepare for the upcoming upgrade to .NET 4.7.2 #37

Open
davidebbo opened this Issue Mar 1, 2018 · 54 comments

Comments

Projects
None yet
@davidebbo
Contributor

davidebbo commented Mar 1, 2018

Discussion thread for Azure/app-service-announcements#89.

@niemyjski

This comment has been minimized.

Show comment
Hide comment
@niemyjski

niemyjski Mar 15, 2018

@davidebbo Would it be possible to have an azure site extension for latest stable as well as pre release versions of .net and .net core depending on the users selected deployment lane?

niemyjski commented Mar 15, 2018

@davidebbo Would it be possible to have an azure site extension for latest stable as well as pre release versions of .net and .net core depending on the users selected deployment lane?

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Mar 15, 2018

Contributor

@niemyjski It's not something that can be done via site extensions. There can be only one version of .NET 4.x on a given VM (by design of .NET fx), so you can't have a given app select among several.

Contributor

davidebbo commented Mar 15, 2018

@niemyjski It's not something that can be done via site extensions. There can be only one version of .NET 4.x on a given VM (by design of .NET fx), so you can't have a given app select among several.

@Daniel-Svensson

This comment has been minimized.

Show comment
Hide comment
@Daniel-Svensson

Daniel-Svensson May 2, 2018

Maybe this could handled by a setting on the app service plan itself (webfarm) in the future. With the rtm of 4.7.2 I see no big reason to have that for this version since I expect an update to be imminent. Would like to hear if an estimated date has been set.

Daniel-Svensson commented May 2, 2018

Maybe this could handled by a setting on the app service plan itself (webfarm) in the future. With the rtm of 4.7.2 I see no big reason to have that for this version since I expect an update to be imminent. Would like to hear if an estimated date has been set.

@Workshop2

This comment has been minimized.

Show comment
Hide comment
@Workshop2

Workshop2 May 5, 2018

Now it's released, what sort or time period until it's available? Weeks? Months?
https://blogs.msdn.microsoft.com/dotnet/2018/04/30/announcing-the-net-framework-4-7-2/

Workshop2 commented May 5, 2018

Now it's released, what sort or time period until it's available? Weeks? Months?
https://blogs.msdn.microsoft.com/dotnet/2018/04/30/announcing-the-net-framework-4-7-2/

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo May 5, 2018

Contributor

@Workshop2 likely a number of months, to let the initial wave of issues get ironed out. We've had problems in the past doing it too fast and breaking some customers due to .NET regressions that had not yet been found.

Are there specific 4.7.2 features that you are waiting for? Unless there is, there is no reason to target it.

Contributor

davidebbo commented May 5, 2018

@Workshop2 likely a number of months, to let the initial wave of issues get ironed out. We've had problems in the past doing it too fast and breaking some customers due to .NET regressions that had not yet been found.

Are there specific 4.7.2 features that you are waiting for? Unless there is, there is no reason to target it.

@Workshop2

This comment has been minimized.

Show comment
Hide comment
@Workshop2

Workshop2 May 5, 2018

Thanks for the quick response @davidebbo.

We have legacy webforms apps we'd like to take advantage of DI 👍

Workshop2 commented May 5, 2018

Thanks for the quick response @davidebbo.

We have legacy webforms apps we'd like to take advantage of DI 👍

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo May 5, 2018

Contributor

I see. Please keep comments coming on this thread. We will try the strike the right balance between limiting risk to existing apps, and enabling the new features. Note that we don't have the ability to deploy it on a per-app basis, so it will need to be part of a future global update.

Contributor

davidebbo commented May 5, 2018

I see. Please keep comments coming on this thread. We will try the strike the right balance between limiting risk to existing apps, and enabling the new features. Note that we don't have the ability to deploy it on a per-app basis, so it will need to be part of a future global update.

@richkgit

This comment has been minimized.

Show comment
Hide comment
@richkgit

richkgit May 8, 2018

We may switch to containers or other deployment options so as to be able to leverage framework updates. Between the DI updates zip performance, etc. we would need those for a current project updating a Web Forms app.

richkgit commented May 8, 2018

We may switch to containers or other deployment options so as to be able to leverage framework updates. Between the DI updates zip performance, etc. we would need those for a current project updating a Web Forms app.

@mrahl

This comment has been minimized.

Show comment
Hide comment
@mrahl

mrahl May 21, 2018

We would like to see the update sooner rather than later. We have had many customer escalations where the root cause is the cache memory monitor bugs 531575 and 531576 (mentioned here https://github.com/Microsoft/dotnet-framework-early-access/blob/master/release-notes/build-3052/dotnet-build-3052-changes.md).

We know how to work around the bugs by configuration, but the problem is customers don't always realize what they are dealing with. They see stability problems (because the apps get killed over and over by proactive auto heal) and look in all the wrong places before even coming to us so we can connect the dots and suggest the workaround.

mrahl commented May 21, 2018

We would like to see the update sooner rather than later. We have had many customer escalations where the root cause is the cache memory monitor bugs 531575 and 531576 (mentioned here https://github.com/Microsoft/dotnet-framework-early-access/blob/master/release-notes/build-3052/dotnet-build-3052-changes.md).

We know how to work around the bugs by configuration, but the problem is customers don't always realize what they are dealing with. They see stability problems (because the apps get killed over and over by proactive auto heal) and look in all the wrong places before even coming to us so we can connect the dots and suggest the workaround.

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo May 21, 2018

Contributor

@mrahl there are some bad SqlClient related regressions in 4.7.2 (see Microsoft/dotnet#749). There needs to be a round of fixes on top of it before it can be deployed to app service.

Contributor

davidebbo commented May 21, 2018

@mrahl there are some bad SqlClient related regressions in 4.7.2 (see Microsoft/dotnet#749). There needs to be a round of fixes on top of it before it can be deployed to app service.

@rokonec

This comment has been minimized.

Show comment
Hide comment
@rokonec

rokonec May 24, 2018

Well - 4.7.2 has finally resolved package/dll hell of System.Net.Http
Upgrade to 4.7.2 is only way how to get rid of assembly conflict warning messages in out solution.
Guess we have to wait a little bit longer before we can leverage it in app services.

rokonec commented May 24, 2018

Well - 4.7.2 has finally resolved package/dll hell of System.Net.Http
Upgrade to 4.7.2 is only way how to get rid of assembly conflict warning messages in out solution.
Guess we have to wait a little bit longer before we can leverage it in app services.

@dmarlow

This comment has been minimized.

Show comment
Hide comment
@dmarlow

dmarlow May 24, 2018

Ugh, I just updated all my projects to 4.7.2 and fought with the binding redirect issues to get everything ironed out to find out that I have to go backwards now. :(

This can't be released soon enough for me.

dmarlow commented May 24, 2018

Ugh, I just updated all my projects to 4.7.2 and fought with the binding redirect issues to get everything ironed out to find out that I have to go backwards now. :(

This can't be released soon enough for me.

@smithkl42

This comment has been minimized.

Show comment
Hide comment
@smithkl42

smithkl42 May 30, 2018

The System.* DLL hell issues are a huge problem for us - we've spent many, many hours fighting with binding redirects, and it seems like we need to fix everything again every time we update a nuget package. We're informed that all this is fixed in .NET 4.7.2, and would love to switch over to it, but can't until app services supports it.

smithkl42 commented May 30, 2018

The System.* DLL hell issues are a huge problem for us - we've spent many, many hours fighting with binding redirects, and it seems like we need to fix everything again every time we update a nuget package. We're informed that all this is fixed in .NET 4.7.2, and would love to switch over to it, but can't until app services supports it.

@jonorogers

This comment has been minimized.

Show comment
Hide comment
@jonorogers

jonorogers Jun 4, 2018

I'm another one in the System.Net.Http binding redirect hell - app service support for 4.7.2 can't come quick enough, in my book.

Question; when an exception is thrown currently, Azure App Services reports the following:

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version: 4.7.2623.0

Does this mean it's already running 4.7.2, as it seems like it is?

jonorogers commented Jun 4, 2018

I'm another one in the System.Net.Http binding redirect hell - app service support for 4.7.2 can't come quick enough, in my book.

Question; when an exception is thrown currently, Azure App Services reports the following:

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version: 4.7.2623.0

Does this mean it's already running 4.7.2, as it seems like it is?

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Jun 4, 2018

Contributor

@jonorogers it has 4.7.1. Not sure I understand what part of this version string made you think it has 4.7.2.

Contributor

davidebbo commented Jun 4, 2018

@jonorogers it has 4.7.1. Not sure I understand what part of this version string made you think it has 4.7.2.

@jonorogers

This comment has been minimized.

Show comment
Hide comment
@jonorogers

jonorogers Jun 5, 2018

ASP.NET Version: 4.7.2623.0

@davidebbo That part confused me, I glanced at the version string and saw 4.7.2

jonorogers commented Jun 5, 2018

ASP.NET Version: 4.7.2623.0

@davidebbo That part confused me, I glanced at the version string and saw 4.7.2

@jrummell

This comment has been minimized.

Show comment
Hide comment
@jrummell

jrummell Jun 11, 2018

I'm also waiting for System.Net.Http fixes. Upgrading to 4.7.2 was the only way I found to get around the following VSTS View compilation error. I'm getting this in all of my web api projects with the Microsoft.AspNet.WebApi.HelpPage installed (e.g. dozens of projects).

Error CS0246: The type or namespace name 'MediaTypeHeaderValue' could not be found (are you missing a using directive or an assembly reference?)

So I can either upgrade to 4.7.2 to fix the VSTS build/release and not deploy to Azure (everything is in Azure), or publish manually from Visual Studio on a few very specific workstations that have the magic combination of .net, Visual Studio and pixie dust.

jrummell commented Jun 11, 2018

I'm also waiting for System.Net.Http fixes. Upgrading to 4.7.2 was the only way I found to get around the following VSTS View compilation error. I'm getting this in all of my web api projects with the Microsoft.AspNet.WebApi.HelpPage installed (e.g. dozens of projects).

Error CS0246: The type or namespace name 'MediaTypeHeaderValue' could not be found (are you missing a using directive or an assembly reference?)

So I can either upgrade to 4.7.2 to fix the VSTS build/release and not deploy to Azure (everything is in Azure), or publish manually from Visual Studio on a few very specific workstations that have the magic combination of .net, Visual Studio and pixie dust.

@mariuszdotnet

This comment has been minimized.

Show comment
Hide comment
@mariuszdotnet

mariuszdotnet Jun 20, 2018

Is the September 2018 still on track? As per Azure/app-service-announcements#89? I'm assuming that's applicable to ASE too?

mariuszdotnet commented Jun 20, 2018

Is the September 2018 still on track? As per Azure/app-service-announcements#89? I'm assuming that's applicable to ASE too?

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Jun 20, 2018

Contributor

@mariuszdotnet Yes, still on track for September, and that will include ASE.

Contributor

davidebbo commented Jun 20, 2018

@mariuszdotnet Yes, still on track for September, and that will include ASE.

@TheDude72

This comment has been minimized.

Show comment
Hide comment
@TheDude72

TheDude72 Jul 20, 2018

@davidebbo: Would there be any issues if I were to target .net framework 4.7.2 in my app and run on the .net framework 4.7.1 in the App Service? As long as I don't use any of the 4.7.2 features, I should be fine, right? So far, I haven't noticed any issues.

TheDude72 commented Jul 20, 2018

@davidebbo: Would there be any issues if I were to target .net framework 4.7.2 in my app and run on the .net framework 4.7.1 in the App Service? As long as I don't use any of the 4.7.2 features, I should be fine, right? So far, I haven't noticed any issues.

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Jul 20, 2018

Contributor

@TheDude72 I guess that would be fine, though if you're not using any new features it doesn't buy you much

Contributor

davidebbo commented Jul 20, 2018

@TheDude72 I guess that would be fine, though if you're not using any new features it doesn't buy you much

@dilv0055

This comment has been minimized.

Show comment
Hide comment
@dilv0055

dilv0055 Aug 13, 2018

May be not a right place to ask, but any plan for upgrading VSTS Hosted Agents .net framework version to 4.7.2 from 4.7.1?

dilv0055 commented Aug 13, 2018

May be not a right place to ask, but any plan for upgrading VSTS Hosted Agents .net framework version to 4.7.2 from 4.7.1?

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Aug 13, 2018

Contributor

@dilv0055 indeed, different team. I suggest trying https://github.com/Microsoft/vsts-agent

Contributor

davidebbo commented Aug 13, 2018

@dilv0055 indeed, different team. I suggest trying https://github.com/Microsoft/vsts-agent

@dkadmin

This comment has been minimized.

Show comment
Hide comment
@dkadmin

dkadmin Aug 16, 2018

Hi,

Can anyone confirm, if .net .4.7.1 will remain or will be deprecated after releasing .net 4.7.2?

dkadmin commented Aug 16, 2018

Hi,

Can anyone confirm, if .net .4.7.1 will remain or will be deprecated after releasing .net 4.7.2?

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Aug 16, 2018

Contributor

@dkadmin all VMs in Azure App Service will be upgraded to 4.7.2 as part of this change, so none will be running 4.7.1. But as stated in the announcement, this should not affect any deployed app unless you hit an unexpected 4.7.2 regression.

Contributor

davidebbo commented Aug 16, 2018

@dkadmin all VMs in Azure App Service will be upgraded to 4.7.2 as part of this change, so none will be running 4.7.1. But as stated in the announcement, this should not affect any deployed app unless you hit an unexpected 4.7.2 regression.

@dkadmin

This comment has been minimized.

Show comment
Hide comment
@dkadmin

dkadmin Aug 17, 2018

@davidebbo thanks for the details. I just want to confirm 1 more thing, as of now we can see 2 version available (v3.5 and v4.7) in webapp under application setting tab. So will be there 1 more new tab or will it remain same.

Thanks in advance.

dkadmin commented Aug 17, 2018

@davidebbo thanks for the details. I just want to confirm 1 more thing, as of now we can see 2 version available (v3.5 and v4.7) in webapp under application setting tab. So will be there 1 more new tab or will it remain same.

Thanks in advance.

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Aug 17, 2018

Contributor

@dkadmin that will not change. 4.7 really means 4.7.x, and it's just that it will move from 4.7.1 to 4.7.2.

Contributor

davidebbo commented Aug 17, 2018

@dkadmin that will not change. 4.7 really means 4.7.x, and it's just that it will move from 4.7.1 to 4.7.2.

@sampath42

This comment has been minimized.

Show comment
Hide comment
@sampath42

sampath42 Aug 20, 2018

Hi Davidebbo
This framework upgrade is only for app service? or is it applicable for the cloud services as well?
From your above comments, "all VMS will be upgraded to 4.7.2 as part of this change", does this mean all Azure VMs?

sampath42 commented Aug 20, 2018

Hi Davidebbo
This framework upgrade is only for app service? or is it applicable for the cloud services as well?
From your above comments, "all VMS will be upgraded to 4.7.2 as part of this change", does this mean all Azure VMs?

@dkadmin

This comment has been minimized.

Show comment
Hide comment
@dkadmin

dkadmin Aug 20, 2018

@davidebbo Thank you for all the info. I have one more quick quetion.
Will there be any impact on our web sites or not. which are hosted on app services? will there be any down time or any other impact.

dkadmin commented Aug 20, 2018

@davidebbo Thank you for all the info. I have one more quick quetion.
Will there be any impact on our web sites or not. which are hosted on app services? will there be any down time or any other impact.

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Aug 20, 2018

Contributor

@sampath42 This announcement only relates to App Service. I have clarified the sentence above.

@dkadmin There should be zero impact, outside of the very small chance of running into a .NET 4.7.2 regression that affects your app (hence the suggestion to test ahead).

Contributor

davidebbo commented Aug 20, 2018

@sampath42 This announcement only relates to App Service. I have clarified the sentence above.

@dkadmin There should be zero impact, outside of the very small chance of running into a .NET 4.7.2 regression that affects your app (hence the suggestion to test ahead).

@dkadmin

This comment has been minimized.

Show comment
Hide comment
@dkadmin

dkadmin Aug 21, 2018

@davidebbo thank you so much..

dkadmin commented Aug 21, 2018

@davidebbo thank you so much..

@itshemant09

This comment has been minimized.

Show comment
Hide comment
@itshemant09

itshemant09 Aug 30, 2018

Is that possible to check the feasibility whether this update .NET Framework 4.7.2 plan first in our pre-prod subscription, so that we will test our application/services thoroughly. @davidebbo

itshemant09 commented Aug 30, 2018

Is that possible to check the feasibility whether this update .NET Framework 4.7.2 plan first in our pre-prod subscription, so that we will test our application/services thoroughly. @davidebbo

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Aug 30, 2018

Contributor

@itshemant09 that is not an option due to the nature of our deployments. But you can test on a separate VM with the new framework.

Contributor

davidebbo commented Aug 30, 2018

@itshemant09 that is not an option due to the nature of our deployments. But you can test on a separate VM with the new framework.

@itshemant09

This comment has been minimized.

Show comment
Hide comment
@itshemant09

itshemant09 commented Aug 30, 2018

@davidebbo VN ???

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Aug 30, 2018

Contributor

Sorry, typo, VM.

Contributor

davidebbo commented Aug 30, 2018

Sorry, typo, VM.

@itshemant09

This comment has been minimized.

Show comment
Hide comment
@itshemant09

itshemant09 Aug 30, 2018

@davidebbo Thank you so much :-)

itshemant09 commented Aug 30, 2018

@davidebbo Thank you so much :-)

@ESSAdeveloper

This comment has been minimized.

Show comment
Hide comment
@ESSAdeveloper

ESSAdeveloper Aug 31, 2018

Hi David,

On Azure Will this 4.7.2 be available as a choice among the other versions or will it be the only version available?

thanks
ESSADev

ESSAdeveloper commented Aug 31, 2018

Hi David,

On Azure Will this 4.7.2 be available as a choice among the other versions or will it be the only version available?

thanks
ESSADev

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Aug 31, 2018

Contributor

@ESSAdeveloper see answer to same question above.

Contributor

davidebbo commented Aug 31, 2018

@ESSAdeveloper see answer to same question above.

@pYThMik

This comment has been minimized.

Show comment
Hide comment
@pYThMik

pYThMik Sep 3, 2018

Hello, do you know / can you precise the actual date that 4.7.2 will be available on app service ?
Thanks

pYThMik commented Sep 3, 2018

Hello, do you know / can you precise the actual date that 4.7.2 will be available on app service ?
Thanks

@Sethu2488

This comment has been minimized.

Show comment
Hide comment
@Sethu2488

Sethu2488 Sep 3, 2018

Hello,
I would like to know if the .Net version 4.7.2 will be automatically upgraded or do we have an option to upgrade as and when required.

If there are issues in 4.7.2 is it possible to roll back to an app service using the existing .net version?

Appreciate your response on the above ask.

Sethu2488 commented Sep 3, 2018

Hello,
I would like to know if the .Net version 4.7.2 will be automatically upgraded or do we have an option to upgrade as and when required.

If there are issues in 4.7.2 is it possible to roll back to an app service using the existing .net version?

Appreciate your response on the above ask.

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Sep 3, 2018

Contributor

@pYThMik @Sethu2488 I have added a 'Frequently asked questions' section to the announcement to cover those points

Contributor

davidebbo commented Sep 3, 2018

@pYThMik @Sethu2488 I have added a 'Frequently asked questions' section to the announcement to cover those points

@leonmeijer

This comment has been minimized.

Show comment
Hide comment
@leonmeijer

leonmeijer Sep 6, 2018

How to tell if we have been upgraded? Since the Azure outage in South Central US, our app service doesn't behave as before. We use Azure AD authentication and we now suddenly have a different claims set. If we deploy the same app to West Europe, all works fine. Thinking Microsoft might have redeployed us with a new template with 4.7.2 on it...?

leonmeijer commented Sep 6, 2018

How to tell if we have been upgraded? Since the Azure outage in South Central US, our app service doesn't behave as before. We use Azure AD authentication and we now suddenly have a different claims set. If we deploy the same app to West Europe, all works fine. Thinking Microsoft might have redeployed us with a new template with 4.7.2 on it...?

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Sep 6, 2018

Contributor

The upgrade to 4.7.2 has not yet started anywhere, so any issue you are having is definitely not related to it.

Contributor

davidebbo commented Sep 6, 2018

The upgrade to 4.7.2 has not yet started anywhere, so any issue you are having is definitely not related to it.

@mmulhearn

This comment has been minimized.

Show comment
Hide comment
@mmulhearn

mmulhearn Sep 10, 2018

Once the rollout begins, how can we determine if it has been installed on our apps?

mmulhearn commented Sep 10, 2018

Once the rollout begins, how can we determine if it has been installed on our apps?

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Sep 10, 2018

Contributor

You can use the following, based on this page. From Kudu console, run:

reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release
  • 0x709fe -> .NET 4.7.1
  • 0x70bf6 -> .NET 4.7.2

It has not yet started, and probably will not until Friday 14th at the earliest.

Contributor

davidebbo commented Sep 10, 2018

You can use the following, based on this page. From Kudu console, run:

reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release
  • 0x709fe -> .NET 4.7.1
  • 0x70bf6 -> .NET 4.7.2

It has not yet started, and probably will not until Friday 14th at the earliest.

@dcc635

This comment has been minimized.

Show comment
Hide comment
@dcc635

dcc635 Sep 14, 2018

To clarify, Microsoft is forcing all machines to be upgraded to 4.7.2, so we need to test it early to work out any potential bugs. But until they force the upgrade we can't actually test on production since 4.7.2 is not available in the Azure VMs yet?

Also, does "upgraded" mean all apps will be changed to target 4.7.2? Or just that the VMs will have 4.7.2 available for targeting?

dcc635 commented Sep 14, 2018

To clarify, Microsoft is forcing all machines to be upgraded to 4.7.2, so we need to test it early to work out any potential bugs. But until they force the upgrade we can't actually test on production since 4.7.2 is not available in the Azure VMs yet?

Also, does "upgraded" mean all apps will be changed to target 4.7.2? Or just that the VMs will have 4.7.2 available for targeting?

@mmulhearn

This comment has been minimized.

Show comment
Hide comment
@mmulhearn

mmulhearn Sep 14, 2018

@dcc635 What we did was spun up a VM, manually installed 4.7.2, set up our site in IIS and tested that way. There were a few bugs that were attributed to this quick set up, but we got the app tested to ease people's minds.

mmulhearn commented Sep 14, 2018

@dcc635 What we did was spun up a VM, manually installed 4.7.2, set up our site in IIS and tested that way. There were a few bugs that were attributed to this quick set up, but we got the app tested to ease people's minds.

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Sep 14, 2018

Contributor

Update: we will not start this deployment until early October (after Ignite conference).

Contributor

davidebbo commented Sep 14, 2018

Update: we will not start this deployment until early October (after Ignite conference).

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Sep 14, 2018

Contributor

@dc995 testing means running your unmodified app on a VM with 4.7.2. There is no need to retarget it unless you specifically want to use some of the new features.

Contributor

davidebbo commented Sep 14, 2018

@dc995 testing means running your unmodified app on a VM with 4.7.2. There is no need to retarget it unless you specifically want to use some of the new features.

@pYThMik

This comment has been minimized.

Show comment
Hide comment
@pYThMik

pYThMik Sep 14, 2018

Update: we will not start this deployment until early October (after Ignite conference).

Too bad. I'm waiting for that update.

pYThMik commented Sep 14, 2018

Update: we will not start this deployment until early October (after Ignite conference).

Too bad. I'm waiting for that update.

@tjrobinson

This comment has been minimized.

Show comment
Hide comment
@tjrobinson

tjrobinson Sep 14, 2018

Thanks for the update @davidebbo

We are consuming .NET Standard 1.5+ from .NET Framework which is "broken" prior to .NET 4.7.2. See: https://twitter.com/terrajobst/status/1031999730320986112 and dotnet/docs#7305 among others. So we're very keen for the upgrade.

Why the wait until after Ignite? Is something being announced perhaps? Or is it just lack of resources until then?

A little off-topic, but do you know if .NET 4.7.2 is coming to Cloud Services anytime soon?

tjrobinson commented Sep 14, 2018

Thanks for the update @davidebbo

We are consuming .NET Standard 1.5+ from .NET Framework which is "broken" prior to .NET 4.7.2. See: https://twitter.com/terrajobst/status/1031999730320986112 and dotnet/docs#7305 among others. So we're very keen for the upgrade.

Why the wait until after Ignite? Is something being announced perhaps? Or is it just lack of resources until then?

A little off-topic, but do you know if .NET 4.7.2 is coming to Cloud Services anytime soon?

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Sep 14, 2018

Contributor

Why the wait until after Ignite? Is something being announced perhaps? Or is it just lack of resources until then?

We've had delays deploying the previous App Service monthly update (not containing 4.7.2). And now we wanted to limit the churn just before the conference, so we decided to move it to after. So it is somewhat related to Ignite, but not tied to any specific announcement.

A little off-topic, but do you know if .NET 4.7.2 is coming to Cloud Services anytime soon?

Sorry, not my area so I really do not know. I suggest asking on the forum for that service.

Contributor

davidebbo commented Sep 14, 2018

Why the wait until after Ignite? Is something being announced perhaps? Or is it just lack of resources until then?

We've had delays deploying the previous App Service monthly update (not containing 4.7.2). And now we wanted to limit the churn just before the conference, so we decided to move it to after. So it is somewhat related to Ignite, but not tied to any specific announcement.

A little off-topic, but do you know if .NET 4.7.2 is coming to Cloud Services anytime soon?

Sorry, not my area so I really do not know. I suggest asking on the forum for that service.

@HowardHoffman

This comment has been minimized.

Show comment
Hide comment
@HowardHoffman

HowardHoffman Sep 17, 2018

Request for clarification: Will a WebJob built with .NET 4.7.2 start successfully in the AzureAppService prior to October? We attempted to test in Azure in a non-production AppService and our (continuous) WebJob stops and sits at 'Pending Restart' status. Backing the change out and switching to 4.7.1 resolved the issue. This expected?

HowardHoffman commented Sep 17, 2018

Request for clarification: Will a WebJob built with .NET 4.7.2 start successfully in the AzureAppService prior to October? We attempted to test in Azure in a non-production AppService and our (continuous) WebJob stops and sits at 'Pending Restart' status. Backing the change out and switching to 4.7.1 resolved the issue. This expected?

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Sep 17, 2018

Contributor

@HowardHoffman This is more of a .NET question than an App Service or WebJobs question. If you run an app targeting 4.7.2 on a VM that has 4.7.1, I would not expect it to run.

Contributor

davidebbo commented Sep 17, 2018

@HowardHoffman This is more of a .NET question than an App Service or WebJobs question. If you run an app targeting 4.7.2 on a VM that has 4.7.1, I would not expect it to run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment