I'm trying to create a custom login for Windows 7 using Credential Provider. I use Windows 7 Professional, Windows SDK 7.0 and Visual Studio 2010 Ultimate. After i build the solution for SampleCredentialProvider from
the sample folder in SDK 7.0 my dll file is created, i copy the dll file into my Windows\System32 folder and i run the Register.reg but nothing is happening at login. According to the documentation in the login screen i should be able to see new users(Administrator and Guest). What have i done wrong? Is there a trick or something?
Thank you.
Are you on Windows 7 64-bit? If so, check to see whether you are building the Win32 version instead. Use the Build > Configuration Manager and make sure Active solution platform is x64, and the Active solution configuration is Release.
Windows SDK for Windows 7 have good Credential Provider samples
Related
Long time reader first time poster here.
I'm a Linux developer trying to get started on Windows development in my new job. I knew it would not be trivial but the first thing I'm trying to do is complete and integrate a netvmini port driver (started by a co-op student) into one of their C++ apps. I am struggling to get the build environment going...
The project was started in Visual Studio 2013 with a Windows 7 target. When I now open it in Visual Studio 2015 and try to build the solution I get:
"Unknown or unsupported property value Win7 for TargetVersion"
for each project. This also happens if I set the configuration to Win8 (both release and debug). If I set it to Win 8.1 I get:
"An SDK corresponding to WDK version '8.1' was not found. Please install the SDK before building"
I have installed every WDK and SDK I can lay my hands on from Windows 7 to Windows 10 using both the web and the VS2015 installer. I have even installed Visual Studio 2013 again but I can't even seem to get the WDK to integrate with that.
The end goal here is to be able to build this (and hopefully debug remotely in kernel mode) from my Windows 10/VS2015 workstation for targets from Windows 7-10. Any advice or documentation that details how to integrate new build platforms into VS would be helpful (all the MS documentation just tells me what I can do if I install this or that, but not HOW to do it)
I also had the same problem after running the Project Upgrade tool.
I discovered when making new configurations that "Win7" and "Win8" TargetVersion are now "Windows7" and "Windows8".
The upgrade tool does not make that change for you but I was able to manually edit my upgraded project with those changes and got it to build for all targets.
I discovered that the installer doesn't install the windows 10 SDK by default. So all the installing of other SDK's was useless. I Also found out that by installing the Win 10 SDK through the VS 2015 installer it integrates and allows me to build for targets back to windows 7 in VS 2015.
I have an application that creates WMSPublishingPoint. After migration to VS2012 (from VS2010) I can't compile the project due to studio can't see 'wmsserver.h' file.
This file is shipped with WindowsSDK 7.1, but there is no such file in SDK for Windows 8.
If I choose platform toolset vs110_xp - it's OK. But I need the v110 toolset.
Here is a link which confirm that developers can use wmsserver.h in development for Windows 8: http://msdn.microsoft.com/en-us/library/windows/desktop/dd874782%28v=vs.85%29.aspx
I tried to reinstall SDK (http://msdn.microsoft.com/en-US/windows/desktop/hh852363), but it didn't help.
Is there any additional link to install Windows Media Services SDK for VS2012? I haven't necessary files after installation of Windows SDK for Windows 8.
The SDK is removed, probably because the component is not supported on Windows Server 2012.
I suggest you to extract the WMS facing code to a separate DLL that uses the vs110_xp set, and use the DLL in your application.
I have an old VB6 application that depends on MSINET.OCX. I'd like to know if I can distribute this application without registering MSINET OCX component. My target OSes are XP, Vista and Windows 7. Do all of them have this component preinstalled?
See if this information from technet helps you. The short of it seems to be that it does not come preinstalled, it is installed when you install an application that uses it. You will need to include it in your installation.
It's not shipping with the OS. It is however delivered with Visual Basic. You must include it within your application setup. For details on Vista and Win7 support see: Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 and Windows 7
I was trying to run an application locally with Enterprise Library 4.1 and do logging to the event viewer. I didn't see Windows 7 under the supported operating systems. Does anyone know of a workaround or if this will not work at all? Also does anyone know if any other logging such as email or DB through Enterprise Library is available on Windows 7?
Thanks in advance.
Yes the enterprise library should work fine as its part of the .NET framework not the OS. Your problem is down to permissions issues.
You need admin rights to 'create' a new source in the event log. You could create a console app to do this (run it under elevated permissions) or set it up directly in the registry.
Once the source is set up you should be able to write your logs away.
P.S - You can use any of the (formatters are they called?!) in the enterprise logging block. (Database, email, text file, etc)
Its setup in the config file. you can use the tool that comes with EL to do this)
Since it works with Windows Vista, it will work with Windows 7.
Under the hood, both operating systems are version 6 and both run the .NET framework.
Enterprise library is built on top of .net so there should be problem.
Enterprise library 4.1 was released before Windows 7, that's why it does not apper listed. However it should work in Windows 7 since it works in Windows Vista.
Firefox depends on an extension and plugin installed by the .NET 3.5 installer to run XBAPs. Unfortunately, in Windows 7 the .NET 3.5 runtime is already installed.
Does anyone know how to get a hold of these plugins/extensions so you can actually deploy XBAPs to FireFox on Windows 7?
Turn out, the answer is to copy the DLL of the extension out of another (presumably XP) machine that can run the .NET 3.5 runtime and deploy it.
I'm uncertain of the legality of this maneuver, but it works.