This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 18%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hi,
Can I upgrade an existing .net application to 4.8 and publish it to a Azure Web App location that is not yet upgraded to support .net Framework 4.8 (West Europe).
Is the framework back-compatible if I use only 4.7.2 features or what will happen?
Thank you
Hi @Johan , .NET 4.8 is backwards compatible so you can still leverage your code running 4.7.2. However, .NET 4.8 has not been rolled out to all Azure PaaS services, so you can't publish your 4.8 just yet. You can follow this Github issue to track the deployment progress though.
Hi @Ryan Hill ,
I created a 4.8 asp.net application and published it to azure location "west europe" which isn't upgraded to 4.8.
But the application was still running successfully.
Is 4.8 backward-compatible so it's still managed to run on 4.7.2 even though the application targets 4.8?
One thing you can do is cd "\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework" and dir to see if the 4.8 is there.
It's not advisable for your app to target a higher version than the targeted machine. But in looking at this migration guide, you may not have been impacted.
Hi,
I didn't have 4.8 in that directory but the app was still working. Still, I've downgraded by application to 4.7.2 again and will wait for the 4.8 to be deployed before going back to 4.8 again.
Thanks.