I've added ever Nuget package I can find and have followed a number of tutorials step by step.
I can't find any questions about what package supplies the JsxBundle functionality.
Also added and removed a large combination of React and Microsoft packages to make sure I wasn't missing something.
Looking for the specific nuget package to install for the JsxBundle, Using vs2019
Related
I use Windows Application Packaging Project to generate MSIXBUNDLE for my WPF app.
App installed failed with error message: Windows cannot install package xxxxxx_3.8.3.0_neutral~_hijkl because a different package xxxxxxx_3.8.2.0_neutral~_abcde r with the same name is already installed. Remove package xxxxxx_3.8.2.0_neutral~_abcde before installing. (0x80073cf3)
I think the reason is that I signed the new package (3.8,3) with a new EV code signing certificate. Does WAP tool support option to uninstall previous package? Under the project property tab "Debug" ->"Start option", there is a check box for "Uninstall and then re-install my package. All information about the application state is deleted". But enable it does not seem to do the job.
Thanks,
"Uninstall and then re-install my package. All information about the application state is deleted"
I think this option is useful only for debugging purposes. It sounds like an option to remove a previous copy of the package (that has the same version and product name). So, this does not help with removing older versions.
For MSIX packages, you don't top configure anything specific in the package to trigger the removal of a previous version, as you used to do with an MSI. This is handled automatically by the OS.
But the OS needs to somehow understand which package to remove and I suspect the digital certificate is part of that check. Just manually remove the old version, install the new one, and then build a test version (3.8.4) to confirm if the different certificate was the problem.
I'm losing my mind here trying to install the Microsoft.Toolkit.Uwp NuGet package into a WPF app (need the toast notifications and possibly some more stuff from UWP), but I always get the following error, no matter which version of the toolkit I'm trying to install and no matter which .NET version I target:
Could not install package 'Microsoft.Toolkit.Uwp XXX'. You are trying to install this package into a project that targets '.NETFramework,Version=ZZZ', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
The weird thing is that Microsoft actually sends you to the Toolkit to do the exact thing I'm trying: get toast notifications from a WPF app, as can be seen here:
https://learn.microsoft.com/en-us/windows/uwp/design/shell/tiles-and-notifications/send-local-toast-desktop
Excerpt from Microsoft's website
Tried downloading the NuGet package and install it from the local source, tried downloading the whole GitHub project, but to no avail. What am I doing wrong here, guys? I can't seem to figure it out.
P.S: I can't use UWP directly, because this will be an internal company app which needs to do lots of stuff not supported by UWP.
The documentation tells you to download the Notifications library. The Microsoft.Toolkit.Uwp package is not compatible with WPF but the Microsoft.Toolkit.Uwp.Notifications package is.
In karaf how do you search for missing packages in repos ?? seems like such a feature would be really really handy
For example, try to install activemq-broker following manual using latest karaf release (at the time of writing this question) and you need to add:
spring-legacy repo to install spring
some other stuff that's required by third party libraries and you have no idea about
Should be able to do a "search for package" and get a list of metadata about artifacts available in a repo that contain that package.
Hello I'm trying to use the Visual Studio extension Quick Install Package to install packages via bower and npm. One example is angular-loading-spinner
When I give the command using the interface, I see that the package.json file is updated and or the bower.json file is updated with the package dependency, but I'm still unable to actually reference the packages as instructed in my html using the tags. No actual files are added to the project, so I feel like I'm really missing something here, or simply don't understand what this package installer is actually meant to do. There doesn't seem to be any clear tutorial on this I can find online, or any good information. It just all assumes it works fine. Can anyone please advise? Thanks]1
Mike, I'm glad to know that my answer was the correct. For future users that have the same concern, they need to look at the folder node_modules to find out all the libraries installed.
This was put in the node_modules folder as pointed out by Jonathan Brizio. The issue was that the files were hidden and had to be included in the project.
On reviewing the chocolatey packages available, I came across a few that have two (or sometimes more) packages apparently for the same product. At first glance is not possible to tell the difference.
For example, there is the AutohotKey package, and then there is also an Autohotkey.install package.
What is the difference between both types of packages?
Have a look at the FAQ in the Chocolatey wiki here:
https://docs.chocolatey.org/en-us/faqs#what-is-the-difference-between-packages-no-suffix-as-compared-to.install.portable
Quoting from that article:
tl;dr: Nearly 100% of the time, the package with no suffix (autohotkey in this example) is going to ensure the *.install. The package without the suffix is for both discoverability and for other packages to take a dependency on.
Chocolatey has the concept of virtual packages (coming) and meta packages. Virtual packages are packages that represent other packages when used as a dependency. Metapackages are packages that only exist to provide a grouping of dependencies.
A package with no suffix that is surrounded by packages with suffixes is to provide a virtual package. So in the case of git, git.install, and git.commandline (deprecated for .portable) – git is that virtual package (currently it is really just a metapackage until the virtual packages feature is complete). That means that other packages could depend on it and you could have either git.install or git.portable installed and you would meet the dependency of having git installed. That keeps Chocolatey from trying to install something that already meets the dependency requirement for a package.
Talking specifically about the *.install package suffix – those are for the packages that have a native installer that they have bundled or they download and run.
NOTE: the suffix *.app has been used previously to mean the same as *.install. But the *.app suffix is now deprecated and should not be used for new packages.
The *.portable packages are the packages that will usually result in an executable on your path somewhere but do not get installed onto the system (Add/Remove Programs). Previously the suffixes *.tool and *.commandline have been used to refer to the same type of packages.
NOTE: now *.tool and *.commandline are deprecated and should not be used for new packages.
Want more information? See http://ferventcoder.com/archive/2012/02/25/chocolatey---guidance-on-packaging-apps-with-both-an-install.aspx
Setting up a new environment with choco recently and became curious about this too. Chocolatey seemingly created a dedicated documentation site and moved the FAQs there, updating link to:
https://docs.chocolatey.org/en-us/faqs#what-is-the-difference-between-packages-no-suffix-as-compared-to.install.portable