I want to create the Angular application using Visual Studio 2019 Angular template in Asp.net core but without Node.js as External tool installation. I found that NuGet package manager also providing Node.js and NPM Packages for building Angular app.
So I created the asp.net core projected and selected Angular Template and add NuGet Node.js 5.3.0 that too is saying in readme.txt "Node.js itself is deployed by NuGet, so there is no need to install it locally on dev machines or build servers."
But when I tried to run the angular project then build is failing.
If anyone knows the solution with exact steps so please help me on this.
There is one extra step is required after the Nuget Node.js package installed in the project, which is missing in the node.js document.
Step: Add node.js installed path in PATH Environment Variable (One-time activity per dev system)
e.g: set PATH=%PATH%; C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VisualStudio\NodeJs
or node.js install path can be set manually in the PATH Environment Variable
Related
I can run an azure function app with libvips library from localhost for this function app - manipulation for images output correctly. I setup my local environment by saving libvips win64 in a folder in my windows 10 PC, added libvips bin folder to environment PATH and in Visual studio I installed nuget NetVips, NetVips.Native.win-64.
This is the method I run :
var rgbThumbnail = NetVips.Image.ThumbnailBuffer(thisRGBImgBytes, 256);
I'm trying to run the .Net Core 3.1 V3 function app from azure. When I run from cloud I get "Error:Unable to load DLL \ 'libvips-42.dll\ ' or one of its dependencies. The specified module could not be found . (0x8007007E)"
I had expected for the nuget packages in VS to suffice when uploading to the function app in azure. I've looked on the internet how to install libvips in Azure but I can't find any reference. Can someone please help?
thank you
Had similar problems.
Libvips is using more then one dll.
Download from
https://libvips.github.io/libvips/
Add all dll's then remove one by one.
Or directly identify the missing dll.
In Visual Studio, right-click your Azure Functions project, then click on Manage NuGet Packages, and install the following packages:
NetVips (latest version)
NetVips.Native (latest version)
That should solve the issue related to missing DLLs.
I have my Azure Web App configured to deploy from a local git repository - I just push my changes to the Web App git repo and it builds and deploys the site.
I just updated to my ASP .NET Core site to: "version": "1.0.0-preview2-003133", previously it was 003131 which worked no problems.
I now get the response when doing the git push:
remote: GETSDKTOOLINGINFO : error : The project is configured to use .NET Core SDK version 1.0.0-preview2-003133 which is not installed or cannot be found under the path D:\Program Files (x86)\dotnet. These components are required to build and run this project. Download the version of .NET Core SDK specified in global.json or update the SDK version in global.json to the version that is installed.
I would prefer to update the .NET Core version on my Web App than downgrade, but how?
In case you are wonder how I have 3133 already: https://github.com/aspnet/Tooling/issues/801
You basically can not update the dotnet version on Azure. Currently the version of dotnet that is running is 003131. So you still have to use the previous version.
How are you building your release package?
I had this yesterday using a VSTS build process, when using the 'Visual Studio' build task it will fail with this error currently - changing your process to use the "CMD line" build task and "dotnet publish" allows the build to complete successfully.
I have created a package of electron application by using electron-packager and created MSI project using Visual studio setup project.
Problem
While installing the application I am getting the following error:
I just cannot rename the file or change the location as its a part of node modules.
Please help and suggest what should I do.
You need to package your app into an archive by passing the asar option to electron-packager, that will allow you to avoid the path limit issues and speed up your app startup on Windows.
unless you run latest, you should update node and npm, then rebuild the package.
In npm#3 they worked about that specific issue to flatten the dependency storage folders as much as possible.
I'm getting this error when trying to install my node modules for my node server.
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK,
2) install Microsoft Visual Studio 2005 or
3) add the location of the component to the system path if it is installed elsewhere.
[C:\inetpub\wwwroot\PearsonRealty- API\node_modules\bcrypt\build\binding.sln]
I've tried to install the .NET Framework 2.0 SDK, but it just exits out and never runs. I can't install Microsoft Visual Studio since I'm on an AWS EC2 instance and I wouldn't have enough space for it. Any help would be awesome, thanks.
You do need to install either VCExpress (preferrably at least 2015) or you can try the experimental VC Build Tools solution which is a smaller install than full-blown VCExpress. Otherwise, if you have one, you can try building on a local Windows machine first and then uploading the compiled addon directory to AWS.
I created Starter Azure Node.js Express Application in my local git repository connected to Visual Studio Online and want to use continuous integration technique in order to deploy it to Azure Websites. In my build definition I selected setup_web.cmd located in bin folder as pre-build script path to install node_modules automatically, but msbuild gives an error. I cannot install node_modules to Azure Websites. How can I fix this problem?
Build definition:
MsBuild Error:
There is no requirement to run the setup_Web.cmd as I believe that Node.js modules on Azure Websites are enabled via IISNODE. All you need to do is write the code for the server.js. More details on this at http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-develop-deploy-mac/