Hosting a web application that uploads and downloads files without graphical interface - asp.net

I am a .NET developer, I created an ASP .NET web application which communicates with windows app clients and xamarin android clients. The web application in fact is a bunch of web services which upload data (images) to the disk of a web server, and manage SQL Server databases. The objective of the entire system is to create budgets for the building company of my brother's, he is a contractor.
I want to host the web application on a shared server, but my web application lacks a web page or user interface, and according to most of the hosting companies in the terms of use they say that files on their servers must be related to the website which one should host.
Are there hosting companies willing to host an application like mine?

You're looking for web application hosting, not website hosting. Azure App Services will do what you're looking for but that might be overkill. This also might be better answered in one of the other stack sites.

Related

Is it possible to only allow selected IP range to access a website in ASP.NET?

I'm trying to lay my hands on MVC currently but I'm a rookie for the moment. I'm tasked to build an intranet web application on ASP.Net MVC5 but I hesitate to do so because it will restrict users in many ways, such as they ought to be in queue sitting on companies PCs and accomplish the required tasks that they are obliged for.
I have read and found out that there is an available option through Web.config file but that is applied if the web application is to be hosted in IIS whereas the web application should be hosted from another server online. Stackoverflow Link
To sum up, I want to enable the website I'm going to create to only be accessible from any device connected to the wireless/cable network of our company whether it is from a PC or from a smartphone/tablet.

Is it possible to deploy a WCF service and a WebSite in the same WEBSITE PORTAL from AZURE?

I' deploying two services, one of them is a website and the another is a WCF Service for desktop applications.
I have one web site called contoso2.azurewebsites.net and that place I place my web site, but also I would like to deploy my WCF service, the question is... I need to create another web site service to deploy in it? Or it can be in the same place?
I think you can. If you have an ASP.NET web application, you can add some .svc files for your WCF service. They will be deployed as part of your web site. Then you can use your website through http://contoso2.azurewebsites.net/ and use your web service through, let's say http://contoso2.azurewebsites.net/api/ProductService.svc
Combining your website and services into one application is possible, but you can also host them in two seperate sites within the same web role.
You basically have to:
Create a cspack with multiple sites
Map the internal IP address of the machine to a DNS of your choice in the hosts file when the role starts
More details and scripts on my blog: http://thomassmets.wordpress.com/2013/01/21/a-web-frontend-with-a-wcf-backend-in-azure/

Why use an Azure Cloud Service Project instead of an ASP.NET project with the Azure SDK?

I'm playing with Azure asp.net development. I use Visual Studio 2010, with Azure SDK and I'm a newbie to Azure cloud.
I created several apps and deployed them to my testing Azure Web Site. Everything works fine - ASP.NET Web Page, ASP.NET MVC3, even simple GridView binding to an Azure SQL database, which I created earlier and that I manage with Microsoft SQL Management Studio, using ADO.NET. It's really simple.
Now, I learned from some tutorials, that I need to use a Windows Azure Cloud Service Project to make sure that my application will work. But it works without this project, too. So what exactly do I need such a project in my solution for?
There are actually three different ways you could have gotten your ASP.NET app over to the cloud, and the confusion comes because you are seeing elements of two of those options.
A Windows Azure Web Site is just a single ASP.NET application running in Microsoft's data centers (versus on premises) so all of the configuration it needs is already part of the project itself (primarily the web.config), some being exposed via the Azure portal. In many ways, this is similar to web hosting providers.
A Windows Azure Cloud Service is a collection of multiple services, which could be web sites/services (Web Roles) or backend code (Worker Roles). The code for your Azure Web Site could also have been deployed exactly as is as a Web Role, but in that case it would be part of a larger application that potentially contains additional Web and Worker Roles. It's the Cloud Service project itself that provides the additional configuration of those web and worker roles (even if you have just a single role in the cloud service). The Cloud Service offering is considered Platform as a Service.
The other option, for completeness, is to create a Virtual Machine image yourself, install your ASP.NET site, and then have Windows Azure host the Virtual Machine. It's at the opposite end of the 'make it simple to deploy' spectrum, but you get a lot of control over what exactly is on the VM that you deploy. This is the Infrastructure as a Service offering from Azure.
I'm going to assume you're developing for Windows Azure Cloud Services (the foundation PaaS solution of Windows Azure). The Cloud Service project defines your application to the Windows Azure Fabric. If you don't already have one, then odds are your are running your application outside of the local Development Emulator. If you are going to deploy your solution to Windows Azure Cloud Services, you will need to create this project for your application so Windows Azure's Fabric (the secret sauce that will manage your application) knows how to manage the application.
And I'm going to assume the opposite to #BrentDaCodeMonkey - that you're developing for Azure Web Sites, and not Cloud Services - in which case you may have confused yourself with the tutorials, as I don't believe a Cloud Services Project is either necessary or advisable.

Does WCF require a separate hosting

I am using WCF with asp.net 4.0 (using Dynamic Data).
I need to tell my Client how many domains does he require to book. So, do i require a separate domain/sub-domain for WCF or just 1 domain for website and WCF would work.
FYI: We might acquire a hosting space at shared hosting servers like GoDaddy.com. I need to calculate the hosting cost of the application.
Thanks
You can host WCF in IIS, or you can host it in a separate program/service. If you're hosting it in IIS, you can create a .svc file and have it live alongside your other ASP.NET pages.
So it's entirely possible to have your WCF service live in the same domain as your ASP.NET app.

How to share a folder in a asp.net web application with a win form client?

In this asp.net web application, users can upload files to the server through a web interface. All the uploaded files are save in a server side folder. If I want to create a new win form desktop client (actually, its a WPF application) which can be used to upload files to that same server side folder as web interface does, how can I share that server side folder with that win form client? Any alternative suggestions are also welcome.
thanks for all in advance.
Several ways; you could consider creating a web service on that same server, and the wpf app will communicate with this service. Or, if in the same network, it should be able to communicate via a network share, provided the proper permissions are set.
HTH.
Like answered in What is the best way to store files in a (asp.net + wcf) web application:
Use the WCF tier as a common ground and store the images behind that service. As I said it's going to be an extra to pull the byte arrays over.
Store the images in the Web UI tier and have a service (asmx or WCF one) to expose the images to your winforms/WPF client.
Make a share for the winforms/WPF client on the server where the web ui runs, and where the images are. Of course be sure to be respectful to security and possible hacks.

Resources