I am trying to use Skype4COM.dll to get the list of contacts for a Skype user and to send messages to a user. I have Visual Studio 2010 and the application I am trying to develop is a C++ based one.
I have issues with importing the Skype4COM.dll into the project. Following are steps I had done:
Downloaded the dll from http://developer.skype.com/accessories/skype4com
Register the dll using regsvr32 command
Created a Win32 Console Application in Visual Studio
Added Skype4COM.dll to the Additional Dependencies of the project
Tried - #import "Skype4COM.dll"
I get an error saying:
Error: cannot open source file "$(SolutionDir)/Debug/Skype4COM.tlh"
Can someone please help me with the problem.
Also it'll be great if someone can point me to a good article on how to use/configure Skype4COM with VC++
Thanks,
Raaja
Solved it by using C:\Program Files (x86)\Common Files\Skype\Skype4COM.dll instead of the one downloaded from the internet.
Thanks!
Related
I've run in to an issue where I can't build a freshly created C++/CLI Class Library project in Visual Studio:
Even though I haven't made any changes I get an error when I try to compile:
Severity Code Description Project File Line Suppression State
Error Could not load UI satellite dll 'FileTracker32UI.dll'. Make
sure it exists in an LCID subdirectory of 'C:\Program Files
(x86)\MSBuild\14.0\bin\'. TestProject c:\Users\abcde\documents\visual
studio 2015\Projects\TestProject\TestProject\FileTracker 1
I've created C++/CLI Class Library projects in the past on the same computer using Visual Studio 2015 without encountering this problem. Any idea what has gone wrong?
I ran into this strange issue today without making any code change. I suspect it appeared due to overnight windows update.
In my case , I copied the two files FileTracker32UI.dll and FileTracker64UI.dll
From
C:\Program Files (x86)\MSBuild\15.0\FileTracker\3082\
To
C:\Program Files (x86)\MSBuild\14.0\Bin\3082\
and it worked. My visual studio version is
Microsoft Visual Studio Community 2015
Version 14.0.25123.00 Update 2
I am hoping the info helps someone.
I had the exactly same problem, after some windows update by my IT.
According to the information (https://forum.dlang.org/post/ezuohezwuzyitjdzpfdw#forum.dlang.org), I renamed the file "FileTrackerUI.dll" to "FileTracker32UI.dll" in the latest LCID folder (latest numbered folder in same location)
Then, it worked at my PC.
Good luck
In my case it was a path issue. Using another directory (shorter path without special characters) solved the problem
I got an old vb6 project which I am trying to get going.
I have installed visual studio 6, installed vb6 service pack 6 and the update for service pack 6.
However when I open the project I keep getting the error:
fpSpr60.ocx could not be loaded
I figured out with google this has todo with fpspread but I also find this should be included inside vb6.
Does anyone have an idea where to look for?
This is a third-party OCX which is not shipped with VB6. You must obtain it and install it separately.
(I have no association with the company.)
I have the following scenario:
Visual Studio 2010 solution with one WPF-project, output file is "Tool.exe"
Eclipse Shared Library project, output file is "Tool.dll"
I place the dll in the same folder as the exe and then I try to debug using Visual Studio; but I get the following error:
Error while trying to run project: Could not load file or assembly 'Tool' or one of its dependencies. The module was expected to contain an assembly manifest.
I have managed to find a solution to the problem, rename the dll, apparently the exe and dll cannot have the same name. My question is, why is this error occuring in the first place? Why does the name of the dll affect Visual Studio? The error occurs before even trying to pinvoke the dll. If I run my application without Visual Studio it works perfectly, but I want to be able to debug it of course.
Right now renaming the dll is plan B, but before I do that I would like to know if there is anything else I can do to fix this problem?
Thanks in advance.
I found simple steps to solve this error.
1- change your windows.
2- install Symantec Endpoint Protection Client 12.1.6318.6100 x32 or x64 bit.
You can geting it software(32 bit) from link: (ftp://192.168.168.215/Public/Antivirus/Symantec/Symantec Endpoint Protection Client 12.1.6318.6100 x86.rar)
drag and drop it to your software(IE ,....) to work.
3- install all driver on your computer.
4- install Visual studio.
End
(I'm running Windows7 and using Visual Studio 2010.)
I'm using ClamAV in a .NET Azure project, and I'm running into side-by-side errors whenever I run clamd.exe, either through my code or by running clamd.exe on it's own.
In Visual Studio 2010 I am getting the error:
Win32Exception was unhandled The application has failed to start
because its side-by-side configuration is incorrect. Please see the
application event log or use the command-line sxstrace.exe tool for
more detail
And in Event Viewer I get:
Activation context generation failed for
"C:\Users\pconerly\code\AntiVirus_source\WorkerRole\clamav\clamd.exe".
Dependent Assembly
Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.6195"
could not be found. Please use sxstrace.exe for detailed diagnosis.
When I searched for "8.0.50727.6195" it led me to the 2005 redist, so I downloaded it
http://www.microsoft.com/download/en/details.aspx?id=3387
After a restart I am still getting the side-by-side error. Additionally, I think that the redist installer is not completing it's install-- like it's seeing visual studio 2010 and saying "oh, that's good enough, no need for me to install". I haven't tried uninstalling 2010 and using 2005, because the rest of my Dev team is using VS 2010.
What's the deal? How can this be fixed? I'm ready to pull out my hair.
The link Timores posted is the update for Visual Studio. The actual redistributable package is this:
http://www.microsoft.com/en-us/download/details.aspx?id=26347
The version you mention is actually at found here
Microsoft Visual Studio 2005 Service Pack 1 MFC Security Update
Timores is right: the redist should be this one, which is related to this KB entry
As you can see there, msvcr80.dll has been updated to version 8.0.50727.6195.
It is the "security update" of the "SP1" of the 2005 C++ runtime..
Your exe probably requires (through an internal manifest) that specific version.
If it is not found on the system (there's a lot of places searched for) nor in the current folder (with a suitable manifest aside) it won't load the exe since it is not able to "activate the context", that is load the specific DLL required in the manifest.
I had similar issues when my system got updated (windows updates) and the newly compiled EXEs were not working with an old-versioned runtime placed on the same folder.
I had to update msvcr80.dll and its manifest (which I found deep in \windows\winsxs) to make everything work.
Context activation is a tricky matter, anyway :)
HTH
I'm trying to use an external library DevExpress.XtraTreeList.v8.1.dll in my vsto office addin built using VS2010 beta 2. I am getting the following compile time error:
DevExpress.Utils.AppareanceObject threw an exception --> System.NotSupportedException.
The error message goes on to say that for compatibility reasons I can use the NetFx40_LegacySecurityPolicy switch.
I've tried putting this config variable in all of the following locations:
1) my applications config file.
2) C:\Windows\Microsoft.NET\Framework\v4.0.21006\msbuild.exe.config
3) C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\dev.exe.config
None of these have resolved the problem. Here were the references I've used.
re-enable cas
msdn.microsoft.com/en-us/library/ee191568(VS.100).aspx
How do I get rid of this error so I can build the application in vs 2010?
LC.exe fails to process license information of devexpress 9.1.4 dlls
Update: Looks like this program is related to lc.exe. create a file called lc.exe.config that contains
<NetFx40_LegacySecurityPolicy enabled="true"/>
under C:\Program Files\Microsoft SDKs\Windows\v7.0A\bin\ (NETFX 4.0 Tools) solves the problem
This does work, however, you'll also need to create a file for devenv.exe.config to edit form designer changes, and the side effect of that is that COM references in project's will give obscure errors.
The end result, is that we really need an update from DevExpress on this. Allegedly a beta fix with a 2010.1 release is due any time now, come on DevExpress, hurry up! :)