-
Jan 17th, 2021, 05:29 AM
#1
Thread Starter
Junior Member
VBCCR17SideBySideAndVisualStyles failed to start side-by-side incorrect
I am having a play with the ocx version of Krool's common controls replacement
I have the OCX registered, I have followed the guide created by MountainMan
I have made a basic project, added a Button, the resource file and loaded the resource editor, built the project which runs fine in the ide, and placed the ocx in the folder next to it.
I get a side by side error
I have run sxstrace and it gives.
Code:
=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = Wow32
CultureFallBacks = en-GB;en;en-US
ManifestPath = D:\Source\Uncontrolled\VB6CommonControls\Project1.exe
AssemblyDirectory = D:\Source\Uncontrolled\VB6CommonControls\
Application Config File =
-----------------
INFO: Parsing Manifest File D:\Source\Uncontrolled\VB6CommonControls\Project1.exe.
INFO: Manifest Definition Identity is (null).
ERROR: Line 69: XML Syntax error.
ERROR: Activation Context generation failed.
End Activation Context Generation.
Which sounds like something is up with the .res file itself. I have used manifests in my own projects by i embed them post compile so have not used a .res file before.
Anyone else using these controls had the same issue?
Thanks
-
Jan 17th, 2021, 12:46 PM
#2
Re: VBCCR17SideBySideAndVisualStyles failed to start side-by-side incorrect
We can't see your XML so we have to guess.
One guess might be that you failed to pad your raw XML to a DWORD boundary before adding it as a resource. That can result in padding with NUL bytes, which are not valid XML white space.
-
Jan 17th, 2021, 02:27 PM
#3
Thread Starter
Junior Member
Re: VBCCR17SideBySideAndVisualStyles failed to start side-by-side incorrect
I am using the .res file, not a projectname.manifest file, or i would be able to diagnose it myself.
My understanding is you add that to the project and it builds it into the exe
-
Jan 17th, 2021, 03:22 PM
#4
Re: VBCCR17SideBySideAndVisualStyles failed to start side-by-side incorrect
Originally Posted by rjsnipe
I am using the .res file, not a projectname.manifest file, or i would be able to diagnose it myself.
My understanding is you add that to the project and it builds it into the exe
Got me. This sounds like the nuttiest thing I've ever heard of.
How does some random manifest predict your program's needs? Not to mention that there are elements there which are supposed to reflect reality: name, version, etc.
name Uniquely names the application or assembly. Use the following format for the name: Organization.Division.Name. For example Microsoft.Windows.mysampleApp. Required.
version Specifies the application or assembly version. Use the four-part version format: mmmmm.nnnnn.ooooo.ppppp. Each of the parts separated by periods can be 0-65535 inclusive. For more information, see Assembly Versions. Required.
https://docs.microsoft.com/en-us/win...tion-manifests
People get away with clunky copy/paste pidgin manifests here and there, but eventually these will bite you. Proper XML syntax is a must though.
-
Jan 17th, 2021, 04:08 PM
#5
Re: VBCCR17SideBySideAndVisualStyles failed to start side-by-side incorrect
Originally Posted by rjsnipe
I am using the .res file, not a projectname.manifest file, or i would be able to diagnose it myself.
You can use Visual Studio 20xx resource editor or Resource Hacker utility to read and update manifest resources in a .res file.
After you create your projectname.manifest file (one way or another) you can indeed embed it in project.res file that is referenced by project.vbp so that you can skip using mt.exe to embed it in final project.exe post compile.
The point is that when project.res gets compiled on File->Make project.exe into final executable it brings projectname.manifest embeded as a resource type 24 too.
cheers,
</wqw>
-
Jan 17th, 2021, 05:03 PM
#6
Re: VBCCR17SideBySideAndVisualStyles failed to start side-by-side incorrect
dilettante, did you ever had any problem because the program name or program version was not right?
If possible please post an example (somewhere).
-
Jan 17th, 2021, 05:44 PM
#7
Thread Starter
Junior Member
Re: VBCCR17SideBySideAndVisualStyles failed to start side-by-side incorrect
I appreciate what you are saying about the manifest, and have my own hand written ones, however I was just following the guide
https://www.vbforums.com/showthread....55#post5129155
I have taken the manifest contents, and was going to embed it myself, when I got hit by the 'out of memory' exception when building the project, that I started another thread about. I am sure that will work, however the .res file is meant to just work, and you can add it to the project, so its not an extra step. It doesn't really matter in the end, as I if I end up using VBCCR17, then I will be adding that manifest section to my own existing one, in the large project I might use it in.
I just thought it was worth asking, its in a guide that is meant to work out the box, and maybe someone else had had issues too. I don't like things not working when they should. I like to know why
Last edited by rjsnipe; Jan 17th, 2021 at 06:14 PM.
-
Jan 17th, 2021, 05:46 PM
#8
Thread Starter
Junior Member
Re: VBCCR17SideBySideAndVisualStyles failed to start side-by-side incorrect
Originally Posted by Eduardo-
dilettante, did you ever had any problem because the program name or program version was not right?
If possible please post an example (somewhere).
To the best of my knowledge you will only get errors with versions of dependent assemblies, not the version of the assembly or exe itself.
-
Jan 17th, 2021, 07:07 PM
#9
Re: VBCCR17SideBySideAndVisualStyles failed to start side-by-side incorrect
Originally Posted by rjsnipe
To the best of my knowledge you will only get errors with versions of dependent assemblies, not the version of the assembly or exe itself.
To my experience the same, but dilletante may have some other information (he is an specialist un manifests).
-
Jan 17th, 2021, 08:25 PM
#10
Re: VBCCR17SideBySideAndVisualStyles failed to start side-by-side incorrect
Originally Posted by Eduardo-
dilettante, did you ever had any problem because the program name or program version was not right?
Read the docs.
Those are assembly names and versions you assign, not necessarily the program's. Ideally, combined, they result in a "strong name" that Windows can use to track them in the assembly cache and in packages. They are marked "required."
Follow the rules of the road as published, or not and risk trouble.
Reminds me of programs that leak handles and memory that seem to work until suddenly they don't.
-
Jan 17th, 2021, 08:27 PM
#11
Re: VBCCR17SideBySideAndVisualStyles failed to start side-by-side incorrect
In any case it sounds like a more fundamental problem here. Bad XML syntax is a separate matter.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|