I have created install project.
I used this tutorail
But when I try to build it, I have this error 7076
I try to add custom redistributables
SSCERuntime_x64-ENU.msi
dotnetfx35.exe
I resolved this problem, just check this
Related
Using Visual Studio 2019 I installed AutoMapper version 8.1.0 via NuGet. When I try to add the services.AddAutoMapper() call though in my Startup.cs file I get a compiler error that the method doesn't exist.
I've already tried to do a dotnet clean and dotnet restore from the NuGet console but that didn't help.
It is an old thread, however the solution for this problem is to install Automapper.Extensions.Microsoft.DependencyInjection package along with your automapper package.
I hope it helps.
I am totally new to Apache Cordova tools with VS 2015. I just tried to create basic initial project, added nothing more and trying to build it, but it fails everytime.
For the specific error I get, I performed all the steps mentioned at:
Configuring Apache Cordova with VS2015.
I am not able to get rid of this error and run the most basic project.
Here is my sample code: https://1drv.ms/f/s!ApUTYQW5TdbIgzrPGeUkxWVmmy0Z
I ran into this problem and was able to solve it using the solution here: https://stackoverflow.com/a/31688018/4045156
The solution is for a slightly different problem, but in my case it did resolve it. :)
EDIT: here's the solution from that post:
Close all VS instances
cd %appdata%\"..\Local\Microsoft\Phone Tools"
rename CoreCon folder to something else
Launch VS again.
As mentioned in the official link - configure VS tools for Apache Cordova which you are following,
If you see unexpected errors when trying to build the Blank App template after installing Visual Studio Tools for Apache Cordova, you can try clearing your cache and reinstalling the Cordova CLI pre-processor, vs-tac, on your PC.Typically, this is only necessary if you try to build a Cordova app and see the error Cannot find module [modulename].
For other errors, you may have to look at workarounds link.
According to me, clearing cache should resolve the issue or this issue would have got introduced in latest version of Visual Studio once again.
I also suggest you to look at the following SO posts which should help you out in this issue.
VS dont work with TACO
Error with cordova using VS
Hope this helps. Cheers.
Uncaught Exception:
TypeError: app.setVersion is not a function
at Object.<anonymous>(C:\Program Files(x86)\Microsoft VS Code\resources\atom.asar\browser\lib\init.js:81:9)
at Object.<anonymous>(C:\Program Files(x86)\Microsoft VS Code\resources\atom.asar\browser\lib\init.js:106:4)
at Module._compile(module.js:418:26)
at Object.Module._extension..js(module.js:436:10)
at Module.load(module.js:343:32)
at Function.Module._load(module.js:298:12)
at Function.Module.runMain(module.js:459:10)
at startup (node.js:131:18)
at node.js:879:3
I have tried many version of node.js.
Please help me!!!!
You shouldn't exchange the node.js version VSCode is running with. The installer brings everything you need.
The installation seems to be broken.
Uninstall Visual Studio Code
Delete the folder %USERPROFILE\.vscode% when it exists.
Reinstall VSCode
In case it is still failing then file a bug.
I had a similar issue. I just downloaded and installed a new version and issue was resolved.
I did not delete the program files. Still using previous extensions and settings.
Finally I found the solution.
In some situation(I don't know), vscode will write incorrect environment variable. So I have to fix it mannualy. Then vscode works.
Running into a situation where I deployed an application to production a few months ago and now I need to do some work on it, on an entirely new machine. The first I do is pull source and nuget restore won't restore because it can't find the particular version of the package it was developed under. When I check nuget.org for this package version it is not there. So how do I upgrade my solution to the latest binaries?
Visual Studio 2013 trying to update ServiceStack '4.0.39' to latest, which is '4.0.40' at the time of this post.
Thank you,
Stephen
The best solution I've come up with for this is to manually edit the Packages.config file(s) and set the version number to whatever you want. Restore should then work. It's not a perfect solution but it has dug me out of some holes.
(I know this is an old answer, but it just came up in some Googling)
One issue with the accepted answer (of just updating the version # in packages.config) is that this is just triggering a "package restore"--and will skip any "installation steps" the package might have (things that were done automatically when you first added the package, such as adding assembly references, modifying config files, etc.).
An alternative way would be to edit the packages.config and REMOVE the package in question from there---then start up VS and add the new version. This will trigger the package's usual install routine to do it's thing.
I recommend you to use the NuGet Package Manager Console of Visual Studio:
TOOLS > NuGet Package Manager > Package Manager Console
Command to update a NuGet package to the latest version:
Update-Package ServiceStack
Command to update a NuGet package to a specific version:
Update-Package ServiceStack -version 4.0.40
I'm trying to build a solution but I get this error,
he 'Microsoft.Bcl.Build 1.0.14' package requires NuGet client version '2.8.1' or above, but the current NuGet version is '2.6.40619.9041'.
I've just upgraded NuGet package manager in Tools/"Extensions and Updates" which reports the version as 2.8.50313.31.
I've restarted VS2012, restarted the computer, cleaned the project and rebuilt, but I still can't get Visual Studio to recognise the new version and hence can't compile.
Thanks
Run Console (cmd) as Administrator
Locate your .nuget folder that contains the NuGet.exe file (you may check error message to locate the path)
execute this command NuGet.exe update -self
Took me all day to find that NuGet was bound to the individual project.
I had to use the package manager console and run
Install-Package Microsoft.Bcl.Build -Version 1.0.14
to get it to work manually.
Edit (5/11/2014). The problem is actually that Nuget gets bundled with the solution and it is this that needs upgrading. I did this by finding the directory in the project with the nuget.exe file in it (.nuget for me, YMMV) going to that directory and running nuget update -self. If you go with the original solution, you have to do this manually for each package. HTH.
This worked for me in VS 2017 Enterprise-
Right click your solution and go to "Manage NuGet Packages for Solution..."
In the window that opens up, click the gear icon at the top right corner.
Select "General" and click the "Clear Clear All NuGet Cache(s)" button. This will run for a few seconds depending on the size of your
cache.
Clean and rebuild your solution.