When i try create new blank application in nanoframework, i get package installation error.
error message
It seems some problem in nanoframework visual studio extension, my version is NET nanoFramework VS2019 Extension v2019.5.0.8.vsix, but i also tried another versions with same problem.
I have visual studio 2019 community edition and i have installed almost all components.
When i press ok, project is loaded, but is not possible compile it, because there are missing all assemblies. When i try add assembly, theres nothing to add and add nuget packages from nanoframework store leads to error.
when i try this:
pm> Install-Package nanoFramework.CoreLibrary.NoReflection -Version
1.10.1-preview.9
I get this error:
NU1202: Package nanoFramework.CoreLibrary.NoReflection
1.10.1-preview.9 is not compatible with netnanoframework10 (.NETna noFramework,Version=v1.0). Package
nanoFramework.CoreLibrary.NoReflection 1.10.1-preview.9 supports: net
(.NETFramework,Version=v0.0)
similiar when i try another package versions.
So the extensions is installed incorectly, but i cant find why. i tried it more times. uninstall and install again. from extenstion store, and from disc. nothing successfull.
The webserver NuGet released today fixes the issues with the version mismatches.
The issue with VS2019 16.9 remains. Reported to VS Developer Community here. Please up vote to help increase priority.
What is the Community version you're using?
After a little test, there seems to be an issue with the latest release of VS2019. A work around would be to:
Use V16.8.X
or
use an already created solution that you can edit.
or
add the required nuget to the project once it has been loaded (after the error):
Update: now fixed! it was due to a change to fix nuget, but caused an unintended consequence with nanoFramework.
Related
I'm attempting to install DotVVM in Visual Studio 2019. Right now I can find it when I 'manage extensions' and it downloads and installs without error. However when I restart Visual Studio post installation I get an error stating 'The DotVVM package did not load correctly' and points me to an xml output file. The contents of said file shows:
SetSite failed for package [DotvvmPackage]
Source: System.ComponentModel.Composition
Description: The composition produced multiple composition errors, with 3 root causes. The root causes are provided below. Review the CompositionException.Errors property for more detailed information
No exports were found that match the constraint: ContractName DotVVM.Integration.VisualStudio.Dialogs.DialogFactory RequiredTypeIdentity DotVVM.Integration.VisualStudio.Dialogs.DialogFactory Resulting in: Cannot set import DotVVM.Integration.VisualStudio.VsPackages.DotvvmPackageDependencies.DialogFactory (ContractName='DotVVM.Integration.VisualStudio.DialogFactory') on part DotVVM.Integration.VisualStudio.VsPackages.DotvvmPackageDependencies.Element: DotVVM.Integration.VisualStudio.VsPackages.DotvvmDependencies.DialogFactory (ContractName='DotVVM.Integration.VisualStudio.Dialogs.DialogFactory') DotVVM.Integration.VisualStudio.VsPackages.DotvvmPackageDependencies
No exports were found that match the constraint:
Pretty much the same error except it's talking about 'DotVVM.Integration.VisualStudio.Common.Licensing.ILoginProvider'
No exports were found that match the constraint:*
Same error except it's talking about 'DotVVM.Integration.VisualStudio.Services.CommandService'
Now I have been trying to find other topics and came across many that said to delete (or rename) the '%appData%'/Local/Microsoft/VisualStudio/16.0/ComponentModelCache' folder which I've tried with no luck. Removed it out of every VisualStudio version folders as well. Restarted Visual Studio of course after. That folder did rebuild itself but I got the same error again.
I've also tried uninstalling and reinstalling it as well. Tired with running Visual Studio as an admin for kicks. Even downloaded the DotVVM.Integration.VisualStudio.2019.RTM.vsix file directly (both 4.0.534 and 4.0.539) and installing it that way with no luck.
I also tried fully uninstalling and reinstalling Visual Studio 2019 all together with no luck. I made sure the entire VisualStudio/16.0 folder was also gone between installs.
I have been able to install other extensions alright just to see.
It seems like I'm missing something or some files when it's trying to install, but I can't figure out what. Any ideas?
Turns out my version of Visual Studio was the issue. My cooperate environment locks me to 16.10.2 which is not the latest version. Visual Studio updates claims I'm up to date but I am not.
The version of DotVVM (4.0.539) doesn't support version 16.10.2 of visual studio, hence the error. I did find an older version of DotVVM (2.5.254) that does support that version of visual studio and that worked fine.
When i try to run the ASP NET 5 solution, i get below error.
Microsoft Visual Studio Error
The following error occurred attempting to run the DNX design time process (dnx-clr-win-x86.1.0.0-beta8).
The system cannot find the file specified.
The DNX design time process provides intellisense, build, and reference information to Visual Studio and without it your experience will be very limited. Please try closing and reopening Visual Studio to see if that corrects the problem. Alternatively, check that the DNX version is properly installed or try changing to a different installed DNX version using the project property pages.
The project is not finding DNX SDK (if you look at the project properties you may see an empty drop-list next to 'Solution DNX SDK version').
If you are on windows 7, I suspect you may have an old version of powershell installed. You need at least version 3.0.
See this answer on a similar issue:
https://stackoverflow.com/a/31549273/299529
Whenever I install a NuGet package in a TFS source-controlled VS 2015 project, I get a message similar to the following output under "Source Control - Team Foundation":
TF204018: Could not check the file's encoding because the file C:\TFS\Oz.Interfaces\Main\Source\MVRSTamperCodes\MVRSTamperCodes.Web\web.config is in use.
I've been searching fruitlessly to see if there's a way to fix this issue and haven't found anything yet. Does anyone know what is causing this message and/or what steps I can take to fix it? I should note that this doesn't prevent the successful installation of the NuGet package so it appears to just be a warning or informational message.
I've met similar issue with blocking web.config and other files. My solution was:
Uninstall NuGet Package Manager (Tools -> Extensions and Updates)
Install newest version (currently: Nuget 3.2)
If you're using Team Foundation Server, you will need to first check out the entire project, before updating Nuget Packages for the project, if you have this problem.
I created a new Project in Visual Studio 2013, a WebApi & MVC 5 project and updated all nuget packages. It updated to mvc 5.1. Now I cannot Successfully build the project it says
assembly uses System.Web.Http 5.1.0.0 which has a higher version than referenced assembly System.Web.Http 5.0.0.0
Anyone run into this before? Why these kind of problems do occur so often in Visual Studio? Does anybody know how to solve this because I really am trying hard but no luck so far...
Solved
I opened the Package Manager Console in Visual Studio and run the command
PM> Update-package
It magically resolved everything for me. You can find Package Manager Console under
Tools
Nuget Package Manager
Package Manager Console
This command deletes all the old packages under the package folder and updates everything if necessary, you may also run the command on a specific package. Here all the variants of the command http://docs.nuget.org/docs/reference/package-manager-console-powershell-reference#Update-Package
Let me know if you found this useful I'm curious to know if it just happened to me accidentally
A new version of ASP.NET was released. Announcement here : http://blogs.msdn.com/b/webdev/archive/2014/01/20/announcing-the-release-of-asp-net-mvc-5-1-asp-net-web-api-2-1-and-asp-net-web-pages-3-1.aspx
You probably have two projects in your solution, where project A references project B. Both projects reference ASP.NET, but there is a version mismatch.
I had a very similar problem to yours exactly with a reference to System.Web.Http and have documented it here:
Could not load assembly error
When you update a Nuget package it would update dependent packages. But it would not update other packages in your solution that depend on the updated packages. These other packages might not even have a newer version built with the udpated packages.
So the solution is either to udpate all your packages like you did (this might not always work) or add binding redirects to the latest version of your assembly reference to your application config.
I solved this way. As I currently have fwk 4.0.0.0 and don't want to install 5.X:
I removed the referenced DLLs
I removed a couple of bindingRedirects at packages.config,
Then I rebuilded that solution, that throws me errors
Then I added the reference again
And voilà, the solution is running with the fwk that I have.
I've just downloaded the ASP.MVC MSI package, but the installation fails with the "There is a problem with this Windows Installer Package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor." message.
I see that other people too have the same problem (http://forums.asp.net/p/1336453/2699267.aspx). Anybody else?
I'm running VS 2008 Professional edition with SP1 on Vista.
Some additional info: entries like Error in Template (C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplates\VisualBasic\Workflow\1033\StateMachineWorkflowLibrary.zip), file (StateMachineWorkflowLibrary.vstemplate). Unregistered ProjectType (VisualBasic). This can be caused by an incorrect ProjectType or because the project type package is not installed. appear in the event log.
BTW I don't have VisualBasic installed. I'm thinking about reinstalling VisualStudio ... :|
I removed all the bad templates and this didn't resolve the issue for me. I found that removing other Add-Ins I had installed let me install Beta 1. In my case the bad add-in preventing the install was Clone Detective.
I had this exact error message from a completely different MSI package - the DevExpress toolkit - turned out to be caused by one of the "defensive" packages installed on my machine.
Check your anti-virus, anti-spyware, anti-intrusion, firewall, anti-xxx etc etc packages to see if any of them might be stopping scripts from running properly.
Hope this helps.
The installer is trying to add templates to the VB package without checking to see if it exists first (ScottGuuuuuuu!).
If the rest of MVC is installed and working, forget about it. If not, you don't have to reinstall VS. A quick fix is to simply install Visual Basic (e.g, modify your installation rather than reinstall it).
Okey, like Simon said, Clone Detective addin was the troublemaker which prevented the installation of ASP MVC. I deinstalled Clone Detective and now MVC has installed without problems. Thanks guys!