The company that I am working at is still using visual foxpro, and I am doing a fingerprint scanner using vfp9 and Griaule Fingerprint SDK 2009.
Everything is doing fine during the first run of the program. But when I re-run it againg. The error will happen. Any ideas why I keep on having that problem? Missing GRFINGER.DLL.
It's getting hard for me to find any support today because foxpro application development is getting obsolete.
The rub of the problem seems to be that the first run causes Fox to be somehow unable to find the DLL or to load it. The latter can occur if the DLL itself is findable but one of its dependencies (like its C runtime DLL) is not.
This may be due to a changed search path (SET PATH). If the search path contains relative directories then a simple change of the current working directory changes the effective search path, even though the actual text (set("PATH")) remains unchanged. That can happen because of things like file open/save dialogues, for example.
P.S.: sorry for the belated answer - the question was at the top of the recent/active list because someone had edited the question recently, and only after posting the answer did I realise how old the question was. However, the answer might still be useful for someone with a similar problem.
Related
Ok, I know this is a very old product so I'm hoping there are still a few of us old timers still out there who can help me.
Internally we have several old systems which are in the process of being migrated to c# however routine work is still required within them.
We have had a problem for quite some time and it appears to be getting worse, in fact it was mostly noticed since upgrading to Windows 10.
To give an example one project consists of the main application and 19 dll's all grouped within the project. Any part of the project can be compiled and works fine, but other times I can compile a dll and the dll vbp file gets corrupted.
Corruption could be...
Duplication
Reference=*\G{72F49028-2BDA-4107-9870-FA71E3F7DFA9}#3.3#0#..\..\..\..\..\DLLStore\VB6\Search.dll#
Reference=*\G{72F49028-2BDA-4107-9870-FA71E3F7DFA9}#3.3#0#..\..\..\..\..\DLLStore\VB6\Search.dll#
Or incorrect reference guid
Reference=*\G{72F6675-2BDA-4133-9778-FA71E3F7DE3}#1.2#0#..\windows\---\COMDLG32.OCX (I've forgotten the exact text)
Object={F9043C88-F6F2-101A-A3C9-08002B2F49FB}#1.2#0; COMDLG32.OCX
Removing the reference line fixes this.
I know I could mark the vbp to be read only and then keep changing it as required but I need to get to the bottom of what is causing it in the first place.
Any pointers are greatly received :-)
I'm very new to Visual Studio and Universal Windows Apps Development. As a part of the course, I have this codeSHOW project provided.
I've cloned it successfully in VS 2015, but I can't run the project using the .sln file. Error:
Here's the error log: http://pastebin.com/c012Bba4
I have no clue how to fix it, and the issues on github go unanswered so I can't expect much from there.
This is an known issue in Visual Studio 2015.
The problem is with files with the exact same name under different folders in a Shared project, which in your case is "resources.resjson".
The only workarounds are either to make the file names unique and if that is not an option, to duplicate the files in the projects instead of sharing them out of the Shared project.
This is a VS2015 specific bug, the solution loads just fine on VS2013. You can get some insight into what is going wrong. First note that your got two message boxes that announced this error. Barely visible in your screenshot.
The failure.txt file gives more hints, you can see the stack traces of the two AggregateException that are raised when the solution is loaded. You'll see that two tasks are trying to load the same resources.resjon project item. Not correct of course, quacks like a standard concurrency bug.
Nothing actually goes wrong, Visual Studio can handle the exception and declares it "Recoverable", the projects are still loaded correctly. And compile just fine. Only other thing you need is the Bing Maps SDK, you can download the correct version here.
If you have VS2013 then prefer that version, it doesn't have this bug and loads the solution without any complaint. And minimizes the odds that you'll run into other quirky problems. Given the current stability of VS2015, not great, it is the best way to avoid losing time. Otherwise just ignore the mishap and close the message boxes, some future Update will no doubt fix the bug. You can report it at connect.microsoft.com if you wish. Not actually necessary I think, it looks like VS is phoning home.
I have a MVC5 app using Entity Framework code-first. It has been fine, working for months while I develop it. This morning it worked fine too. Then suddenly I run it for the 10th time of the day, and it won't run. I'm getting a crazy set of errors that aren't consistent.
First off it said it couldn't find mscorlib.pdb. I researched that and downloaded the latest symbols (first place didn't have it, second place did), and now I have the pdb. But I continue to get errors whenever I try to access the DB.
I have seen entityframework.dll and mscorlib.dll mentioned, but very little info is given because it usually just says:
An unhandled exception of type 'System.StackOverflowException' occurred in mscorlib.dll
{Cannot evaluate expression because the current thread is in a stack overflow state.}
I did try to turn on stepping and then I get this file box that is asking me to find files, that I have no idea where they are. The first time, it asked me for enumerable.cs, the second was RType.cs, and the third was IPipelineRuntime.cs. It tries to look in a very obscure folder structure (f:\dd\ndp\clr\src\BCL\System\RtType.cs) but I don't have these files on my machine.
Suddenly none of my projects are working that need EF. I even created a brand new project, with a simple code-first model to try it out and got the same issue.
Please help!
Answer found.
I kept reading on other issues where a lot of people were saying that it was due to someone's own code and not a system issue.
I used the datemodified stamp of the files to determine all the files I had worked on in the few days leading up to the issue.
I went back through and began removing them one by one, and discovered the issue. It was my own recursive code.
I am using Visual Studio and a solution with 10 or so projects in (mostly VB, some C#) which have various dependencies set up. Usually when I compile the solution it works fine. Occasionally when I do it I get a build error saying that one of the projects referenced is the wrong version (I think always the same one, possibly may be two that can cause problems). In this case going to the solution explorer and right clicking on the mentioned project and saying "rebuild" followed by another full build makes it work fine.
I assume there is something set up wrong somewhere but I didn't set up the solution myself initially and a quick look through doesn't show anything immediately wrong.
It feels like there is some kind of race condition, that VS is internally setting the version number of the project it needs before that project has been rebuilt and thus gets it wrong or something like that but I'm sure VS should handle all this sort of thing properly.
Can anybody please suggest places that I could check for whether this has been correctly set up...
And I should finally note that since I don't have reliable repro of this I may not be able to respond to questions too quickly. For example the obvious one of "Could you give the exact error message" will have to wait since I didn't think to copy it this morning, it was only after I cleared it up with the above steps that I thought to post here. Similarly any solutions may take a while to confirm.
Edit to add error message:
Indirect reference is being made to assembly ODP version 1.0.3792.16586, which contains '{{CLASSNAME}}'. This Project references a prior version of ODP version 1.0.3791.18659. To use '{{CLASSNAME}}', you must replace the reference to ODP with version 1.0.3792.16586 or higher.
Edit for more apparently relevant details
Since it has been bought up I will clarify that one of the projects is a web project and that it is this one which is generating the above error message.
Further edit
Having looked further there is a copy of ODP.dll in the bin diretory of my web project. Using windows explorer and right clicking, asking for properties and looking at the version it is version 1.0.3791.18659. Having deleted this (actually moved it elsewhere) when doing a build it recreated this file still with that same version number (ie an old version number).
ODP claims to be a project reference too which still makes me think it should just work... :(
Further Further edit
I think now that the problem is that if the ODP project changes then it gets rebuilt but it doesn't necessary cause all the projets that are dependant on it to be rebuilt. So one project might still be built against the old version and one against the new version. If they are then trying to talk between each otehr with objects from ODP then it goes wrong... I need to confirm this but I'm not sure what would need to be done to fix it at the moment. :)
Is the build order correct? I can imagine if you build one project which references the other one, and that one isn't built yet you can have this kind of problem.
Link: http://msdn.microsoft.com/en-us/library/5tdasz7h%28v=VS.80%29.aspx
If you have a website project, are you sure you have set these to be 'project' references rather than 'bin' references - you could be getting some issues this way.
I had never had this error before, and I didn't move any file, or exclude any reference.
I'm getting this error (link).
In the ajaxcontroltoolkit.dll.refresh file, I get a path to the DLL, but it is a path that was located in someone else's computer (who no longer is in charge of this).
It might as well work if I just re-do the reference, but what is weird is that I've used this reference before, and had no problems. I don't know what triggered it..
Does anyone have any clue ?
--[UPDATE]--
As expected, I've fixed it, but this question remains unanswered. Besides, the exact same problem with a coworker..
Delete the .refresh file and do a Clean and Rebuild.