WDK changes from 10.0.10075 to 10.0.10240 - driver

I have a kmdf driver I've been using since the beginning of Windows. I will probably be rewriting it to UMDF, but I have noticed differences in the WDK from 10.0.10075 to 10.0.10240. I include
usbdlib.h
ntstrsafe.h
usbbusif.h
These files appear in C:\Program Files (x86)\Windows Kits\10\Include\10.0.10075.0\km
but not
C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0
what happened? are they in a new file now?

I see the files: "C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\km\usbdlib.h", "C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\km\ntstrsafe.h" and "C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\km\usbbusif.h" on my setup.
Make sure you also have the WDK installed and not only the SDK.

Related

Location of nmake in VS2019 is not generic. Or am I missing something?

I am creating a generic script to deploy on the build server to build our project using VS 2019. The location of nmake in VS 2019 is at: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin. The inclusion of numbers like 14.29.30133 doesn't allow the script to be very generic.
In the earlier generations of VS, nmake paths were like: C:\Program Files\Microsoft Visual Studio 10.0\Vc\bin or C:\Program Files (x86)\Microsoft Visual Studio 11.0\Vc\bin
Maybe I installed MSVC incorrectly? Any help is appreciated. TIA.
You installed MSVC correctly, and yes, this can cause some headaches, because the version number in the folder name changes with every new minor release of VS 2019.
To resolve this, use this command line snippet for getting the path to the latest installed nmake.exe into the variable %NMAKE%:
set VSPATH=C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional
for /f %%i in ('dir "%VSPATH%\VC\Tools\MSVC" /b') do set VCTOOLSVERSION=%%i
set NMAKE="%VSPATH%\VC\Tools\MSVC\%VCTOOLSVERSION%\bin\HostX86\x86\nmake.exe"
This works for all intermediate versions of Visual Studio 2019 I tested it with.

VS 2019 update to 16.8.4 broke every single one of my solutions

I don't recall the previous version I had (it could have been 16.8.1), but updating just now to 16.8.4 results in none of my solution projects being able to load. Here's the output window for one of my solutions:
F:\Users\username\Documents\Visual Studio Projects\FitnessManagerCore\FitnessManagerCore\FitnessManagerCore.csproj : error : The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Roslyn\Microsoft.CSharp.Core.targets" was not found. Confirm that the expression in the Import declaration "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Roslyn\Microsoft.CSharp.Core.targets" is correct, and that the file exists on disk. C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.CSharp.CurrentVersion.targets
F:\Users\username\Documents\Visual Studio Projects\GeneralUtilities\GeneralUtilities\GeneralUtilities.csproj : error : The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Roslyn\Microsoft.CSharp.Core.targets" was not found. Confirm that the expression in the Import declaration "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Roslyn\Microsoft.CSharp.Core.targets" is correct, and that the file exists on disk. C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.CSharp.CurrentVersion.targets
F:\Users\username\Documents\Visual Studio Projects\FitnessManagerCore\FitnessManagerConsole\FitnessManagerConsole.csproj : error : The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Roslyn\Microsoft.CSharp.Core.targets" was not found. Confirm that the expression in the Import declaration "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Roslyn\Microsoft.CSharp.Core.targets" is correct, and that the file exists on disk. C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.CSharp.CurrentVersion.targets
VS advised to try to reload the projects manually. When I attempt this, I get the following error message:
It seems Microsoft has no means to roll back a previous installation. I do not have a restore point. I do not want to uninstall/reinstall.
Edit:
I just tried creating a new solution to see what would happen if I tried to load one of my existing projects. When creating a console app w/ .NET Core, I get this:
Update:
This latest VS 2019 simply does not want to work on my machine in any capacity. I uninstalled VS 2019, rebooted, and attempted to reinstall. The installation stops midway with the below error message. When I click "Report this problem", it opens a Microsoft web page to report the issue, but says "Disconnected from Visual Studio". Since I can't roll back to a previous version according to what I'm reading, I guess I just can't use VS 2019 anymore.
You could check in your csporj file if you have:
<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
You would need to change MSBuildToolsPath to MSBuildBinPath, like this:
<Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" />
When you create a project in Visual Studio 2008, $(MSBuildToolsPath) is added by default to your csproj file as the path to Microsoft.Build.Engine v3.5.
Be sure to change it to $(MSBuildBinPath) which is the path to Microsoft.Build.Engine v2.0.
(more info here)

F# broken in VS build tools 2019 16.6.0

After installing this version, nothing that touches F# will build, everything throws the same exception:
error FS0193: Could not load file or assembly System.Buffers, Version=4.0.3.0, blablabla..
Apparently it's nothing to do with what I'm building. Even trying to execute let x = 3 in fsi.exe has the same problem.
Anyone else had this problem?
Yes, this is a known problem, see https://github.com/dotnet/fsharp/issues/9295.
While the next fix isn't out yet, you can resolve it by manually copying the missing assemblies. The exact list of missing assemblies is mentioned in this comment. The cause was explained by Kevin Ransom to be that the Setup for MSBuild didn't get the new dependencies for fsc.exe.
Note that FSI from within Visual Studio shouldn't have this issue, nor should building from within Visual Studio 2019. The way I understand it, only the MSBuild Tools are affected.
For posterity, in case the links go dead, the workaround in the Github issue is to just copy the dlls over:
copy "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\Common7\IDE\PublicAssemblies\*.dll" "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\Common7\IDE\CommonExtensions\Microsoft\FSharp"
Edit: the source path given above may not always be correct, depending on what versions of VS you've installed. Alternatively, try:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\PublicAssemblies
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\PublicAssemblies
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\PublicAssemblies
C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\Common7\IDE\PublicAssemblies
If you only want to copy the minimal set that's needed, just copy only these files, that's the diff set:
System.Buffers.dll
System.Memory.dll
System.Numerics.Vectors.dll
System.Reflection.Metadata.dll
System.Resources.Extensions.dll
System.Runtime.CompilerServices.Unsafe.dll
System.Threading.Tasks.Dataflow.dll

