Is it possible use Visual Studio 2013 Application Insights with my web forms project?
I have added application insight to my project but cannot get performance metrics to Application Insights portal. My project is running top of Azure web sites.
There's now an Azure Websites Extension that supports perf metrics for azure websites:
http://blogs.msdn.com/b/visualstudioalm/archive/2015/01/07/application-insights-and-azure-websites.aspx
If you have an Azure WebSite and would like to enable Application
Insights follow these steps:
1) Onboard your application to Application Insights from Visual Studio
2013 Update 3 or later and deploy to an Azure WebSite.
Note: If your application onboarded to Application Insights already
ensure you are using the .12 SDK (or later).
2) Enable the Application Insights Extension on the Azure WebSite
blade (not the Application Insight blade) for the website that was
enabled for Application Insights with the .12 or later SDKs
3) Now the extension is enabled execute a few requests against your
web App and navigate to your Application Insights resource blade
As far as I know Application Insights will only work with Web Applications.
Here are the project types supported:
A web service or web application.
Web pages that use JavaScript. A
Windows Phone 8 app.
A Windows Store app.
See this page for further information on the types of projects you can monitor: http://msdn.microsoft.com/en-us/library/dn481095.aspx
Ken's answer is right for the types of apps that application insights supports really well. this includes seamless onboarding/getting started and loads of "automatic" data visible without having to write any new lines of code.
From an SDK "core" perspective we can support other types of apps like WPF and desktop apps. Here are the steps required to setup it up manually and the code required to get metrics, events, traces, etc sent to the application insights service. this should just work if your winform app is running on an azure website too.
Application Insights for WPF Application
At the present time, Application Insights is focused just on web-based applications.
ASP.NET Web Forms
ASP.NET MVC
ASP.NET Web API
ASP.NET Core
WCF
JavaScript
and some alternative platforms / languages (PHP, Ruby, Java).
Azure App Service (formerly Web Sites) does not support Performance Counters (CPU percentage, Disc read/write operations, Available Memory etc.).
For clarification: Azure Website Extension just helps you to collect dependencies and some statistics in case your application is running on .NET version < 4.6.
Related
I can't find an example code for publishing ASP.NET Webforms websites to Azure Functions. Months ago I tried to replicate the C# example but I ended up with only being able to use the precompiled batch function type.
I want to publish VB.NET web apps - any framework version, using Web Deploy...
Here are some important concepts you should know about Azure Web App and Azure Function:
Azure Web App:
Azure Web App is a sand box. The only way an Azure web app can be accessed via the internet is through the only two already-exposed HTTP (80) and HTTPS (443) TCP ports.
For Nodejs App deployed to Azure, Azure will create a named pipe for your server to listen, and pass the request from 443 port(as you use https) to the named pipe.
Azure Function:
Azure Functions is a solution for easily running small pieces of code, or "functions," in the cloud. You can write just the code you need for the problem at hand, without worrying about a whole application or the infrastructure to run it. Functions can make development even more productive, and you can use your development language of choice, such as C#, F#, Node.js, Python or PHP. Pay only for the time your code runs and trust Azure to scale as needed. Azure Functions lets you develop serverless applications on Microsoft Azure.
Api apps and Web apps are pretty much the same deal. Logic Apps and Functions are the same in a sense that they allow you to do something as a response to event or on a schedule, but Functions are a way to run code (or existing app) and Logic Apps are more like a workflow constructor, where you take existing actions and chain them (so no coding, or almost no)
Deploy:
Use ftp to deploy your web form to Azure Function. There will be no problems with the deployment, but the webpage will not display.
Note:
Although Azure Function and Azure Web App are very similar in many cases. But if you choose to deploy web form app, you will still find differences. Even if you can deploy your project to Azure Web App, it won’t display any webpages.
I have a service fabric stateless service which I am running inside my cluster within azure
At the moment the service in question only has 1 instance
I would like to be able to access data in the service via web api
How can I do this with .net standard not .net core?
There are a lot of links for creating web apis but they seem to be either Old or they refer to .net core
Some also give instructions for adding via visual studio which now doesn’t appear to be available within visual studio 2017
Paul
ASP.Net Core is only compatible with .Net Framework and .Net Core. Not .Net Standard unfortunately.
ASP.NET Core is a new open-source and cross-platform framework for
building modern cloud based internet connected applications, such as
web apps, IoT apps and mobile backends. ASP.NET Core apps can run on
.NET Core or on the full .NET Framework. It was architected to provide
an optimized development framework for apps that are deployed to the
cloud or run on-premises. It consists of modular components with
minimal overhead, so you retain flexibility while constructing your
solutions. You can develop and run your ASP.NET Core apps
cross-platform on Windows, Mac and Linux. Learn more about ASP.NET
Core.
https://github.com/aspnet/Home
I was reading this article in looking for differences between creating an API using WebAPI and MVC and came across this statement:
In simple load testing on my local machine, I’ve found that Web API
endpoints hosted in console apps are nearly 50% faster than both
ASP.NET controller actions and Web API endpoints hosted within MVC
projects.
As such, I'm interested in how this would take shape in a production environment.
Obviously I'm looking for performance, so I looked into OWIN and self-hosting. However I'm not clear on if this offers the same efficiency as the console app discussed above.
Can someone please explain the proposal of hosting an API console application for consumption in a production environment - i.e. how would you connect a URL to the console app, etc.?
Thanks.
My understanding is self hosted OWIN apps can be run within any kind of app domain e.g console, windows forms, windows service, AWS EC2, Azure Worker Role etc. The application you should run it in is dependent upon the hosting environment you choose, there are lots of options.
Context:
Building new multi-tenant application using Azure SQL, Azure Table Storage, EF, Web API, MVC, Azure Cache, Possibly Worker Roles -- all the usual suspects:
Please see prior question asked/answered a while back (Jun '12): What is the difference between an Azure Web Site and an Azure Web Role
Side Note:
I'm leaning towards Web Role/Worker Role for Web API and Web Site for MVC/CMS frameworks (i.e., DotNetNuke)
I understand Web Sites are out of beta and have closed the gap with the Web Role in some respects.
Question:
I'm looking for an updated answer to the following:
What are the material differences between the new Azure Web Sites and the traditional Azure Web Roles for an ASP.NET MVC and an ASP.NET Web API application? What reason would I choose a "web site" over a "web role" or vice versa?
Nowadays you have the following execution models:
-Web Sites
-Cloud Services (Worker Role / Web Role)
-Mobile Services
-Virtual Machines
What are the differences between Cloud Services and Web Sites.
-Cloud Services:
You could integrate with Team Foundation Services and allow it to publish to Azure. (Continuous Delivery). With Cloud Services (Web Role), you have two environments in Azure, staging and production. You can use Staging to validate, and with one click (swap option), apply the new deployment package to production environment.
-Web Sites:
Web Sites is the right option when you want to create a simple web site. It is also a good choice for creating a low-administration web application, even one that must be quite scalable, or moving an existing IIS web app to the public cloud.
Cloud Services, which was the initial execution model provided by
Windows Azure, is an explicitly PaaS approach. While the line between
PaaS and web hosting is blurry, Cloud Services differs in some
important ways from Web Sites, including the following:
Unlike Web Sites, Cloud Services gives you administrative access to
your application’s VMs. This lets you install arbitrary software that
your application needs, something that’s not possible with Web Sites.
Because Cloud Services offers both web roles and worker roles, it’s a
better choice than Web Sites for multi-tier applications that need
separate VMs for their business logic. Cloud Services provides
separate staging and production environments, making application
updates somewhat smoother than Web Sites. Unlike Web Sites, you can
use networking technologies such as Windows Azure Virtual Network and
Windows Azure Connect to hook on-premises computers to Cloud Services
applications. Cloud Services lets you use Remote Desktop to connect
directly to an application’s VMs, something that’s not possible with
Web Sites.
http://www.windowsazure.com/en-us/manage/windows/fundamentals/compute/
More info:
http://www.windowsazure.com/en-us/manage/services/cloud-services/how-to-create-and-deploy-a-cloud-service/
I am new to Windows Azure and I have a question.
I have:
Web site which deployed to Windows Azure - The web site manage a table (add, edit, delete). I used this guide: Deploying an ASP.NET Web Application to a Windows Azure Web Site and SQL Database
Andorid application & iOS Application (Native Code).
Now, I want the mobile applications to get data (in JSON format) from the web site (and from the DB).
What is the best practice to do that?
I tried to create a Azure (WCF) Service (the project refrenced to the web site project) but I didn't succeded. If this is the way - Is anyone knows a good tutorial to do that?
Is there another option? Maybe from the web site itself?
Thank you very much,
Yuval
If you want to integrate with non-Microsoft technologies I suggest you take a look at the ASP.NET Web API which allows you to build REST services using content negotiation. Content negotiation allows your consumer to specify the format it requires (json, xml, ...).
To host the ASP.NET Web API in a Windows Azure Web Site you should take a look at Carlos' blog, he describes in detail what you need to do to make this work: Creating ASP.NET Web APIs on Azure Web Sites
Have you given ASP.NET Web API a look-see?
http://www.asp.net/web-api