I was trying to compile the windows application for visual studio 2017 and I'm coming across this:
fatal error C1083: Cannot open include file: 'gdiplus.h': No such file or directory
I've tried searching for where to download this file but I can't seem to find it. I contacted vidyo and they redirected me to this link but I don't understand what to do with the file. It compiles and then runs without any real effect.
https://code.msdn.microsoft.com/windowsdesktop/GDI-bb1a3ba3
Anyone have any insights?
Thank you!
I am assuming you are trying out the vidyo.io Windows sample project. This sample project was probably compiled to an older version of Windows SDK, so you can either try it on an older version of Visual Studio, or the better approach would be to retarget the sample project in Visual Studio, so that it would refer to the newer Windows SDK. Here are the steps to follow:
Go to the "Solution Explorer" view.
Right-click the "VidyoConnector15" solution or the "VidyoConnector" project icon.
In the context menu, select "Retarget solution" or "Retarget Projects", respectively.
In the resulting dialog, the preselected option is probably a newer Windows SDK version that is already installed on your computer. Accept that option, and let Visual Studio update the sample project.
Built the app without errors.
Good luck!
Related
Trying to set up my dev env on my mac machine with M1. Downloaded VSCode and all required SDKs.
I am able to run any project >=6.x (because MSFT has native SDK for ARM64), but struggling in running projects that target .NET Core 3.1 for instance.
Here is what I get as an error when I try to build\run:
Architecture: arm64
Framework: 'Microsoft.AspNetCore.App', version '3.1.0' (arm64)
.NET location: /usr/local/share/dotnet/
The following frameworks were found:
6.0.7 at [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Learn about framework resolution:
https://aka.ms/dotnet/app-launch-failed
To install missing framework, download:
https://aka.ms/dotnet-core-applaunch?framework=Microsoft.AspNetCore.App&framework_version=3.1.0&arch=arm64&rid=osx.12-arm64
I have tried to run VSCode using rosseta to emulate Intel without any luck. Looks like omnisharp extension needs to be updated, but not sure what exactly to change.
Appreciate any help!
P.S. Everything works in Visual Studio, but not in vscode.
UPDATE
Adding path (/usr/local/share/dotnet/x64) to x64 in /etc/path makes the
trick, but I don't like this kind of trick, let me know guys if you have an any better solution...
Adding an answser here as well as a comment, as formatting in comments doesn't work...
I needed to edit the file
/etc/paths
to add the line:
/usr/local/share/dotnet/x64
Note that you may not see the /etc folder in Finder on the mac because it's hidden.
To see hidden files/folders in Finder, press Shift-Cmd-1
The above key combination toggles hidden folder/file visibility
I recently installed the preview version of visual studio and created a new .net maui blazor hybrid app.
When debugging the app, a window shows up and everything works just as expected.
However when i go to the bin folder and run the exe that is located there the window does not come up.
In the windows event logs i can see the following:
Exception Info: System.DllNotFoundException: Unable to load DLL 'Microsoft.ui.xaml.dll' or one of its dependencies
And indeed that dll is missing from the bin folder.
What does visual studio do to make this work? How can i just run the exe?
Right now we only support so-called “packaged” apps. Those you need to publish to an MSIX and install in order to run.
We’re working on adding the unpackaged scenario as well, you can track that here: https://github.com/dotnet/maui/issues/3166
While searching for the above issue I noticed a couple of others ones though. According to this and this it might already be possible right now, you might want to try!
I have DevExpress XtraReports v18.1.6 version and PostgreSQL 4 v3.3. Visual studio 2017 v15.3.3 and Windows 7.
Here is scenario: In my project, I have some reports writen in devexpress v17.2. I could not run those reports, because I could not download exactly that version 17.2, I install new 18.1.6. Then in Visual studio main menu "DevExpress" I click on "Project converter to 18.1.." and that action replace my old dlls v17.2 with new 18.1. After that I could run reports (see it in designer).
But problem is with databse connection. I created connection string with "XpoProvider=Postgres".
Every time when I want to get data in report, or rebuild result shema, or manage queries I get error:
Could not load file or assembly 'System.Threading.Tasks.Extensions, Version=4.2.0.0,...
I have that reference, exactly that version. Also I tried with new versions of threading.tasks but unsuccessfully.
My version of Npgsql.dll was 2.2.7, I tried with 3.2.5 (read from some devexpres documentations). Also tried with new 4.0.3.
Did anyone have a similar problem?
we had the same issue when using the DevExpress (18.1) Report Designer with Visual Studio 2017.
I know this might not be an ideal or the best solution but at least it worked for us:
I used ProcMon to determine where it was looking for that specific File, for me it turned out to be C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\hhfnlhs1.kna
I downloaded the NuGet Package for System.Threading.Tasks.Extensions from NuGet (https://www.nuget.org/packages/System.Threading.Tasks.Extensions/)
I unzipped the Package and stored the DLL at that path from step 1
I had to active "loadFromRemoteSources" in my machine-config (see https://learn.microsoft.com/en-us/previous-versions/dotnet/netframework-4.0/dd409252(v=vs.100))
I had to put another DLL from NuGet (https://www.nuget.org/packages/System.Runtime.CompilerServices.Unsafe/4.5.2) into that folder from step 1
That's it - now I can access the DB again.
I'm following the tutorials and samples of the official WSO2 ESB documentation. When I create (or load) a synapse configuration in the WSO2 Developer Studio I'm getting the error as shown below:
Save problems
Save could not be completed.
Reason:
resources\sunErrorHandler.esb_diagram (The system cannot find the path specified)
This error shows up when I want to open anything in the Design view. Even when I'm not trying to save anything.
So far I have tried to add the path specified in the error, but without success. I already found a workaround to be able to save and deploy my ESB configurations. By using "Save as" I'm able to keep the changes I made in the XML files. However the error stills shows up when I open the new version of the file.
Does anyone know a better solution to permanently resolve this error message?
I had this problem as well, running eclipse.exe as administrator fixed it.
Issue remains unresolved for my Eclipse + DevStudio 3.8.0 install on a Windows 10 environment. However since I was experiencing some other issues with the WSO2 ESB I decided to migrate to a Linux (Ubuntu) environment. This seems to work much better, the eclipse does not seem to have this issue on Linux.
Eclipse want to write in C:\Program Files\eclipse\resources. I solve problem by adding full permissions to group users on folder C:\Program Files\eclipse
If this happens in Mac you can provide the required permission to the "/Applications/IntegrationStudio.app/Contents/MacOS/resources" folder.
I have this Metro App project that I just tried building for the Windows Store.
After completing the buildprocess (with no errors) I can't open the appxmanifest xml file in visual studio anymore. If I select "STORE" > "Edit App Manifest" I get the following error message: "Value does not fall within the expected range."
I can't open any manifest file in any project now.
Does anybody know whats happening, do I need to reinstall Visual Studio or whats going on?
I'm pretty desperate, so any suggestions are welcome.
Found the answer here http://forums.asp.net/t/1836720.aspx/ - so i tried deleting the .suo files from the project, and now it seems to work. I have no clue why that would affect newly created/other/checked out projects, weird behavior indeed?
(Since I am both new to SO and to Visual Studio, I don't know if answering my own question is considered bad practice, if it is, please let me know what I should do instead)
It's an XML file, so you could try to open it with a text editor to figure out if there's an invalid value set somewhere. You could always compare to a default Package.appxmanifest from a new project.
Can your fellow coworker open the manifesting file you're having trouble with?
The first thing to check is to make sure you are running Visual Studio as an admin. (Right click, run as administrator)
Try creating a completely new project. Save it without modifications. Build it. See if you can open the manifesting file in that project. If you can't, try a XAML/C# project instead of JS just to see if something is wrong with the specific project type.
And before you try completely reinstalling, you might try resetting your Visual Studio settings. Make sure to take a backup just in case you need to get your environment back to where it was once you find the issue.
http://msdn.microsoft.com/en-us/library/ms247075.aspx