VC 2008 SP1 manifest adresses old CRT
Dieter Pelz
I installed SP1 für Visual Studio 2008. After rebuild my application the
manifest seems to address the old versions of CRT and MFC.
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC90.CRT"
version="9.0.21022.8" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC90.MFC"
version="9.0.21022.8" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
</dependentAssembly>
</dependency>
Is this correct?
The new version is "9.0.30729.1".
Has there been any changes in the Runtime, so that it is nessecary to update
existing installations to the new version or could they use the older onces?
When it is nessecary to update how could I switch in VS to the new onces?
Thanks,
Dieter
David Connet
news:#t9j4tR$IHA....@TK2MSFTNGP04.phx.gbl:
I just ran into this too: I've submitted a bug -
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?
FeedbackID=361682
Vote on it!
Dave Connet
David Connet
$vn7...@flpi147.ffdc.sbc.com:
I just found a workaround - edit the .manifest files for the CRT/MFC
(from the redist directory) and make the version number in those be
"9.0.21022.8". I just noticed the files we were using with the Feature
Pack installed had that version, even though the dll has a greater
version number.
Dave
Dieter Pelz
the workaround seemed to not to be the right solution, because the runtime
should be installed in Windows as side by side assembly.
The main question is should I change the manifest to version "9.0.30729.1".
When installing the runtime there are also policy files which switch the
older versions to the new version.
But I wanted to known should I change the manifest to the new version and
therefore what should I do for this change in Visual Studio?
In the modules window in debugger I could see that when SP1 runtime is
installed the new version of the runtime is used, also when both versions
are installed.
When only RTM Runtime is installed this version is used, also with a
programm build with SP1. But when MFCNEXT feature are used there will be
unresolved externals.
I think with MFCNEXT or other CRT functions only in SP1 the manifest shoud
address the new runtime version.
How could I change the embedded manifest to the new version?
Thanks,
Dieter
"David Connet" <st...@agilityrecordbook.com> schrieb im Newsbeitrag
news:K7Jok.21437$N87....@nlpi068.nbdc.sbc.com...
Dieter Pelz
I found the solution for your problem.
You must define
_BIND_TO_CURRENT_VCLIBS_VERSION=1
This will change the manifest to the new Version!
But my main question is currently open:
Should I use this define or are there not enough changes as long I will not
use MFCNEXT, TR1 etc.?
Thanks,
Dieter
"David Connet" <st...@agilityrecordbook.com> schrieb im Newsbeitrag
news:K7Jok.21437$N87....@nlpi068.nbdc.sbc.com...
Jeffrey Tan[MSFT]
I will spend some time on this issue and get back to you ASAP. Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd...@microsoft.com.
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Jeffrey Tan[MSFT]
Sorry for the late response.
After discussing to the VC++ team, they confirmed that, due to customers
request we have changed the way VS2008 binds to the base RTM version
(9.0.210028.8). Way back in VS2005 we used to bind the version to the
latest version installed on the developers machine. If developer had VS2005
SP1 we bind current version to SP1 and this can be verified from manifest.
But now in VS2008 we bind always to RTM version (9.0.210028.8) even if you
have VS2008 SP1 installed, unless explicitly mentioned using bind macros.
You may get more information from the blog entry below:
http://blogs.msdn.com/vcblog/archive/2008/05/15/vc-runtime-binding.aspx
Hope it helps.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
=========================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd...@microsoft.com.
This posting is provided "AS IS" with no warranties, and confers no rights.
Dieter Pelz
this answers my question. Now it's clearer.
Thanks,
Dieter
""Jeffrey Tan[MSFT]"" <je...@online.microsoft.com> schrieb im Newsbeitrag
news:F0Sz51PA...@TK2MSFTNGHUB02.phx.gbl...
Jeffrey Tan[MSFT]
post, thanks.