After I created the blazor application in Visual studio . When i trying to run or build the application am getting this error.
I used dotnet restore and dotnet build .
This was the fix for me https://github.com/dotnet/aspnetcore/issues/20857
If you check the build ouput window, you might see a more useful error like:
This showed that I needed to install the lastest .NET runtime from https://dotnet.microsoft.com/download/dotnet-core/thank-you/runtime-aspnetcore-3.1.5-windows-hosting-bundle-installer
For me, installing 2.1 SDK did the trick. Here is the link to it: https://dotnet.microsoft.com/download/dotnet/2.1
I updated Visual Studio to 2019 v16.9.2 and that fixed it for me.
I also read another post where repairing the VS installation fixed the problem.
My problem started mysteriously after everything had been working for some time, so I don't think it was an issue with the version. I think just running the upgrade repaired the installation.
Related
I’m having difficulty getting the sample code for tws api running. I’ve successfully run it on a borrowed laptop but the same version fails on my own windows 10 laptop. When running on Release mode in Win32, I get the popups
The code execution cannot proceed because biddll.dll was not found. Reinstalling the program may fix this problem. and The procedure entry point ?cancelOrder#EClient##QAEXJ#Z could not be located in the >dynamic link library C:\Eclipse-workspace\TWS >API\samples\Cpp\TestCppClient\ReleaseTestCppClient.exe.
I’ve read through several questions similar to this. I’ve tried installing the Visual C++ Redistributable for Visual Studio 2022 for both x86 and x64 from here: https://learn.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170. I’ve tried loading biddll.dll from another folder but it gives the message “Module was built without symbols.”. I’ve run “sfc /scannow” for broken files. The issue persists. biddll.dll still seems to not be anywhere in the system files or the API files. The only version is the one I copied from another version of the project.
Thanks for your suggestions. I uninstalled TWS API and reinstalled it. I made sure to build for Release. It sounds like there was a mismatch between some debug libraries and it started pulling them instead. There may have been some unexpected behavior from installing several versions while troubleshooting as well.
I have a 32bit Application to Install on Win10 (x64 OS). All my Oracle functionality works from within the debugger. Oracle.ManagedAccess driver is correctly registered in the VS Projects and the application works as expected from within the debugger. However, when I build my WiX-Based install pack and run the installed application I get the following error:
What am I missing here? In the previous VS2013 incarnation of the code as recently as last month using the ODP.NET driver 'Oracle.DataAcess', the application worked fine when installed. I'm at a loss as to where else to take this. Any assistance most welcome.
Based on input from Stein Asmul, I jave resolved the problem. Solution simply involved including the Oracle.ManagedDataAccess.ddl in the product.wxs depositing the file in the application folder solved the problem.
I've been developing my Windows Store App for over a month, and all of a sudden I get this error when I try to run it in Visual Studio 2017 on my developer machine:
Visual Studio Errors
(DEP0600 Deployment Failed. Failed to deploy through new deployment pipeline)
(DEP8000 Unexpected deployment failure: AggregateException : One or more errors occurred)
This error only occurs at my current project, not at a standard template for example.
I already cleaned and rebuild my solution but still no success.
At the moment I run
Target Version : Windows 10 Anniversary Edition(10.0; Build 14393)
and
Min Version : Windows 10(10.0; Build 10586).
For me the problem was that my app was already running. I set it as the startup app and after that I couldn't redeploy the newer version. Stopping the app solved the problem.
DEP8000 just means that an agregated thread encountered an error and is thrown to the parent thread.
The real issue here is DEP0600.
I encountered a solution on MSDN.
Basicaly it can occur if any of your filenames has accented characters (á, ô. õ, é) ect.
Rename all your files to remove these and you're good to go.
You need to change the Universal Window Target Version as Windows 10 Fall Creators Update(10.0;Build 16299).
If you can not find this version option,you need to install the WDK for 16299, this is the download link.Please try it,and feel free to let me know if there is any problem.
I encountered the same problems when working with Deploying UWP app to HoloLens.
Here are few steps that can help:
Clean & Rebuild solution
Deleting .vs folder can help
Else you can just rename the package name under project settings.
I am using Visual Studio Community Edition 2017 and trying to create a UWP application.
I get the following error
Your project is not referencing the "UAP,Version=v10.0.10240" framework. Add a reference to "UAP,Version=v10.0.10240" in the "frameworks" section of your project.json, and then re-run NuGet restore.
I had the same issue on my build machine. What's weird is everything runs fine on my local machine.
I managed to fix this by going into the project properties for my UWP app, and changing the Target version to match the Min version.
The reason I believe this issue is happening is because when targeting a higher framework, on a Windows Server machine (the build agent) it doesn't restore all of the packages between your min and target version. It seems to build fine against the version you target.
By the way Ken, following the instructions given by the error don't fix the issue. Try not to be so rude. I came to this page looking for the same issue, and you are no help at all.
I have the same issue, after I remove my bin and obj folder, I can build mine and see the errors gone.
I recently ran across this same issue when updating the target framework. The issue turned out to be the Nuget Restore task in my VSTS Build definition needed to be updated to the latest version (2.*). Once I did that, the builds worked as expected.
I agree with Jeff. Ken Not sure if you should be giving any answers with this kind of attitude.
The error message is misleading there is not project.json at least you cannot see it in the Visual Studio explorer.
I had the same issue and have min and target version set to the same number but it would not build.
The fix was to make sure in Nuget package manager setting to tick checkbox 'Allow Nuget to download missing packages' and the one below it as well and rebuild the project.
This is a pretty weird mistake, but what worked for me :
1st Solution:
1 - Change your project target to "10.0.10586" (or up)
2 - Make a clean / nuget restore / rebuild
3 - Return the project target to the "10.0.10240"
4 - Make a clean / nuget restore / rebuild
Do not ask me why, but it worked :)
2nd Solution:
If you use a repository with Tortoise, try making a CLEANUP
I had an old Backup folder in my project that contained a project.json. Looks like it might have been from an earlier upgrade. I deleted Backup and got a good build.
This happens in exactly this manner, if projects were generated in the year 2017 in the phase where MS changed to project.json and then decided against it. I tried several solutions (and yeah, Ken White is so wrong!) and the cleanest way was to really build up a new clean project in the lastest and up to date version of Visual Studio (VS2015 did not work sustainable) and just copy over the old project content which is just a few minutes work. This will save you a lot of headaches especially working in a larger team!
I tried the above solutions but nothing worked. I had to backup and remove the UWP project and recreate it from scratch.
I tried a couple of solutions.
Solution 1
Open the solution from Windows explorer and search for project.json files. Open all of them (If you have multiple) and make sure the required framework versions are there. I frequently switch between build 10240 and 17763 and I get this error frequently. (I switch between git branches that target different frameworks of UWP) So instead of adding the exact version I just added only the 10.0 part like this.
"frameworks": {
"uap10.0": {}
},
Now if your project.json files are ok, search for project.lock.json files. If you have one or more of those, delete them.
Now clean your solution
Close VS
Delete all the bin and obj folders.
Reopen the VS and try to run the app.
Solution 2:
Go to project properties
Change the minimum and target version to something else and do a clean build. Then put the actual versions and build again.
After downloading updates it shows a error that can't install updates .
An error occurred while uninstalling
session context was:(profile=epp.package.cpp, phase=org.eclipse.equinox.internal.p2.engine.phases.Uninstall, operand=[R]org.eclipse.rcp.configuration_root.win32.win32.x86_64 1.0.0.v20130521-1847 --> null, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CleanupzipAction).
Backup of file D:\eclipse\eclipse.exe failed.
Can not remove : D:\eclipse\eclipse.exe
I'm running it under win7 and jdk1.7.0_21 64bit .
How fix it ?
Solution extracted from the forum linked in Anonymous answer:
Run eclipse
Rename eclipse exe to eclipse.exe.back
Run updates
Updates executed successfully
To match so guidelines:
Always quote the most relevant part of an important link, in case the target site is unreachable or goes permanently offline.
Refer this post: http://www.eclipse.org/forums/index.php/t/487240/. It helped in solving this problem for me.
Shown below for your convenience :
I had same issue with updating Kepler. W7 with admin.
How to solve:
Run eclipse Rename eclipse exe to eclipse.exe.back
Run updates
Updates executed successfully
Premysl Fiala
Create a new workspace. Eclipse Kepler does cause a problem if we work on the older workspace. Worked for me.