I am new to .NET aspx web applications with only about one hour of hands on experience so far to date. I have a .NET web application deployed and running in a test environment, but it has some defects visible through the UI.
My question is, how do I know where that application is hosted on disk, and how do I start and stop it? There are several copies deployed, but I do not know how to find out which one has been spun up (or how) and mapped to the test URL.
Any tips would be more than welcome! Thank you!
Related
I've a dedicated machine with at least 6 diferent asp.net 4.5 applications where the developer deployed compiled versions. This apps are all working fine now, but I haven't access to source code.
Now I want to deploy this apps to Azure, but not to a VM, to an Azure Web App Service. Is it posible?
Thanks in advance!!!
Quite possibly. We can't say for sure without more information.
You'll need to FTP all files from your existing root directory/directories to your new Web App. If it's a vanilla ASP.NET web app and there aren't any dependent issues (such as databases on other servers that you cannot move or poke holes through firewalls), it should work.
There are many considerations. For instance, if the applications have dependencies on specific drive letters, you won't be able to mount those drives.
This is just one example, you can take a look at the restrictions that are imposed on Web Apps: https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox
The best way to know, is to create a new site, deploy the files, and see what breaks.
I have an Asp.Net vNext site that I want to connect to a Silo. The vNext site is already done and in production, but the silo part isn't started yet. I'm just in the planning phase, so now's the time to just scrap the whole idea if it seems crazy. Is this even do-able?
I know that you can create a Virtual Network to connect your web app to your Worker Role, which seems simple enough. But, I'm not sure what my server and client configuration should look like, especially around using/discovering DeploymentIds.
The Orlean's provided AzureClient throws an exception when I try to use it in the vNext site -- something about an Azure-related type not being marked Serializable. In the vNext site, I can get the normal SiloClient to work by manually providing the DeploymentId. In my dev environment, the DeploymentId changes each time I debug, so this obviously isn't going to work.
Does anyone have any advice to point me in the right direction here? Let me know if you need more information, and I'll be glad to provide it you.
Where are you hosting your vNext site ? Is it inside webrole or Azure App?
Orleans Client and Silo can't be run in the same App domain so the simplest way to run it in a separate worker role ( it also allows you to scale silos independently)
I'm a .net developer.
I have a project that I might get into.
The thing is, the servers are WebLogic.
I don't know a lot on this subject so I wanted to know if I can deploy my asp.NET application on that server (or what I have to do for that)
Thanks for any help
I've been looking at application pools lately, specifically with ASP.NET applications in mind and I've been struggling to find any best practices for use of application pools.
Of course alot depends of the size and scale of your destined apps in regards to memory limits etc, but I was more specifically thinking along the following lines...
If developing relatively small .net apps which need to be deployed underneath an existing site, should I as a best practice be creating a new virtual directory and application pool for each app?
Or should I just run them underneath the sites already present app pool?
Secondly are there any limits to the amount of app pools you can run (realistically and again assuming small apps with memory limits auto-handled and not defined) on a standard web server?
With resilliance and optimisation in mind my initial thought is to create a new v dir and app pool per app under the parent site - I just wondered if anyone has any thoughts on best practice or links that may assist?
Cheers
For resilience, create a separate application pool for each application. That way if an event occurs in one application that causes the pool to stop, it is only THAT application affected, and not any others on your server.
This also helps in terms of security - the application pool controls the identity of the running application. You should only give just enough permissions for the application to run on the machine. If one application requires access to a specific folder on the server, that doesn't mean you should be giving the same access to all of your applications.
We have an ASP.NET application running on a webfarm. When we release a new version and copy it to the production servers, occasionally it happens that after a few hours the application reverts to a an earlier code base.
Have anyone else experienced something like this? Would sharing an application pool between two applications running different versions of the code make this happen?
Additional information:
3 x web servers running w2k3/iis6
ASP.NET 3.5
I've had this happen rarely on non-precompiled sites and the solution was to stop IIS and clear out the temporary cache at:
%WINDIR%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files
Is not a long-term solution, but will address the immediate problem. If not already, it is worth considering deploying the site pre-compiled.