VS Express 2010 KernelBase.dll _com_error DirectX11SDK - c++

yesterday i tried to reinstall VS2010 Express after an reset of my system.
I installed VS2010 Express the Windows SDK 7.1 and the x64 Compilers as well as the DirectX SDK(June 2010).
At first i got an Error that he couldn't find Winmm.lib. I fixed this by adding the windows sdk directory to the Library Directorys.
Now Tutorial00 creates a window but whenever i start Tutorial01 the window appears and the closes and i get this error message:
"First-chance exception at 0x000007fefd239e5d (KernelBase.dll) in Tutorial01.exe: Microsoft C++ exception: _com_error at memory location 0x001feca0.."
I think it's a problem with the DirectX SDK, because Tutorial00 doesn't use any DirectX features.
Any Suggestions how to solve the problem?

Related

c++ mfc project upgrade from vs2015 to vs2019 breaks application

I decided to migrate to visual studio 2019 for my mfc c++ application from visual studio 2015.
I have installed all the required SDKs and chose target platform Windows 10, version 10.0.18362.0 and toolset visual studio 2019 (v142). Previously in visual studio 2015 I had Windows 8.1 and v140.
Everything compiles and I can debug the application, however I get strange behaviour for CSingleLock and CCriticalSection where static CCriticalSection objects are null or invalid causing null reference crashes. Static variables seem to have a mind of their own having random values in child frames. The application will open one child frame, but I cannot open multiple child frames simultaneously as the treecontrol in the main frame is misbehaving and will not change on click, the clicks are registered but the treecontrol is unable to get a handle to the ParentFrame (GetParentFrame) to open a new frame. Nothing untoward shows up in the output windows.
In visual studio 2019 I then changed toolset to v140 (Visual studio 2015) and all works as expected.
Has anyone got anything similar happen to them, is there anything I need to do different in code between the two toolsets or does anyone have any suggestions ?
I realise this post does not have much details as I am just fielding atm, if anyone needs more infro please let me know.

DirectX 11 debugger requires Windows SDK 10 but it's selected in IDE and present in system

While working with directx11 APIs I frequently getting a warning stated below but I can see Windows SDK 10 is present in the system (C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.7.2 Tools) as well as selected that version in VS IDE.
D3D11CreateDevice: Flags (0x2) were specified which require the D3D11 SDK Layers for Windows 10, but they are not present on the system.
These flags must be removed, or the Windows 10 SDK must be installed.
Flags include: D3D11_CREATE_DEVICE_DEBUG
I have to debug directx11 objects. I need to get rid from that warning. Would anyone please help to fix this issue?
FIX: Graphics Tools installed offline following this post and the warning is gone.
But now it throws exception from D3D11CreateDevice() but the flag D3D11_CREATE_DEVICE_DEBUG is added or not it throws following exception. How to fix this exception?
Exception thrown at 0x27A7DD55 (d3d11_3SDKLayers.dll) in xxx.exe: 0xC0000005: Access violation reading location 0x00000000.
I have uninstalled then installed the Graphics Tools again. Then followed the your post then it showed debug layer outputs. I can see DXGI error and warnings now. Thank you.

mscorlib MissingManifestRessource exception when using WebRTC.Initialize

