Visual Studio Tips

How to Connect to a Local git repo in Visual Studio?

Posted by matteskolin on

I don’t see my local gir repositoy in the local git repositories list inside Visual Studio, how can I add my local git repo and open it in Visual Studio?

I have a repository called “TinyEditor” located on my local computer at c:\temp\TinyEditor

Clicking on the “Add” button, and typing in any path will cause Visual Studio to search for all repos under that path. I type in “C:\temp”, and the repository inside of “C:\temp\TinyEditor is added to my local VS repos.

Result of clicking add below. The repository has been added.


Visual Studio Tips

Getting Started with Application Insights

Posted by matteskolin on

Here is a microsoft link to show excatly how to enable Application Insights in Visual Studio..

https://docs.microsoft.com/en-us/azure/azure-monitor/app/asp-net

Configuring Application Insights even for a local application appears to require an Azure account.

Once configured, telemetry data is immediately sent to Microsoft from where the application is running, i.e starting a debug session in visual studio will start collecting telemetry.

You can view the insight data inside of Visual Studio , by navigating to more windows -> Application Insights Search

View.ApplicationsInsightsSearch is the Visual Studio command here for anyone wishing to avoid the navigation fatigue and headache of having to navigate all the way through Other Windows; I have mapped Application Insights to Cntrl + 0 for my environment.

The Visual Studio Insights search allows you to view Insights from a single debug session, or to pull all the insight data from an Azure Resource.

There are several different filters available on the left “Refine By” column. I was confused at first clicking the filter checkboxes as nothing would seem to happen, and all my data was still showing. It turns out you must click the update button circled in blue above to apply all filters and refresh the main view.

So far I only have Server Response Time metric, and Requests in my insights.

This system looks like it could be useful to identify trouble spots in the application where users are having issues, but not issues serious enough to become bug reports.

Also without this telemetry, I have not seen in the default site templates anything that tracks requests at this level of detail. When working with a larger application it would be help to know what parts of the application are hit the most, and which parts are rarely or never used.

This can help teams know what bugs to focus on and where the site may need to be optimized for speed as well.