Virtocommerce deploy on domain and hosting service provider - virtocommerce

In Virtocommerce document I can deploy it on Azure or my local PC. Is it possible that I can also deploy it on domain and hosting service provider like godaddy or other domain and hosting service provider?

Yes you can, but in this case your deployment scenario will be a same as deploy VC to dedicated server

Related

Accessing Azure app configuration in a WCF service

We have an on-prem WCF service. Recently we added Azure app config to store some config values. We use certificate based authentication(using service principal) to access Azure App config. The issue is, when we try to connect to the Azure app config from WCF service, we get authentication failed error. We can successfully connect to and access the config values from Azure, using a console app in the same server using the same certificate.
The service account of WCF has all the access to manage the certificate. Why can't we access Azure app config in WCF service? Are we missing any settings?
Any help is appreciated.

Is deploying to a hosting provider required for standalone Blazor webassembly PWA?

I am working on a Blazor(PWA) standalone app. Is deploying to a hosting provider required for standalone Blazor webassembly PWA? Or is it possible to serve the app from a network location for users to download and run it locally in their browser? I looked for documentation but can't find any. Please let me know. Thanks!
You'll need to host the app from an HTTP server that provides secure hosting (HTTPS). For example, you could set up an HTTP server on your local network, or use a hosting provider on the internet.
It cannot be shared from a network drive, or anything like that because it's not considered secure, and thus the service worker won't be registered.

WCF on cloud is not working

I just created a WCF service and deployed in one of the machine's IIS and checked it works fine.
When I deploy the same service on Cloud VM's IIS I am not able to consume that service.
I am getting the error saying that "There is no listener with the endpoint".
Can i deploy normal WCF on cloud or do i need to create WCF cloud service?
Environment(IIS 8.5)
It could be several Things, most probably:
ASP.net not activated on IIS
Also check:
The url you are using
firewall problems
site not started

Deploying WCF Service on Azure : Web Role or Worker Role?

I am evaluating the various options to deploy a web service in Azure. Presently, the web service would be consumed only by a front end UI which will be deployed as a separate web role within the same cloud service that would be hosting the web service. However, the web service would be exposed in its own right at a later stage. Apparently, web services can be hosted from within either Web Role or from a worker role. Could you please throw some light on pros and cons of either approach? Which of these approaches would you recommend for my scnario?
A web role assumes that the application will be hosted in IIS. If your service does not require any of the benefits provided by IIS or its HTTP stack, then hosting it in a worker role may do you perfectly fine and also provide you a lower resource utilization for that service (since there's no "overhead" for the IIS server).

Use a Self-Signed Certificate in production for a WCF service hosted in IIS?

I have a project consisting of a website (ASP.NET WebForms) and a desktop application (WinForms + WPF). Right now I'm designing a WCF Service to be hosted in IIS, that will be consumed by these applications. Service is authenticated by an Active Directory. Unfortunatelly in WCF all security related stuff needs a certificate to work.
On the development machine I know I can use a temporary certificate, but the problem is with production. The client server is accessible only from the intranet, so there is no SSL configured and no certificate (and it's not an option to buy one).
My question is: can I use a IIS Self-Signed Certificate on production? What are the disadventages of this? Until now I have used WCF only for simple AJAX calls, and haven't played with the security stuff and certificates.