mshtml 8.0 and Microsoft.mshtml 7.0 - mshtml

I'm a little confuse and maybe you can help me.
I've the mshtml.dll (version 8.0) and the Microsoft.mshtml.dll (version 7.0)
If I go to add a reference to my WPF project and try to add the mshtml.dll, it tells me that the reference has to be a valid assembly or com component. And that's right as I know I have to add a reference to Microsoft.mshtml.dll because it's mshtml.dll's wrapper, am I right?
Now, my mshtml.dll version is 8.0 and Microsoft.mshtml is 7.0.
Where can I found the 8.0 version of Microsoft.mshtml.dll?
If I add the 7.0 of the Microsoft.mshtml.dll it'll run the functions of the mshtml 8 dll?
Why are they different?
Thanks a lot for all,
Jayson

Related

Omnisharp error about dotnet version - Unity

at VSCode launch today I'm receiving this error:
Starting OmniSharp server at 27/5/2022, 12:37:25
Target: f:\UnityProjects\MyGame.sln
[ERROR] Error: Found dotnet version 5.0.407. Minimum required version is 6.0.100.
I read that there have been updates in omnisharp but I really don't know how to fix the issue.
I've installed dotnet 6.0 TLS through a new visual studio installation... is there anything else I can do to bring dotnet working with my Unity project?
If you're using C# extension 1.25.0 they announced a change in the extension's details page:
.NET Framework builds of OmniSharp no longer ship with Mono or the
MSBuild tooling (See announcement omnisharp-roslyn#2339). To ensure
that the C# extension remains usable out of the box for .NET SDK
projects, we have changed the default value of omnisharp.useModernNet
to true.
If you still need Unity or .NET Framework support, you can set
omnisharp.useModernNet to false in your VS Code settings and restart
OmniSharp.
Changing that omnisharp.useModernNet setting to false worked for me.
If you use vscode for web development and your installed dotnet SDK version is < 6, this answer might be useful.
After quite some time I spotted an Ominisharp Log warning this.
[ERROR] Error: Found dotnet version 3.1.419. Minimum required version is 6.0.100.
Solution
Install dotnet SDK 6 alongside or by replacing your current version.
I recommend you install it by using the dotnet-install.{sh | ps1} script.
By running the command below it will install the latest version alongside your current one.
sudo ./dotnet-install.sh -c 6.0 --install-dir /usr/share/dotnet
~ ยป dotnet --list-sdks
3.1.419 [/usr/share/dotnet/sdk]
6.0.300 [/usr/share/dotnet/sdk]

Xcode fails to build new projects (12.4) - Could not build Objective-C module 'SwiftUI'

As soon as I create an Xcode project I can't build and have a bunch of errors (Xcode version 12.4)
Could not build Objective-C module 'SwiftUI'
I figured it out! MY Xcode was using the wrong toolchain version even tho I tried to uninstall Xcode and reinstall it.
Make sure you have selected the correct version, in my case since I was running Xcode 12.4, I had to use version 12.4 for toolchains. It's weird that Xcode did not manually change it since I updated.
To updated version:
Xcode > Preferences > Components > Toolchains > and then select your
version

Unity 2019 - How to fix TextMeshPro 2.0 error cs0433

I have just started new project that contains Vuforia SDK. After making some changes I decided to install GitHub extension from Asset Store to make some backup. After that my textMeshPro plugin went crazy, throwing an annoying error which I can't deal with. The error says:
Library\PackageCache\com.unity.textmeshpro#2.0.0\Scripts\Editor\TMP_PackageUtilities.cs(310,17): error CS0433: The type 'Task' exists in both 'System.Threading, Version=1.0.3333.0, Culture=neutral, PublicKeyToken=402899b480e6f383' and 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
Does anybody has an idea how to get rid of it?
My Unity version is 2019.1.0f2
SOLUTION:
Thank you for your answers, I have found solution on other forum.
The way to fix the error in unity 2019.1.0f2
Go to Window->Package Manager
TextMesh Pro (Version 2.0.0 will be installed)
Click on the arrow > on the left to see all the available versions.
4 .Update TextMesh Pro to 1.3.0 (same version as in Unity 2018.3.12f1)
Let the compiler finish and you should see the error clearing from the console
Link to original post: Original post
In Unity 2019.1.5 Looks like TextMeshPro needs at least .net ver 4, I changed .net from 3.5 to 4.6 by going: File > Build Settings > Player Settings > Player > Scripting Runtime Version (which also has a warning on 3.5), selecting 4.6, after reload, textMesh error gone ... moving onto all the other errors in my project!

Framework issue - Module file was created by an older version of the compiler

I'm using
newest OpenXSDKframework (debug)
included in embedded Binaries
Build Settings: Embedded Content Contains Swift Code YES
Other linker -Objc
XCode 7.31
swift
when import OpenXSDKCore
this error is showing
.../ViewController/OpenXBannerViewController.swift:11:8: Module file
was created by an older version of the compiler;
rebuild 'OpenXSDKCore' and try again:
.../OpenXSDKCore.framework/Modules/OpenXSDKCore.swiftmodule/i386.swiftmodule
is this related to the Framework producing Company ?
what should i do - to fix that error?
thanks
That error will occur if the compiled framework (binary) was compiled using earlier version of compiler and in the most of the iOS cases it means that the binary was compiled using some earlier versions of Xcode.
Most probably, your OpenXSDKCore was not built using Xcode 7.3 that you use. The best course of action would be downloading the framework source code and compiling it by yourself.
If you don't have that option you can only wait or downgrade to earlier Xcode version.

How to specify compatibility version for dylib in iPhone projects?

I recently added a static library (mobclix) to my iPhone project which required me to set the Base SDK to 3.0. This library is claimed to be compatible with 2.2 and so far it looks like it's true. I set the project's Deployment Target to 2.2. No problems there.
Now, I am also using libxml2 in this same project. Apparently, the libxml2.2.dylib in OS 3.0 is newer than in OS 2.X (version 10 and 9 respectively). However, my code that uses libxml2, was already compatible with the libxml2 version included with OS 2.X. Since I needed to set the Base SDK to 3.0, the "compatibility version" / minimum version requirement / dependency is automatically set to the newer version of libxml2. When I try to run the app in OS 2, I get this runtime error (obviously):
Dyld Error Message:
Library not loaded: /usr/lib/libxml2.2.dylib
Referenced from: /Users/Martijn/Library/Application Support/iPhone Simulator/User/Applications/4D5456DE-F297-4DF4-ACA6-DA8BBBBBA914/Luisterpaal.app/Luisterpaal
Reason: Incompatible library version: Luisterpaal requires version 10.0.0 or later, but libxml2.2.dylib provides version 9.0.0
Is it possible to override the version requirement somewhere?
Or other ideas to solve this issue?
The compatibility version is set according to the version embedded in the dylib of the current SDK during build. I have not found a way to change or override this.
However, in the target in Xcode under the "Link with binary with libraries" branch there is an option to link a dylib "weakly". This skips version checking at the time of loading the dylib (runtime). It's your responsibility then to only make calls to existing functions. Making calls to non-existent functions will crash the application.
Apparently there was a change with SDK 3.0 that broke compatibility with libxml. Apple have posted about it here:
http://developer.apple.com/iphone/library/qa/qa2009/qa1659.html