I wanted to have a go at Microsoft.ApplicationInsights telemetry. Documentation claims that TelemetryContext is supposed to be in Microsoft.ApplicationInsights.Contracts namespace, however when I grab Application Insights for Web from nuget (it gets me Microsoft.ApplicationInsights as dependency), it does not seem to have Contracts in it.
Microsoft.ApplicationInsights.Contracts nuget search gives no results.
I must be missing something obvious here.
The documentation on MSDN appears to be out of date.
In 1.1 of the Application Insights SDK (the latest, which I'm assuming you are using), has TelemetryContext in this namespace: Microsoft.ApplicationInsights.DataContracts (note DataContracts not just Contracts). I used Resharper to let it find the TelemetryContext class and it found it in this namespace in the core package (Microsoft.ApplicationInsights).
The SDK release notes do not mention anything specifically about this namespace moving however, https://azure.microsoft.com/en-us/documentation/articles/app-insights-release-notes-dotnet/.
API docs now updated. Sorry for the inconvenience, and thanks for pointing this out.
Related
I have a problem with testing in Rider using XUnit.
Basically, I have a solution with two project - one is the rest-api-app, the second is rest-api-app-test. Both are the exact .net core versions, are in the same solution, but I have no idea where to set the reference from rest-api-app-test project to the rest-api-app. When I was adding testing project to the main solution, I didnt see any option to set reference to the tested project.
With that being said, I can't use 'using rest-api-app' namespace in the test project.
Thanks for any help.
I have managed to fix that; I am almost sure it was some kind of framework bug.
tl;dr
Just try to use classes and methods from desired namespace, InteliSense should suggest to import it, like normally it does.
What I have done (steps):
Restarted few time Rider IDE (I think it was relevant).
Although, I didn't have 'Using rest_api' (.NET CORE didnt recognize it at all, neither InteliSense did any sugestions to fix it), I have tried to use some classes & methods from the 'rest_api' namespace and viola! InteliSense suggested to import rest_api namespace :D
I am still curious why this bug occured, nevertheless, I am happy it has passed.
I'm a little lost on the examples at http://autofac.readthedocs.org/en/latest/configuration/xml.html#configuring-with-microsoft-configuration
After poking around for ages not realising I also had to add the Microsoft.Extensions.Configuration.Json package (and they were only in pre-release), I now get an error on:
var module = new ConfigurationModule(config.Build());
I get a compile error about not being able to instantiate an abstract class.
There's no mention in the docs about having to ref any other package. Any ideas?
Right, so what I had to do was instal the pre release version which solved my issues
I was using the current stable.
As Stephen noted, the documentation covers the prerelease API by default. You can access documentation for the currently supported XML configuration process by toggling the green v:Latest in the bottom left corner of the docs, which will give you the option of switching to the current stable release:
>>
This is similar to a previous question which has been asked (which I incorrectly replied to previously - sorry guys) BizUnit - Pipeline Test Steps missing
The latest version of BizUnit downloaded from nuget no longer contains the above dll. This used to be in previous versions but it seems to have been removed from the nuget package so now I don't have the ability to execute maps from BizUnit as the ExecuteMap method was in the namespace BizUnit.TestSteps.BizTalk. I've looked in the github repository and the code is there but it's not in the solution. I cannot find any information as to why this may have been removed.
Any ideas?
I'm currently developing a Xamarin.Android application in VS2013.
I want to implement Azure Active Directory in my app following this guide. Then I add Microsoft.IdentityModel.Clients.ActiveDirectory nuget package as described.
Then I want to add an AuthenticationResult attribute, but then I got a missing assemble reference error. Even when I explicitely write (or drag and drop) Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationResult.
I looked everywhere for solutions, but none fits my problem. (Upgrade/Downgrade target framework didn't solve the issue)
If anyone has an idea about this, I would be really thankful because I'm getting out of ideas.
Thank you.
Few things to check or try:
Does the Reference to Microsoft.IdentityModel.Clients.ActiveDirectory appear in the References list from your solution?
If it appears, what are the properties, like copy to output, absolute/relative path?
Is it added for all Project configurations (Debug/Release)?
So I found out what was the problem. I had to use a specific version of the package since it's a pre-released version. I had to install 3.0.110281957 exactly then it recognize the reference as I needed.
working with unity and c# and when I try these line
using System.Xml.Linq;
I get this error
The type or namespace name Linq' does not exist in the namespace
System.Xml'. Are you missing an assembly reference?
So I found online, through a lot of searching, that Linq can cause problems, and you need to manually add a reference in MonoDevelop. So I added a reference there (by right clicking References in the solutions pane, clicking Edit References and browsing for System.Xml.Linq)
Still no luck,
Any ideas?
I think this SO post will answer your question...
https://stackoverflow.com/a/875704/1246574
It's pretty much the same issue you're having.
You can't modify the monodevelop (or visual studio) solution or project manually. Because they are generated by Unity. Even if you modify it, Unity can overwrite your changes when it regenerates the solution files.
The reason you can't use some namespaces is the .net/mono version selected in your Unity project settings.
Search for "API Compatibility Level" in this documantation http://docs.unity3d.com/Documentation/Manual/class-PlayerSettings.html
C'mon people, Stop modifying the generated code files. This is 2013!
from this post, I found that Unity doesn't support .NET 3.5 by default (which is required to use Linq). In the settings Xtro talked about, you can only choose .NET 2.0. Instead, you need to drag the desired .dll file into Unity like a texture. Kinda hackish, but it works. Once again, like Xtro said, there is NO REASON to edit the MonoDevelop settings. They have no affect on the final compilation.
EDIT: See Xtro's answer for an alternate solution. He was able to make Linq work by changing the API Compatibility Level to .NET 2.0 (not Subset).
EDIT 2: I just updated from Unity 4.1 to 4.2 today and got an error that Linq was defined twice. by deleting the .dll, I solved the error. Note I'm still using .NET 2.0 Subset. Looks like they added Linq support by default.