I have just saved my program as an exe file. When I try to open this I get the following error.
Any ideas?
Printable View
I have just saved my program as an exe file. When I try to open this I get the following error.
Any ideas?
Activation context generation failed for "C:\Users\s\Desktop\Main Program\ImageScope.exe".Error in manifest or policy file "C:\Users\s\Desktop\Main Program\ImageScope.exe" on line 19. Invalid Xml syntax.
There is an XML syntax error in the application manifest or in assembly manifests of dependencies.
Usually it will actually be a low-level XML problem like a missing closing tag, but it can also be related to XML element name vs. namespace conflicts.
I think it is also saying this is an embedded manifest resource that is incorrect.
Thanks for the reply. If it is because of a missed closing tag wouldn't I receive an error when running my program through visual basic? Also, I don't understand what you mean by XML element name vs. namespace conflicts, could you explain a little more please.
Thanks a lot :)
Can we please see the Event Log File???
No. Running in the IDE handles tons of things diffrently.
Big topic and nothing we can cover here in a few words.
XML tag names can be qualified by namespaces defined in schemas. Manifests use tags defined in several schemas, and getting these wrong can result in SxS failures.
Where did you get this manifest from? What is wrong in line 19?
What Debug.Print files? Why assume he's doing any? And besides the program never gets that far, it never runs.
This has nothing to do with runtime files that I can imagine, and the event log clearly says there is an XML syntax error. This happens very early in CreateProcess before the runtime would even begin to be invoked.
Can you post the XML project source code. And please really try to comment your work, as it will take along time to read and interprete if you haven't done so...
My guess would be that the manifest is the only XML he's dealing with, and that's exactly where the syntax error is.
Your program logic never sees or touches that XML. It is configuration data about your program that Windows uses to start the program. It's all part of how things changed in Windows starting with XP. Most VBers ignore it and rely on appcompat to let their programs keep running.
So he probably doesn't have any "XML project" at all.
If anything, we need to see his manifest.
I would also start by: Looking at the contents of his VBP file, that works as his project file...
[Tearing hair out.]
No, it is unrelated to anything in the .VBP file. It is a SxS manifest syntax error.
I have some problems with my VBPs that they expire, after a few saves of the project files. I just thought that he/she had the same problem, as me. As we are using the same programming language.
-- Just drawing paraellels, here. Sorry for the mix up!!
Does the project run as excepted in the Visual Basic 6 IDE?
ah ok! I did some searching on the internet and found this. Hopefully, the article has some usefully information for the original poster.
Yes, but I doubt the OP is using MMM.
In any case the MMM bug has been fixed, though the new version hasn't been posted yet. Most people aren't using buggy libraries like that ZLibTool control. If they can't get the strings right in their typelib info no telling what else more serious might be broken. Sad, just sad.
Ahh, the new MMM has been posted.
Hi every, sorry I have been away for a few days. Thanks for all your replies and insights.
I am using the same machine I programmed it on
Yes it works fine when I run it within Visual Basic.
As far as the manifest and XML logs you are mentioning I am unsure on how to gather these, so if you think they would help please guide me on this.
I have uploaded the project, hopefully it will help in finding the problem:
http://www.angelfire.com/me5/sljackson/FileFinder.rar
Thanks again for your help :wave:
Sorry about that, the file was too large to be uploaded on the forum, however I have uploaded it here:
http://www.angelfire.com/me5/sljackson/FileFinder.rar
It should work just fine when you run it through Run-Time Process. But the thing is in Compile-Time Process, is very different, in deed. I have found that to be, just so...
There seemed to be a problem with the link I provided, here is another one:
https://rapidshare.com/files/461489832/FileFinder.zip
Any help on this would be greatly appreciated! Thanks