TFS Build not finding Dlls

I am new to TFS build. I am using TFS Visual Studio Template.
My app uses dev express dlls.
All my devexpress dlls are checked into Common Folder:
When I run the build, build agent is failing with unable to find dev express component. Its looking for dlls under : C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.1
2017-05-23T19:15:04.0271172Z For SearchPath "{TargetFrameworkDirectory}".
2017-05-23T19:15:04.0271172Z Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\DevExpress.Charts.v15.2.Core.winmd", but it didn't exist.
2017-05-23T19:15:04.0271172Z Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\DevExpress.Charts.v15.2.Core.dll", but it didn't exist.
2017-05-23T19:15:04.0271172Z Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\DevExpress.Charts.v15.2.Core.exe", but it didn't exist.
2017-05-23T19:15:04.0427439Z Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\Facades\DevExpress.Charts.v15.2.Core.winmd", but it didn't exist.
2017-05-23T19:15:04.0427439Z Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\Facades\DevExpress.Charts.v15.2.Core.dll", but it didn't exist.
2017-05-23T19:15:04.0427439Z Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\Facades\DevExpress.Charts.v15.2.Core.exe", but it didn't exist.
2017-05-23T19:15:03.7771166Z 7>ResolveAssemblyReferences:
2017-05-23T19:15:04.0271172Z Primary reference "DevExpress.Charts.v15.2.Core, Version=15.2.5.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a".
2017-05-23T19:15:04.0271172Z ##[warning]C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): Warning MSB3245: Could not resolve this reference. Could not locate the assembly "DevExpress.Charts.v15.2.Core, Version=15.2.5.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
2017-05-23T19:15:04.0271172Z 7>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "DevExpress.Charts.v15.2.Core, Version=15.2.5.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [E:\agent\CentralCompliance\_work\9\s\CentralCompliance\CentralCompliance.csproj]
2017-05-23T19:15:04.0271172Z For SearchPath "{CandidateAssemblyFiles}".
Any idea why its not looking into the common folder? What am I doing wrong?
Thanks for help.
Due to the VS designer specificity, all designer assemblies should be installed in the GAC. Guess this is why it's looking for dlls under:
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.5.1 instead of your common folder. It's not possible to deploy those assemblies to computers without DevExpress installation. So does the build agent. The design assemblies which will be put into the GAC during the DevExpress installation.
Besides to avoid the license issue, you should also need to install the DevExpress on build agent.
We are verifying and integrating the license information at the
"building an application" stage. So, it's necessary to have our
components installed and registered on a machine. Otherwise, the
trial window may appear. You can organize a build server and build
projects there. The build server should have the components
installed as well, however, you can be sure that you will not get a
licensing issue.
More details please take a look at below linkļ¼š
Is it possible to keep DevExpress dlls in TFS
Add DevExpress libraries to TFS source control
You have to install DevExpress on your build agent. The build process restores the dependencies by using a local DevExpress installation.

This java mosquito keeps biting me- NoClassDefFoundError. Spray ! Spray ! Spray ! ..& Nothing happens

I am trying to use a bunch of JAVA apps and I keep hitting this wall. I looked up and followed pretty much everything out there that could cure it. But this is a JAVA super bug mosquito. Pl tell what is happening
C:\Users\Administrator>java -version
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
C:\Users\Administrator>where java
C:\Program Files\Java\jdk1.8.0_45\bin\java.exe
C:\Users\Administrator>echo %java_home%
C:\Program Files\Java\jdk1.8.0_45
C:\Users\Administrator>echo %path%
C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\WINDOWS LIVE;C:\PROGRAM FILES (X86)\COMMON FILES\MICROSOFT SHARED\WINDOWS LIVE;C:\WINDOWS\SYSTEM32;C:\WINDOWS;C:\
2\WINDOWSPOWERSHELL\V1.0\;;C:\PROGRAM FILES (X86)\INTEL\OPENCL SDK\2.0\BIN\X86;C:\PROGRAM FILES (X86)\INTEL\OPENCL SDK\2.0\BIN\X64;C:\PROGRAM FILES (X86)\COMMON
M FILES (X86)\WINDOWS LIVE\SHARED;C:\PROGRAM FILES (X86)\WINSCP\;C:\PROGRAMDATA\CHOCOLATEY\BIN;c:\Program Files\WIDCOMM\Bluetooth Software\;c:\Program Files\WID
ram Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\Skype\Phone\;C:\Program Files\Java\jdk1.8.0_45\bin
C:\Users\Administrator>echo %classpath%
C:\Program Files\Java\jdk1.8.0_45\lib
I also have JRE installed but I removed it from the PATH ( i.e. the bin dir of JRE as also that of Oracle's ) to make sure there is JUST one exe for Java.
I get this error in spite of that.
I am on windows 7
The problem was rt.jar needed for the java.lang.Object wasn't there in the lib dir.
My 32 bit JRE was working. Just 64 quit. Transplanting RT.jar from x86 to x64 from lib did not work so I uninstalled and reinstalled JDK ( with JRE ) and it ran well.
The rt.jar got prolly removed by Trend AntiVirus scan

Resources