I have used these tools for some demonstrations recently. The interaction between VSO and Visual Studio works great. However, if you want to interact with Azure then make sure you are using the 2.x version of the SDK.
I issued the specified command:
PM> Install-Package Microsoft.ApplicationInsights.Log4NetAppender -Version 0.10.0-build17704 -Pre
Successfully added 'Microsoft.ApplicationInsights.Log4NetAppender 0.10.0-build17704' to mypjt.Web.
however - when the webproject runs i see output:
log4net:ERROR Could not create Appender [aiAppender] of type [Microsoft.ApplicationInsights.Log4NetAppender.ApplicationInsightsAppender, Microsoft.ApplicationInsights.Log4NetAppender]. Reported error follows.
System.TypeLoadException: Could not load
references look correct so I'm not sure where to troubleshoot next.
I realize this is old, but make sure the references set to copy on output, etc. the message implies that the AI log4net appender class couldn't be found at runtime, so i'm assuming it, or some dependencies, are missing from your output directory at runtime?
We are ramping up support for WinForms, etc through the HockeyApp integration which is now part of the AI tools as well. You can add AI manually to those other types of applications by installing the nuget packages and configuring the ApplicationInsights.config file manually.
So far I have had few problems running my web site with Application Insights locally.
One is stated here with workaround.
But I can't disable this extension, not even after running VS2013 as Admin.
I'm not sure what disabling the extension would do in that case. The extension only adds commands and features to visual studio. You can uninstall the extension from VS if you really need to, but that wouldn't affect the app you already have modified with the tool.
The Developer Analytics tools include:
* the ability to easily add Application Insights to various types of projects (ASP.net, others), where the tools wire up things like instrumentation key so you don't have to do that yourself
* search tool to search your Application Insights data, either live in production, or the data that was sent in a debug session
* 5.2 added support for HockeyApp for UAP and Winforms apps, to upload builds of those to the HockeyApp service
see the full release notes at https://azure.microsoft.com/en-us/documentation/articles/app-insights-release-notes-vsix/
Not in the immediate future. We're now focusing on building up the Azure version of Application Insights. Device apps in that version are a little way down the line yet. http://msdn.microsoft.com/library/dn793604.aspx
I have questions regarding store apps. What's the story in regards to the CPU build selection within VS? I watched a Build session from Channel 9 where x86 was chosen in the demo. Is this just to enable the debug logging or does it mean an app that's currently built and deployed to the store with 'Any CPU' now needs 3 builds and three packages to be uploaded to the store?
The instrumentation being added in the current version is native, so this requires specifying the CPU; this will be fixed in a future update. We are looking to make this fix available in late June or early July. Sorry for the inconvenience.
The newest version of the SDKs, which are supported in the (just released) VS 2012 Update 3 do support Any CPU. However, they also point at the azure preview portal instead of the existing VSO portal, so your data gets routed to a different place.
Unless I'm mistaken, for store apps there's not much benefit in doing this at the moment because the preview portal doesn't support showing telemetry for them at the moment, right? Is there any rough timeline for when this might become available?
Also, I encountered an error whilst adding telemetry to my existing windows store app project - I documented my experience here: http://www.goatly.net/adding-application-insights-to-an-existing-windows-store-project-using-visual-studio-2013-update-3
Getting an error when trying to add to an MVC 5 app.
"Could not add Application Insights to project.
Failed to install package:
Please try again later.