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.
Related
I have recently cloned a new repository which has AzureFunctions but I am unable to run it. The build succeeds and on Run click it opens a window suggesting that it is downloading Azure
I am using VS2017 and .Net core 2.1.
It seems to be working for other team members but not for me.
I keep getting this 'Could not find Azure.WebJobs.Host...' error continuously.
I've tried all the fixes that are there on the internet without any luck.
The Azure Functions and Web job tools dlls seem to be up-to-date as they are not shown in the updates tab.
Updating all the nuget dependencies also did not work.
I tried using VS2017 and .Net core 2.1.
Installed Microsoft.Azure.WebJobs - 3.022 version from Nuget Packages.
Included Namespace
using Microsoft.Azure.WebJobs.Host;
I found that there is no Microsoft.Azure.WebJobs.Host direct assembly to include.
If you install Microsoft.Azure.WebJobs you can directly use Microsoft.Azure.WebJobs.Host namespace.
Check your .csproj , if you have any PackageReference Included with Microsoft.Azure.WebJobs.Host, try to remove and build your Application.
It must include Microsoft.Azure.WebJobs
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
I've created a simple package, only consisting of a couple of binaries in the
tools folder. The package is created with NuGet version 4.4.1.4656.
A local folder has been initialized with nuget init and contains said package. VS2017 Package Manager shows the package as expected, whereas VS2012 does not.
There are no available updates for the Package Manager in VS2012, which is at version 2.8.60318.667.
How do I get the feed to work with VS2012, so I can install the package in one of our older solutions? Is this a compatibilty issue?
Any pointers are welcome!
I have created an Azure Function using the latest build of visual studio 2017 (15.3.1).
This build allows me to do the:
New Project > Azure Function App approach
This produces a .csproj (not a .funproj file) and it's doesn't come bundled with a website or anything. I've tried .Net 4.6 and 4.6.1 as the target framework and neither have worked.
I get the following error in VSTS:
C:\Users\Builder.nuget\packages\microsoft.net.sdk.functions\1.0.2\build\netstandard1.0\Microsoft.NET.Sdk.Functions.Publish.props
(13, 3)
C:\Users\Builder.nuget\packages\microsoft.net.sdk.functions\1.0.2\build\netstandard1.0\Microsoft.NET.Sdk.Functions.Publish.props(13,3):
Error MSB4019: The imported project "C:\Program Files (x86)\Microsoft
Visual
Studio\2017\Enterprise\MSBuild\Sdks\Microsoft.NET.Sdk.Publish\Sdk\Sdk.Props"
was not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.
There is no node in my .csproj file so I am not sure where it is getting that from.
I'm using the latest NuGet option in VSTS, I'm using the Latest VS Version option as well.
The build steps are:
Get Sources
NuGet Restore
Build Solution (MSBuild.exe exited with code '1' every time)
Is there any way to build (and then release) compiled .Net functions in VSTS at the minute?
I was able to solve this by swapping the build agent from the "Default" group to the latest, "Hosted VS 2017" group, and that has compiled fine.
Looks like the machine is missing the latest dotnet cli. I'm not too familiar with VSTS build machines, but you'd need to get that on there somehow https://www.microsoft.com/net/download/core
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.