I am looking for a hosting service for my Blazor Server web application. It is a simple static website with some extensions to send emails and styling but there is no database or API project currently.
I looked into Godaddy but looks like it does not provide hosting. Also I tried to host it on Netlify but it did not work and there are no tutorials or support fo .Net Core 3.1.
What would be the best place to host a simple blazor app? I am trying to find a cheaper option than Azure
Related
I would to host two ASP.NET Core Applications, a Web API and a Blazor Server App, but I searched in the internet and the answers that I founded only target to a different path inside of one application, that's not my case. I would to use they like a sub-address of the same Azure Web App for example: www.example.com and www.example.com/api where each one will be a different .NET Core application. So I suspect that I'll need to create two Azure App Services and try to communicate they both, but maybe the structured that I wonder won't work in this way, it's that right? How I can do this?
I have the same setup as you; an ASP.NET Core web API, and a Blazor Server Side app.
As you want to use the same domain for both services, you would have to use Azure API Management or some other proxy if you were to route requests to two different Azure App Services.
An easier option is to deploy both services to the same App Service, but as different virtual applications. You publish your Blazor app as normal, but for the Web API you would publish to a new virtual application /api.
To enable this virtual application, navigate to Configuration and then Path mappings in your App Service. Here you already have the default virtual application / pointing to site\wwwroot. You then add another virtual application named /api pointing to site\wwwroot\api:
When adding the virtual application, remember to remove checkbox for Directory (making it a virtual application instead), and optionally enable Preload:
If you publish your app using Azure DevOps Pipeline, it has an option to specify virtual application if another than default should be used.
You can now navigate to your two different URLs and hit each service. Note that when developing your Web API, you should not add api to your controllers routes, as this virtual application does that for you.
I have a application which is hosted in IIS on window server and application URL is "www.hire.com/jobborad". Now i am going to add new feature(sub application) for example "Candidate Hub" so
I am planning to created separate code-base and host that application in Azure as Web App but i want to use the same parent domain of my original application. my sub application's URL will be a "www.hire.com/CandidateHub".
Is there any way that even if my application hosted in differently environment, I will be able to use same domain?If yes then could you please recommend me any tutorial, blog or any thing which help me to resolve my problem.
I search a lot on google but nothing find useful.
Thanks in-advance for help.
Note : Mentioned URLs are just for example. Those are not exist.
this is usually done with the URL Rewrite Module in IIS.
Don't be surprised that the docs are quite old. They are still valid for latest Win Server and IIS.
for external routing you also may need the ARR feature which should be downloaded via the Web Platform Installer.
I have two projects: an ASP.NET web application and a WebAPI application.
Web application uses the WebAPI application via AJAX.
To avoid cross domain problem, I want to the two projects deployed under one domain on Azure.
For example:
http://www.mycompany.com/api/products is a web api.
http://www.mycompany.com/index.html is the home page of the site, which calls the web api via AJAX.
Is it possible?
Yes, you can host multiple applications on the one site.
Go to Configuration / Virtual Applications and Directories:
Simply host your app under
/ site\wwwroot
And host your API under
/api site\wwwroot\api
And make sure your API is copied to the api sub-directory.
Make sure you tick the Application box.
How can I develop web pages with .net on sharepoint online. A way is using visual web parts. Is there any other way?
Thank you
You can use Visual Web Parts, if you use the Sandbox Solutions. You'll need to put code in those which that type of solution is being deprecated. Instead you should be build a SharePoint App. There are three (3) types of hosting, SharePoint hosted, Auto hosted and Provider hosted.
SharePoint hosted will generally allow you to host .js and .html/.aspx files.
Auto hosted and Provider hosted will allow you to write server side code. The different being that Provider hosted will require that you provide a web server, and Auto hosted will put a simple web site and SQL Azure database in Azure for you.
All three of these can create App Web Parts which is generally the same thing as a Visual Web Part, except that they will be using an iframe to include you web app.
I'm fooling around with a WebAPI application I've developed in two solutions: one solution is the WebAPI / serverside solution with db access using SQL server, the other is a durandalJS client application. I have the WebAPI bits hosted in an Azure Website right now, but I'm not sure where to put the client solution.
Should I throw it in its own website and just have it make requests within azure across to the other website? I want to avoid putting them in the same solution because I would eventually like to practice load balancing the front-ends when I have more dough to play with.
Idea of cloud like Azure is pay as you go. If you do not have the volume currently to load-balance, why create two websites and pay for them both regardless of the usage? You can have just one web site and host both the web application and web API. In the future, if you want to separate out API piece and load balance web app, you can do that when you have the volume. For this approach to work, structure the solution like this. The Web API piece will be just an assembly which you can reference in the Web application itself and host it in the same web site as the web application. In future, if you want to separate out, create a new empty ASP.NET Web application and host the Web API referencing your Web API core assembly.