So, I wanted to develop a little Filesystem Mini-Filter driver for windows.
I have installed Visual Studio 2019 and 2022 community edition with the following list of packages:
WDK
SDK
Python Development
Desktop development with C++
Universal Windows Platform development
Linux and embedded development with C++
Optional Packages:
C++ CMake tools for Linux
IntelliCode
Embedded and IoT tools
Legacy Embedded and IoT tools
With those installed I still don't have FileSystem Mini-Filter project type available. I also tried to search for it under Individual Components but it do not exist.
I came across this question: https://learn.microsoft.com/en-us/answers/questions/720582/filesystem-mini-filter-template-won39t-appear-in-v.html
Which seem to have worked for the guy, but a re-install did not work for me.
Is there anything I am missing here?
Related
How can I restore my SageMaker Studio Lab environment so that it connects successfully again to the d2l:Python kernel? I installed some packages using %pip (instead of %conda as I have since learned is recommended -- the packages I needed were not available on conda), and now my SageMaker Studio Lab will only connect to the Python kernel. Apparently, I have introduced some dependency issues with the packages I installed.
I have searched stackoverflow (and google) looking for a solution, but so far I have not found anything on point.
Everytime I see a driver tutorial I see they use visual studio, I was just wondering if it is absolutely required to install it in order to develop windows drivers?
Say for example I would like to compile the following driver: (source)
NTSTATUS DriverEntry(PDRIVER_OBJECT DriverObject, PUNICODE_STRING RegistryPath)
{
DbgPrint("Hello World\n");
return STATUS_SUCCESS;
}
How would I be able to compile/link it without visual studio? I have searched all over the place.
The linked tutorials are based on older WDK builds. You can get the old WDK and follow the tutorial, but I don't really recommend it.
Recently, the common way to develop Windows drivers is to use Visual Studio, but there is also a similar approach to the tutorial, which is developed from the command line environment.
https://learn.microsoft.com/en-us/windows-hardware/drivers/develop/using-the-enterprise-wdk
Of course, you don't have to install Visual Studio as using EWDK.
If you would like to use a different IDE then you must use the Enterprise Windows Driver Kit (EWDK) https://learn.microsoft.com/en-us/windows-hardware/drivers/develop/using-the-enterprise-wdk
After downloading and unzipping the archive you will need to launch LaunchBuildEnv.cmd and then run MsBuild.
Example:
Msbuild my_driver_project.vcxproj /p:configuration=debug /p:platform=x64
This assumes that you will write your own vcxproj file. Details about the file format here: https://learn.microsoft.com/en-us/cpp/build/reference/vcxproj-file-structure?view=vs-2019 and you could look at some driver samples from Microsoft here: https://github.com/microsoft/Windows-driver-samples
If you are just starting out with Windows Drivers I would say that using Visual Studio and WDK is a good idea because you can concentrate more on core Driver Development concepts and after you have something working you can write your own vcxproj file and use the eWDK. Having some examples of vcxproj files is useful.
If you do go down the Visual Studio route you can use Visual Studio Community edition which is free for non-commercial use.
It is important to install Visual Studio prior to WDK because the WDK is essentially a plugin to Visual Studio.
Additional instructions and download links for Visual Studio and WDK https://learn.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk
I am trying to migrate my silverlight applications from version 3 to version 4. I've been running into this problem. when i try to install silverlight4 tools for visual studio 2010
Visual Studio 2010 or Visual Web Developer Express 2010 or Visual Phone Developer Express 2010 that matches the language version of Silverlight Tools 4 must be installed before installation of Silverlight Tools can continue. Silverlight Tools is available in other languages at http://go.microsoft.com/fwlink/?LinkId=177432.
I have installed
microsoft visual studio 2010 professional
version 10.0.30319.1.RTMRel
Microsoft .net framework
version 4.0.30319 RTMRel
please help!!!!!
Silverlight tools 4 is available in English, French, German and Japanese. You need to have downloaded the correct language version of the Silverlight Tools (note the language combobox).
If your version of Studio is installed for another language then you could try installing the English Visual Web Developer Express 2010 (it should install fine side-by-side with your standard product) then installing the Tools. I'm not sure that will get you completely to where you'd want to be as far as templates are concerned but it should get you going.
How to determine what failed
If you use the Web Platform Installer to install, it tells you in the log file what happened.
IronSpigot::Main::LogPackageNameAndVersion(): Package Name = Silverlight 4 Tools for Visual Studio 2010
IronSpigot::Main::LogPackageNameAndVersion(): Package Version = 10.0.30319 1033
It will compare these against the values in the following two registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0\Setup\VS\BuildNumber\1033
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\General\UILanguage
If you have VS.NET 2010 SP1 for en-us, the first will contain '10.0.40219' and the second 1033.
The setup confusingly reports this as a language issue, but if you read carefully it is a language and version issue.
Here's how to work around the version check:
Using regedit, change the first key to 10.0.30319. Run the setup.
Using regedit, change the first key back to 10.0.40219
I recommend reapplying SP1 to be safe, but I'm not sure if it is required.
This other answer has a longer solution which is to uninstall SP1, install the tools, then reinstall SP1.
coudn't find the soulution.
however my issue resolved when i installed the same build version of Visual Studio Premium version.
I have a .NET WinForms application that I've converted into a COM dll using the Interop Forms Toolkit 2.1. Thet setup project for the application has both my tlb as well as the Microsoft.InteropFormTools.tlb file set to Register as vsdrpCOM. The prerequisites for the project are to ensure that Windows Installer 3.1, .NET Framework 3.5 SP1, and the Microsoft Interop Forms Redistributable Package 2.0a is installed.
When I run this locally on a Windows XP box with both Visual Studio 2010 and Visual Studio 6 installed, it works fine. However, on this Windows XP machine, I receive an error stating: "Class does not support Automation or does not support expected interface."
Any ideas?
I got it. For those of you that are running into the same, do the following:
Go into Visual Studio 2005, 2008, or 2010 (I used 2010) and build your Interop Form.
Then, go into Visual Basic 6. If your library is not already referrenced, reference the
library.
Build your VB6 executable.
Go back into Visual Studio (.NET version) and build only your installer. This way the installer and VB6 both have the same .tlb file
You're good to go. Thanks for the suggestion Kris!
You have RegAsm the assembly (see stackoverflow for more) on the machine you want to install the application on. The assembly should also be in the directory where the VB6 application runs, or installed in the GAC.
I would like to install Visual Studio 2008 and MS SQL Server 2008 on Ubuntu OS which I have in my PC.
Wine is great, but using it for either Visual Studio or MS SQL Server is probably pushing it. Both are behemoths that tend (especially VS) to use the latest MS APIs. More to the point, both VS and MSSQL are listed as Garbage in Wine's db, meaning compatibility is very poor.
I would recommend you take a serious look at the available tools on GNU/Linux, such as MonoDevelop, Mono, Eclipse, MySQL, etc. You can use cross-platform build technologies, such as nant to build the same apps on both platforms.
If that isn't an option, then you will have to resort to virtualization, as noted by sean.
This answer might help you. Visual Studio and SQL Server are for Windows OS variants. You'll need some sort of VM to run on Ubuntu.
If you have some sort of Windows OS disks available to you (XP / Vista / 2008), then you could consider installing Windows under VirtualBox, and installing your software inside that VM. That used to work really well for me when I was still on Ubuntu.
I've been developing using Visual Studio in Ubuntu since version 10.04, and there is a solution, although I would recommend that you run the 64 bit version of Ubuntu and have at least 4Gb of ram available.
Install the latest version of VirtualBox (download from the website, rather than using the ubuntu repository), and install Windows as a virtual machine. You need to allocate a virtual disk and then, when the virtual machine starts for the first time, either install Windows from a CD/DVD, or select a CD image to use within VirtualBox.
You will also see, with the later versions of VirtualBox, something called "seamless mode". This essential hides the virtual machine, so that instead of running in a window, it will integrate with the Ubuntu desktop. That way, you can run Visual Studio in what looks to be native to Ubuntu.
I have tried both VMWare Player and VirtualBox and found VirtualBox to be better for my setup. Although VMWare Player has something called VMWare tools, which provides an API layer to better translate Windows calls to your video card, this can be temperamental if you're using an ATI card (speaking from experience with a Mobility Radeon HD 4600). Nvidia provide much better driver support in Linux than ATI do.
Hope this helps!
I think is better to simply dual boot to write your .net code. It will put your hardware to better use, and you will be able to focus more since all the programs on which you waste your time will be on the linux side :D (at least that's the upside for me)
To use Visual Studio 2008 and MS SQL Server 2008 in any Linux..
Just try sharpdevelop: http://www.icsharpcode.net/opensource/sd/