We currently have two slots in azure app service: staging and production. We just migrated .net core 2.2 to 3.1 and tested it in a separate dev app service. We are about to publish the 3.1 app to staging.
Does anyone know if there are any issues with having one slot running 2.2 and another one 3.1?
Azure web app is a PaaS service, and we cannot modify the content in it. Because of this, it integrates many environments by default, or supports all our common SDK versions by default.
If you are not at ease, or when an exception occurs, you can add an Extension to solve possible future problems.
Test steps:
Create an app service (jasonp2core22) which version is .net core 2.1.
Run dotnet --info.
Create an app service (jasonp2core31) which version is .net core 3.1.
Run dotnet --info
Slot is essentially an app service, so your worries are non-existent, and it can all run normally.
Also run dotnet --info.
Related
I am migrating an application from .NET Framework 4.7.2 (WCF) to .NET Core 3.1 (gRPC), and my current architecture has two processes running on the same port. I wanted to ask if there was a way to run two gRPC processes on the same port in .NET Core 3.1.
It is important to me that these be two individual processes, rather than two services in the same process. Thanks in advance.
I have a .net core 3.1 with razor page webapp solution that consists of multiple .net core projects, some are API. It uses identityserver4 for authentification. It can run on Centos 8 as well as on Windows 10 successfully. However, now i would like to split the front end and backend deployment.
backend to run in linux and front end to run on windows. What is the guideline to split the current webapp ?
I am using NServiceBus as middelware for an asp.net core 3.0 API. I already configured the service in my API using NServiceBus version 7.2 because the documentation for that on the website of particular is amazing. Saddly I have a probleem because i got a licence for an older version of NServiceBus versions until version 7.1.x are valid.
my question is: is there a recomendition for configuring NServiceBus in asp.net core using Versions 7.1.x?
One option is to use an external container and configure the endpoint to use it. Take a look at the sample available in the README of the MSDependencyInjection container.
The same thing can be achieved, with very similar code using one of the supported IoC container: https://docs.particular.net/nservicebus/dependency-injection/#internally-managed-mode-using-a-third-party-container
I'm liking a lot what I see about Service Stack, and want to use it with Azure. I found the following project and it compiles ok, but there is either something not mentioned in the readme documents or the 2.1 vs. 2.0 version of the Azure Emulation services is not compatible (which seems unlikely)
I probably have to setup the store manually, but I don't see any interfaces in the emulator to do that.
https://github.com/letsbootstrap/Razor.ServiceStack-On-Azure
Message=Login failed for user 'RazorServiceStack'.
I have site implemented in ASP.NET ( c# 3.0). Can I host that on Mono ?
If I can, do I need to change something in my code ( except communication with database) ?
Due to the Mono Compatibility page the latest stable version of Mono (version 2.8) has complete support to the ASP.NET 4.0 and ASP.NET MVC 2. There is some useful links to read about porting and establishing your site to Mono:
Mono ASP.NET Section
Mono ASP.NET FAQ
Porting ASP.NET Applications
Walkthrough: Porting Asp.Net MVC Website
Can I host that on Mono ?
You can host your application either on Apache with mod_mono or through FastCGI on web servers like nginx or lighttpd.
do I need to change something in my code
Only if some parts of your application use technologies/libraries which are not supported by mono.