I got a asp.net mvc project from my friend. This is her project but i need to work on it. So when i try to start it, there are some errors. Here is that errors;
Could not copy the file "_bin_deployableAssemblies\x86\sqlceme40.dll" because it was not found.
Could not copy the file "_bin_deployableAssemblies\x86\sqlcecompact40.dll" because it was not found.
Could not copy the file "_bin_deployableAssemblies\x86\sqlceer40EN.dll" because it was not found.
Could not copy the file "_bin_deployableAssemblies\x86\sqlceca40.dll" because it was not found.
Could not copy the file "_bin_deployableAssemblies\x86\sqlcese40.dll" because it was not found.
Could not copy the file "_bin_deployableAssemblies\x86\sqlceqp40.dll" because it was not found.
I did some search and found some solutions about updating my nuget packages. I did all updates including EntityFramework.SQLServerCompact. But i have still that errors and have no idea what to do. So can someone could help me?
Thanks in advance.
I ran into the same issue after updating VS to 153.
However since I am not Using SqlServerCompact edition anywhere in my project: I use Entity Framework to SQL Server proper I didn't feel the need to have those references and provider in the web.config.
In the Web Project - I used NUGET to remove all references to SQLServer Compact Edition. Then I Removed the reference to SqlCEProvider in the providers section of the web.config. Recompiled and everything works as expected.
You can try this command:
Update-package -Reinstall
from Console administrator packages (PM)
I solved this error using the following steps (order of some steps matters):
Installed SQL Server CE 4.0. I had to install the x64 version to match my OS, but it included the x86 redistributable files referenced in my project.
Using NuGet, removed EntityFramework.SqlServerCompact from my project
Using NuGet, removed Microsoft.SqlServer.Compact from my project
Using NuGet, installed EntityFramework.SqlServerCompact, which also installed Microsoft.SqlServer.Compact.
I had the same issue and i uninstalled SQLServer Compact Edition and installed again from nuget packages
Related
I tried creating a asp.net core web application with mvc in visual code 2019 and as soon as I open it it showes me a lot of errors like in the picture.
enter image description here
I triend closing and restarting vs, cleaning and rebuilding the solution and restoring nuget packages and it is still not working.
I got similar issue where it was not able to detect the namespaces from .Net library. I uninstalled the SDK and reinstalled it. then it worked !
Check whether .Net SDK is installed properly in your system and do a clean install once again.
Right-click your project name then open the properties windows after that downgrade your Target framework version, build Solution then upgrade your Target framework version which is the latest, and then again Build Solution.
Hope it will resolve your issue.
Im trying to use an ASP.NET web application downloaded from the internet. Im looking for a way restore all the dependencies/packages in a quick way (clean and building the project did not solve it), rather than installing them via nuget one by one. Is there anyway to download and install/resolve (version issues) all the necessary packages at once?
I tried below package manager console commands, but they did not resolve the package conflicts.
Update-Package -Reinstall,
nuget install packages.config and other solutions here - How do I get NuGet to install/update all the packages in the packages.config?
[resolve/install packages]
Can someone help? Maybe Im using wrong commands or doing something wrong.
If you go into Tools > Nuget Package Manager > Manage Nuget Packages for Solution, it will show a yellow bar at the top asking you if you want to restore missing packages. That's a manual way, but there are also some important VS options you want to look at as well, one being an option to restore packages on build.
There is a generic restore option as well from the package manager console, and that should have worked if it was simply a matter of reimporting the missing packages...
Update-Package -reinstall
You can try to delete the folders, than reinstall using these options. However, is there a possibility there is a .NET framework version mismatch with the version of the DLL's? Maybe some of the DLL's need updated?
Remove package folders from Package folder - don't remove package.config. Next, build you application - nuget should automatically restore all packages.
I have installed Umbraco via nuget to empty project. I then ran the project so the installation started.
After installation ran there was lots of generated files so I have included them in project so that I can use source control.
I then ran project again and got the error:
Could not load file or assembly 'Newtonsoft.Json'
There is the dll file for this in bin folder and also a reference.
I think this might be because the "packages" folder created by nuget installation is not included in project. I do not know how to include this.
Does anyone know what I should do?
It turns out problem was in the Newtonsoft.Json file in nuget package. I downloaded latest dll from codeplex and it fixed the 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!