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?
Related
I have a vs2019 C# project that references a Nuget project called Diffplex. Even though the first time we downloaded Diffplex it was version 1.7.0.0, we have since upgraded via nuget to 1.7.1.0.
When we make a distribution of our program, we include Diffplex 1.7.1.0 in the file set. Yet when we run our program, it errors with the screenshot provided.
I did find the "answer" to this. Which was to include the ".exe.config" file in the distribution. However I am not satisfied here. When I look at the app.config of my program, there is this binding redirect statement, presumably added by the nuget process:
<dependentAssembly><assemblyIdentity name="DiffPlex" publicKeyToken="1d35e91d1bd7bc0f" culture="neutral" /><bindingRedirect oldVersion="0.0.0.0-1.7.1.0" newVersion="1.7.1.0" /></dependentAssembly>
I am guessing that is why I needed the .exe.config file.
However, I do not understand the error's reference to version 1.7.0.0, like its still looking for that version, like it was linked to that version. There is NO reference to 1.7.0.0 anywhere that I can find within this project. No old copies of DLL's lying around, no mentions in any files within the solution. The only thing I know is that this was the version the first time we downloaded this nuget package.
I think 2 things, that I'm not sure are correct. 1. I should not need any binding redirect statements if I am compiling to the same version I am distributing. 2. There is a bug in either VS or nuget causing the old version to stick around and cause problems.
Can anyone explain this behavior? We are starting to distrust nuget as this is the only time we see this behavior, and I don't want that to be the case.
Thanks,
Dave
My guess is that another assembly you are using is referencing the old dll(1.7.0.0). You can check all of the other project references being used and make sure if they have a reference to the DiffPlex dlls.
Go to the solution explorer and choose DiffPlex under References, right-click and say properties. Check the version and modify the version to 1.7.1.0 if you want to use new version.
Or as the exception message says, it wants 1.7.0.0 but you give it 1.7.1.0 with bindingRedirect element in app.config file . The problem is that the bindingRedirect works. You can remove your binding redirects in app.config and then it will reference the old version.
So, I'm having trouble adding a git project to my net Core solution, and after spending hours trying to figure this out and being uncapable of finding a solution online, I decided to ask here.
I have a forked github repo (link) in which I modified some files to suit my needs, but I simply can't seem to get it to work with my current project.
The problem I'm having is that normally, when I want a package for a .NET project, I usually simply go to nuget and fetch the necessary dependencies. This is usually very simple and straight forward. But now that I have these modified files, I'm unsure on how to proceed.
I have tried adding it as a submodule, but after I built the project, I got an exception saying that the dll could not be found.
Then I've tried adding the dll itself as a reference, but the ImGui.dll depends on a C dll which couldn't be found then (nor added to the project).
Finally, I've tried adding the csproj as a project of my solution, but that didn't work either
Do you know what am I doing wrong here? Am I missing a key piece or is it just something obvious I'm not seeing? It can't be this hard to get it to work
From the look of it, that repository produces a DLL (output type Class Library). So modify it to your liking, and use the sample program build (ImGui.NET.SampleProgram) to test your changes. Once you're happy, build the DLL project (ImGui.NET) and use the resulting DLL as a Reference in your own app.
In Visual Studio:
Solution Explorer>YourApp>References>Right Click>Add Reference...>Locate your DLL
This means you should also keep track of your modifications to the ImGui.NET project itself, since you may/will be required to maintain this in the future.
Hope this gets you started -- update your question with more specific issues once you're underway.
Edit:
Like #CoolBots mentions, I probably misread your question. Seems like the build depends on cimgui.dll, which you can hotlink from the ImGui repo along with your custom DLL. In fact, the demo app is using cimgui.dll, cimgui.dylib and cimgui.so. Regardless of linking method, you want the files to copy into your build folder. I don't believe subfolder /bin is necessary.
You can find all the cimgui dependencies for various operating systems in the ~/ImGui.NET/deps/cimgui folder.
The demo also utilizes NuGet packages Velrid and Velrid.StartupUtilities.
Depending on your own codebase, you may or may not require these NuGet packages along with the aforementioned class library.
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.
I am trying to locate PerRequestLifetimeManager. In MSDN, it says that it is part of the Unity 3 assembly.
I've installed Unity.Mvc4 via Nuget. The package.config says I am using Unity 3.0:
The Microsoft.Practices.Unity.dll says I am using Unity 3.0
I looked inside the DLL using object browser, and the PerRequestLifetimeManager is no where to be found.
Am I missing something here?
If someone will suggest an alternative class, I am planning to use a custom PerRequestLifetimeManager found here (if I am unable to find the class).
EDIT:
I've uninstalled Unity.Mvc4 and directly installed the Unity3.0 in the package console, here is what I got:
PM> Install-Package Unity -version 3.0.1304.1
'Unity 3.0.1304.1' already installed.
Successfully added 'Unity 3.0.1304.1' to RedLions.Presentation.Web.
I still can't find the PerRequestLifetimeManager class, even in the official library.
It seems not good to answer my own question when I just instead did it on my own. I can no longer delete my question.
Anyway, here was my solution.
I went straight to the source code of Unity, I found out that the class does exist in the same namespace but not in the same assembly. PerRequestLifetimeManager is in Microsoft.Practices.Unity.Mvc
I checked MSDN and it did say that its in a different DLL, which I failed to notice. Sorry about that.
It is not part of the Unity package in nuget, but in a different package in Nuget (Unity.Mvc), so here it is: http://www.nuget.org/packages/Unity.Mvc/
I decided to dump Unity.Mvc4 as it is no longer needed, everything is already in the Unity.Mvc. (App_Start/UnityConfig.cs)
you can delete the original DLLS and Uninstall the reinstall.
Run the following from PCM, Package Manager Console:
Install-Package Unity.Mvc
This will give you the DLL Microsoft.Practices.Unity.Mvc where it is.
Im trying to use the libgit2sharp library. My only code is
Repository repository = new Repository(#"C:\Path\To\Repo");
and when i run it i get an error saying Unable to load DLL 'git2': The specified module could not be found. So, I manually went and grabbed the git2.dll from libgit2sharp and moved it into the directory. When running the same program after that I get another error: An attempt was made to load a program with an incorrect format.
While researching this I found this post and the solution that seemed to work for the poster there didnt work for me. That post was also made a year ago and a supposed fix was made for it, Im using the latest branch of libgit2sharp (ive tried older repositories no change)
Any ideas?
The recommended option would be to install the latest LibGit2Sharp NuGet package which will take care of installing everything in the correct location.
However, if you prefer to handle this by hand, the GitHub repository includes both x86 and amd64 version of the git2.dll. Performing a checkout of the master or vNext branch should retrieve them.
Beware that every version of LibGit2Sharp works against a specific version of the libgit2 binary. Each LibGit2Sharp branch contains a libgit2 submodule which points at the libgit2 commit being wrapped.
In order for it to perfectly work, the LibGit2Sharp assembly expects the git2.dll binary to be located into a specific tree structure.
LibGit2Sharp.dll
|__NativeBinaries
|__x86
| |_git2.dll
|
|__amd64
|_git2.dll