Here is my code from my new C# Windows Universal Project:
public MainPage()
{
this.InitializeComponent();
//Initialization of WebRTC worker threads, etc
try
{
WebRTC.Initialize(this.Dispatcher);
}catch(Exception e)
{
}
}
I just installed WebRTC with Nuget with
Install-Package WebRTC -Version 1.62.0.7
and added the line
WebRTC.Initialize(this.Dispatcher);
When I start the app, after some seconds I receive the message, that I shall start the new debugger in new Visual Studio
When I start it, I receive the exception:
If you click on it, it will be bigger.
I am new to Visual Studio 2017 and webRTC. Can you help me with this exception? Is it Visual Studio problem or a WebRTC problem?
Details:
starting with Debug x64
"WebRTC": "1.62.0.7"
Visual Studio 2017 15.4.1
Edit: I updated Visual Studio to 15.5.6 and have still the crash problem without showing me the exception. I asked my question at microsoft feedback.
Edit: If I use English language in Visual Studio, I don't even receive the exception. Visual Studio just stops, wants to start new debugger in new instance of Visual Studio, but can't do it. Only German version shows devenv.exe: Assert failure.
Edit. It is a webRTC problem. Install-Package WebRTC -Version 1.62.0.7installs bad webRTC package.
WebRtc from NuGet is bad and causes the crash.
I received more information in Release Mode
Unhandled exception at 0x749608F2 in VideoConference1.exe: Microsoft
C++ exception: Platform::NullReferenceException ^ at memory location
0x0D92F41C. HRESULT:0x80004003 Ungültiger Zeiger WinRT information:
deviceId is a required parameter.
My WebCam didn't work - https://github.com/ortclib/ortclib-sdk/issues/3

How to make a C++ Application in Visual Studio 2015?

I made a small C++ game in Visual Studio 2015 using the SFML library and it works perfectly fine when I click the '► Local Windows Debugger' button in 'Debug-x86' mode.
My game does not work on anyone else computer because it says the next dll files are missing:
msvcp140.dll
msvcp140d.dll
vcruntime140d.dll
ucrtbased.dll
appcrt140d.dll
desktopcrt140d.dll
I know those files comes from the Visual Studio 2015 Instalation, but for those who do not have VS installed what can I do to fix those problems?
I copied the first 4 dll from my PC C:\Windows\System32 (msvcp140.dll, msvcp140d.dll, vcruntime140d.dll, ucrtbased.dll) on the exe path but couldn't find the last 2 in nowhere. (appcrt140d.dll, desktopcrt140d.dll)
I have no idea how to make an exe aplication with all its dll dependencies.
When I use the 'Release-x86' mode it throws the next error by the way.
Exception thrown at 0x62234AE7 (vcruntime140d.dll) in Timber.exe:
0xC0000005: Access violation reading location 0x00000000.
If there is a handler for this exception, the program may be safely
continued.
I fixed it by configuring the release mode of the SFML library in the project's properties and by switching to 'Release-x86' mode instead of 'Debug-x86'.
You can read more about how to configure your SFML projects here: https://www.sfml-dev.org/tutorials/2.4/start-vc.php

ImageWatch in Visual Studio 2013 : exception has been thrown by the target of an invocation

I currently work with OpenCV C++ in Visual Studion 2013 (Community). I have installed the plugin ImageWatch into Visual Studio, which is useful debugging aid.
After a recent upgrade of Windows 10 (I was already was working with Win 10 and it was fine), I started to receive the following error : "exception has been thrown by the target of an invocation" when opening ImageWatch from 'View/Other Windows/Image Watch'
I have tried un-/re-installing ImageWatch and updated VS 2013 to the latest .Net Version (5.0) for 2013. I also, as suggested on other posts, where the same error has been generated for different reasons, shortened the length/removed some of the lengthy less used System Environmental Variables. All to no avail.
Part of the symptoms I received from Win 10 update were some missing .dll messages for MSVCP110.dll and MSVCR110.dll, generated directly after start up (of my PC). A quick search indicated that I was missing some crucial Visual C++ Redistributable x64 and x86 updates for Visual Studio 2012. (see http://answers.microsoft.com/en-us/windows/forum/windows_8-winapps/the-program-cant-start-because-msvcr110dll-is/f052d325-3af9-4ae5-990b-b080799724db)
These can be download here:
https://www.microsoft.com/en-us/download/details.aspx?id=30679#
After installing these updates for x64 and x86 and a reboot, the dll messages disappeared at start. Following a reinstallation of ImageWatch plugin, I no logner recieved the "exception has been thrown by the target of an invocation" and Image Watch was opening and running fine.