I performed a new installation of VB6 / Visual Basic 6, but when I try to generate the executable this error is occurring:
'License information for this component not found...'
The application is compiling correctly.
Any suggestion?
Related
Whenever I am creating a new project using Microsoft Visual Studio 2010 in libraries provided from Windows 7, I am getting an error: You have sellected a library. Please select a folder instead. The same error is coming in my project while I am browsing for an existing directory using Qt.
My code is as below:
QString directory = QFileDialog::getExistingDirectory(this,
tr("Select a directory to store"), QDir::currentPath());
Background:
So I picked up Programming the Windows Driver model and tried to build the very first sample it has using visual studio 2013 Ultimate. While the book seems very reputed, there is no update for the sample code.
I saw some signs to used the older "build" instead of current msbuild / visual studio. But that is another learning I am not prepared to do unless required (especially as I didnt find nmake or build quickly enough and i ll be learning older build processes which I dont need to use).
Problem:
error C1083: Cannot open include file: '\inc\wxp\warning.h': No such file or directory stddcls.cpp
Building the sample gives me this error.
I included the folders for wdm.h and warning.h in the includes path. Wdm.h got resolved, but warning.h continues to throw an error - and I dont even know where warning.h in included/referenced.
I can post the entire code if required.
Yes, I am new to driver development.
If this book is too old to use, pointers to "newer" tutorials of Windows driver dev is appreciated.
In Visual studio
Project -> Properties -> C/C++ -> Advanced -> Forced Include file.
There is a hardlink to warning.h here. This needs to be changed to
C:\Program Files (x86)\Windows Kits\8.1\Include\shared\warning.h and the error goes away!
Another useful link for "Programming the Windows Driver Model" Oney:
http://csserver.evansville.edu/~reising/EE%20356%20Fall%202005/Changes%20to%20files%20from%20Walter%20Oney.pdf
Summary: I'm trying to compile a NVIDIA SDK app in Visual Studio 2012 on Windows 8 and I get the error message: FXC : error X3501: 'main': entrypoint not found. I'm new to Windows programming and trying to figure out what this means.
Details:
I'm trying to compile the Multi-View Soft Shadows NVIDIA SDK app. After downloading it I had a vcproj file. I opened this in Visual Studio 2012 on Windows 8 and had some warnings during the conversion but it seemed to open the project correctly.
However, when I build the project I get the following error: FXC : error X3501: 'main': entrypoint not found.
At first I thought this might be because there is no main function in the application. But then I found the wWinMain which I guess is supposed to replace main in some Windows applications. So I think that the source code is correct, but perhaps there is some setting with Visual Studio 2012 that needs to be changed. But searching for that error message hasn't answered my question, so I'm wondering if someone can explain what the cause of the error is and any advice about how I could fix it.
This isn't a C++ problem... the shader compiler, fxc.exe, is looking in your shader code for a function called main. It isn't finding it and throws an error as a result. Right click on your HLSL files and go to Properties -> Configuration Properties -> General. There should be an Item Type field. Change it from HLSL Compiler to Does not participate in build. That should prevent the HLSL compiler from coming along and giving you those errors.
You need to change (in Project Properties -> Linker -> System -> SubSystem) the subsystem of your application from CONSOLE to WINDOWS. After that, the entry point will be changed from Standard C/C++ main to Windows-specific wWinMain.
Trying to build a project that uses managed C++/CLI and it compiles successfully when in the 64-bit build config. When I switch to Win32 config it fails siting the managed C++/CLI dll is not a strong named assembly. When switching configs I have verified that both have the Project -> Configuration Properties -> Linker -> Advanced -> Key File entry has the proper path to the snk file ($(SolutionDir)key.snk)
Not sure if I'm missing something here. I haven't been able to find anything on Google...
[UPDATE]
If I use a post build event in the C++/CLI project the output window shows the following error:
c:\path\file.dll does not represent a strongly named assembly
I'm using the following post build event:
sn -Ra "$(TargetPath)" "$(SolutionDir)key.snk"
Again - the above post build event works on the x64 config but not the win32. (I have tried compiling on both 32-bit & 64-bit machines w/ same result)
Just ran into the same problem today, after some digging it looks like this is caused by a bug introduced in Microsoft Visual Studio 2010 SP 1.
A description of what caused the bug and a workaround can be found at the following link:
http://blogs.msdn.com/b/vcblog/archive/2011/03/11/10140139.aspx
When building an F# project through Visual Studio 2010 (either Build or Rebuild, or Clean -> Build) where I've checked "XML Documentation file" and specified a location in the Build tab of the properties page, I frequently but sporadically run into build failures:
FSC: error FS0193: Access to the path 'xxx.XML' is denied.
I've experience this with several F# projects / solutions. Most of the time I then just turn it off, but I recently noticed then documentation isn't built into the compiled assemblies (I apparently falsely assumed that the XML doc was only for possible external processing and that the doc comments would always get built in).
Any help appreciated.
I know we fixed this bug in VS2010 for F#. I seem to recall that C# and VB had the bug as well (dunno if they fixed it, I can investigate). Do you have a C# or VB project referencing the F# project? (Are you building the solution, or a specific project?)