Vista - side-by-side

How do I get rid of the side-by-side configuration is incorrect, is there
any body out there that can explain it, thank you.

Hello Antonie,
We need to see more information from you as to what you are seeing?
When do you see this error message? At boot? When you logon? When you
start an APP? Random popup?
Where do you see this error message? Pop-up? Event Message? Error Dialog?
What is the exact string of the error message?
Are you programing or installing Visual Studio for example?
It's more common when programming or from an application.

Here is a description of Side-by-Side Assemblies
http://msdn2.microsoft.com/en-us/lib...29(VS.85).aspx


Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|> From: "Antonie Bakker" <antonie@xxxxxx>
|> Subject: side-by-side
|> Date: Sat, 15 Mar 2008 14:54:35 -0600
|> Lines: 3
|> Message-ID: <3F67C818-6FB7-4579-84B8-D6F33903BCA5@xxxxxx>
|> MIME-Version: 1.0
|> Content-Type: text/plain;
|> format=flowed;
|> charset="iso-8859-1";
|> reply-type=original
|> Content-Transfer-Encoding: 7bit
|> X-Priority: 3
|> X-MSMail-Priority: Normal
|> X-Newsreader: Microsoft Windows Mail 6.0.6000.16480
|> X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16545
|> X-MS-CommunityGroup-MessageCategory:
{E4FCE0A9-75B4-4168-BFF9-16C22D8747EC}
|> X-MS-CommunityGroup-PostID: {3F67C818-6FB7-4579-84B8-D6F33903BCA5}
|> Newsgroups: microsoft.public.windows.vista.security
|> Path: TK2MSFTNGHUB02.phx.gbl
|> Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.security:14064
|> NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
|> X-Tomcat-NG: microsoft.public.windows.vista.security
|>
|> How do I get rid of the side-by-side configuration is incorrect, is
there
|> any body out there that can explain it, thank you.
|>
|>

A side by side error is "normally" displayed when starting an application that has an incorrect manifest file
used to enable XP and Vista styles, or by a manifest that is embedded in an application, and the manifest
"resource" did not have the proper byte count.
For a manifest embedded as a resource in a Visual Basic application, the byte count of the manifest resource
must be evenly divisible by 4.

--

Steve Easton






"Antonie Bakker" <antonie@xxxxxx> wrote in message
news:3F67C818-6FB7-4579-84B8-D6F33903BCA5@xxxxxx