I have a click once application that we have been working on. The hosting server recently changed and a dependency on the Microsoft.ReportViewer.DataVisualization.dll version 11 is now missing from the GAC.
I didn't realize this was there in the first place. I would like to include this dependency in the application file and publishing, but I cannot seem to locate this as a NuGet pacakge.
I am not even sure this assembly is required as I don't see it being referenced anywhere - so my only guess is it is a transitive dependency.
Where is this assembly so I can include it with the application build.
Related
I am working through IS quickstart and having trouble adding IdentityModel to the Client project. I installed the NuGet package through VS.Net and it seemed to be successful but after that, the assembly does not show from the reference list. What am I missing here? Do I need to browse the file system to find the dll? If so, where?
When you add the IdentityServer4 NuGet package, it has a dependency on IdentityModel. So it is already added and that's you don't see it.
You can see its dependencies here
And in Visual Studio if you drill down the Dependencies -> Packages -> IdentityServer4 node
I have a nuget package targeting net462 and I want to use it in netcoreapp3.0.
It works fine if the package has no dependencies (or has netstandard/netcoreapp dependencies), otherwise dependencies are not resolved at all.
Let's say we have package A targeting net462, which depends on package B, which also targeting net462.
I want to use package A in project C, which is netcoreapp3.0. If project C uses package A only, everything works fine. But if it uses something from package B, FileNotFoundException is thrown.
If I understand correctly, I need to add an additional netcoreapp3.0 target to the 'dependencies' and 'files' nodes in both packages A and B. But if I wrong, is there a more appropriate way to make this work?
Anyway what assemblies do I need to add to the 'files' node when targeting netcoreapp3.0?
Same as for net462? Or should I add netcoreapp3.0 to TargetFrameworks in projects A and B and use the resulting ones?
In my practice, I copied the same bits under "net462" node to "netcoreapp3.0" node for both nuget packages.
It works for me.
So I tried to install a package called 'Image Processor' to our Umbraco build which I later found was incompatible. How do I manually remove this package from the build? I've tried removing all mention of 'ImageProcessor' from the Web.config, packages.config etc still no cigar.
This is the error we're getting.
Check in the /bin/ folder for the Image Processor DLL file. If this file is present, I believe that the application is trying to load it. However, this file requires something from Umbraco.Core which isn't there, so it crashes.
If you find the DLL, try deleting it and reloading the application.
Also, I assume you installed this package through Umbraco. In the future I would recommend using NuGet to install packages, as it allows you to add, update and remove packages without running the application (so if you were to get an error like this again, you would be able to easily uninstall the package).
Recently I've been running into an issue and I'm not sure how to best resolve it. We have a very modular architecture on the front end. We write individual angular components, put them in different repo's, and then include them in other apps as they are required, built with webpack & included via NPM.
Recently I've run into issues where multiple versions of a module end up in the compiled /dist folder coming from different places such as:
Directly included in the App I'm working on
2x Indirectly included through a module that I included (see chart for details).
The reason different versions could be used is that at the time CodeA is written ModuleA may be at version 1, then at a later date CodeB is written which also uses ModuleA which is now at version 2.
Then CodeA and CodeB are included in CodeC and now you have a module name collision on ModuleA.
With this setup, I believe if the multiple modules by the same name are loaded, the last one to get loaded is going to be the code behind that module name. Meaning it will be the one to be used by all modules. So there's no guarantee that the most up-to-date version is will be used. This usually results in getting an error that a method on ModuleA by name XXX does not exist.
To make sure I'm running the latest version of the module I have to go in and manually update (npm install) and build with webpack (npm run build) each library and then push them all to Github. Then I have to npm install in my root app. This isn't always an easy thing to do as the individual libraries' code may need updated to use the latest version of the module in question.
I'm looking for a solution to this issue. I'm guessing a structural/organizational change that will help us to not get into this predicament. If you have any solutions/advice/articles I need to check out please share. Thanks!
I'd love to use Pandoc in a utility I'm writing (C# console app) and I found this bindings project on GitHub, libpandoc and by extension, it's .NET bindings project, libpandoc-dotnet.
I wish the author had included the built DLL but I suppose he wanted to leave it open to future Pandoc versions.
I have no Haskell experience whatsoever, I just want the .NET bindings in the end. I'm trying to install the dependencies via cabal but I don't understand the error messages and a cursory search leads me to believe installing base is a no-no, so I'm not sure what to do.
C:\Development\Contrib\libpandoc>cabal install base-4.1.0.0
Resolving dependencies...
cabal: Could not resolve dependencies:
next goal: base (user goal)
rejecting: base-3.0.3.2, 3.0.3.1, 4.6.0.1, 4.6.0.0, 4.5.1.0/installed-7c8...,
4.5.1.0, 4.5.0.0, 4.4.1.0, 4.4.0.0, 4.3.1.0, 4.3.0.0, 4.2.0.2, 4.2.0.1,
4.2.0.0 (global constraint requires ==4.1.0.0)
rejecting: base-4.1.0.0 (only already installed instances can be used)
rejecting: base-4.0.0.0 (global constraint requires ==4.1.0.0)
If a kind soul could even build the damn thing (fork it? upload it somewhere?) I'd love you forever. Alternatively, show me how to build it properly and I can handle it from there I think. Though now that I think about it, not sure I have a C compiler installed.
Update:
OK. So it all comes down to the fact that libpandoc is 3 years old and its dependencies are out of date. I had no luck trying to get all the old Haskell tools to install and work, I probably had no idea what I was doing. I got as far as installing some dependencies but some dependencies weren't versioned so I had to track each version specifically and I eventually gave up.
I then just updated the dependency versions for libpandoc itself and now I've got all the dependencies built and linked.
The only remaining issue is that libpandoc needs to be updated to work against the latest Pandoc release (1.10).