I want to "install" a credential provider.
What I have already done:
I installed a vm with windows 8.1. Downloaded the Windows 8 Sample. Built the dll with Visual Studio. Copied the dll to the System32 folder in my VM and executed the register.reg file in the VM.
So I´m asking if these steps were right and if the dll file should have a special name?
look at:
https://github.com/DavidWeiss2/windows-Credential-Provider-library
the most relevant link from there is:
Credential Providers in Windows 10 - Microsoft Windows 10 summary page in the MSDN (still kind of a WIP)
Related
Microsoft website says about Cloud Files API (Cloud Sync Engines):
Starting in Windows 10, version 1709, Windows provides the cloud files
API.
However, OneDrive that is built using this API can run on earlier Windows versions, including Windows 8.1. I guess that I just need to install all Windows updates or need to install some windows components on Windows 8.1.
Is Cloud Files API supported on Windows 8.1?
I have tested
OneDrive on Win 8.1 x64 Version 6.3 (Build 9600)
And OneDrive on Win 10 x64 Version 1909 (Build 18363.1082)
Windows 8.1 does not support offline files in the manner Windows 10 is doing. It just synchronizes all files from the server to the client.
I have also tried calling cloud filter API - it is not supported on Windows 8.1
Unhandled exception. System.TypeLoadException: Could not find Windows Runtime type 'Windows.Storage.Provider.StorageProviderSyncRootManager'
I set the path "JAVA_HOME" and installed WSO2 IS 5.6.0 x64 on Windows 2016 Server. After the installation, I try to start the server via "wso2server.bat", but I get the message "The system cannot find the path specified. The batch file cannot be found". After doing this operation, when I looked into the folder where the server was installed, I noticed that all files are deleted.
Am I doing something wrong? How to correctly run WSO2 Identity Server?
Thank you for pointing this issue with WSO2 Windows Product Installers. The issue is resolved and updated product installers are now available in WSO2 website.
You can download WSO2 IS 5.6.0 x64 Windows Installer from here. Then install WSO2 IS 5.6.0 on your machine using downloaded '.msi' file. After installation, start the server by clicking on the shortcut that build by the installer. You can find WSO2 IS 5.6.0 shortcut in following location.
Start Menu -> All apps -> WSO2
or you can search "Identity Server 5.6.0" in Windows search and click on the shortcut. This will start the WSO2 Identity Server on your machine.
For new WSO2 Products Installers you do not need to set JAVA_HOME separately. It contain jdk1.8.0_192 and if JAVA_HOME is not set, it will automatically set JAVA_HOME to jdk1.8.0_192 and start the WSO2 Product.
This blog could be a help for you to understand the installation progress.
For me the problem was solved with not downloading the windows x64 installer but rather the binary
wso2is 5.6.0 binary.
After downloading you just open bin directory and run the wso2server.bat file.
If you need to make it windows service use the NSSM
We are attempting to migrate our old web server to a new web server. We are trying to install Effalre's CFX_ImageCR3 tag on our Windows Server 2008 R2 64 Bit server running ColdFusion 10 64-Bit.
We've installed the latest setup file from Efflare's website and have registered the CFX C++ Tag in the ColdFusion administrator just as the documentation describes, but when the code that uses the CFX_ImageCR3 tag executes, it says "Unable to load library."
After searching Google, one person recommended we run Dependency Walker to see what DLL's were missing. On the new server, it says the following 'delay-load dependency module was not found'
- GPSVC.DLL
- IESHIMS.DLL
- MF.DLL
- MFPLAT.DLL
- MFREADWRITE.DLL
- WLANAPI.DLL
For comparison, I ran the same program on the old server on which that CFX tag is working. It reported that GPSVC.DLL and IESHIMS.DLL could not load, but the other ones could.
Both of the servers are running the same Operation Systems and the only difference is Cold Fusion 10. Is it possible that I'm just missing some DLLs on the new server? Could it be that it is not compatible with ColdFusion 10 64-Bit? Can you load 32-bit DLL CFX C++ tags on a 64-bit install of CF?
Any help is greatly appreciated.
Thanks
Solution found. It appears that the C++ CFX tax is 32 bit and is compatible with ColdFusion 64-bit version. Effalre currently has a beta installer on their VIP download site, cfx_imagecr_3_service_beta_081030.exe, which is the Java tag.
This was a bit tricky to figure out at first, but once you install the beta make sure you follow these steps:
Install the beta installer to C:\efflare\ (Do not install to C:\Program Files (x86)!)
Start the windows service 'Efflare ImageCR 3 Service'
Open the CF Administrator then goto Java and JVM, in the ColdFusion Class Path add: {applicatino.home}/wwwroot/WEB-INF/lib,C:/Efflare/imagecr3.jar
Restart ColdFusion
NOTE: The class path if for the default ColdFusion 10 install. The first path must point to the directory where you have a cfx.jar file. If you get the error -java.lang.NoClassDefFoundError Exception com/allaire/cfx/CustomTag it is because the class path is not pointing to where the cfx.jar file is located at.
I am using Windows 64 bit machine (windows server 2008) & have IIS 7.5. When I try to build one of project which is in C++, it shows ahadmin.h file missing.
I am very new to IIS server project.
You need to download and install Windows SDK. It doesn't seems like this file comes with Visual Studio, but it's part of the SDK.
I have an outlook 2010 add-in that has a service reference to a simple web service we have set up.
The config for the service is in the app.config file.
This add-in is deployed using windows installer into the program files folder.
This has been working without a problem until yesterday.
Yesterday I installed VS 2010 SP1 and now when the add-in tries to access the web service it has the error "Could not find default endpoint element that references contract in the ServiceModel client configuration section."
Does anyone know what has changed and what is causing this problem?
If I open the project in VS, build and then run from within VS the config is picked up fine.
Thanks
Gavin
The actual solution is more simple. There was a breaking change made to VSTO 4 sp1 in that the manifest has to be a fully qualified URI. So when building your setup project, you must prefix the path to the manifest with file:/// and everything works as you'd expect again. They didn't get the documentation and tutorial pages updated in time for the release. I'm not sure that they have been yet.
Perhaps you're hitting a problem with extensionless services after installing SP1? http://support.microsoft.com/kb/2468871 - Issue 16?
I had this exact same problem. After installing Visual Studio sp1 (which installs VSTO 4 sp1), my Outlook addin could no longer find its config file for service endpoints. The only solution I've found so far is to run the VSTO setup (the new one) and choose uninstall, then run the old version that was previously installed and rebuild the setup package. If the new version is installed on the client machine, that machine will have this issue. Your setup may not detect it because typically you specify a minimum version for it to look for. I haven't found any other info about others having this problem besides yourself or anything official from MS about the problem.