VS2005 SP1 Hell

Visual Studio C++ >> VS2005 SP1 Hell

We upgraded to VS2005 SP1 and of course our code doesn't run now :-) We get
the "app config is incorrect, etc.".

Anyway, I think its because its not loading the right runtime libraries.
So, we've updated our installation so that the SP1 runtime libraries get put
in our app directory now. Problem is, its still loading the libraries from
the SxS storage area.

We really don't want to force every user to go run some other MS runtime
install kit to be able to run our SW.

So... the question is, how do we force our app to load the runtime libs from
the app directory?

This used to be a simple matter of putting all the right DLLs in your app
directory.

Whats the easiest way to do this?

Visual Studio44

Visual Studio C++ >> VS2005 SP1 Hell

> This used to be a simple matter of putting all the right DLLs in your app
> directory.
>
> Whats the easiest way to do this?

Static linking looks better every day :).

--
David Wilkinson
Visual C++ MVP

Visual Studio C++ >> VS2005 SP1 Hell Good point :-) Although we use third party libraries which themselves do
not statically link (which we've updated with SP1 builds of course) so going
static linking probably isn't an option.

Dave

>
>> This used to be a simple matter of putting all the right DLLs in your app
>> directory.
>>
>> Whats the easiest way to do this?
>
> Static linking looks better every day :).
>
> --
> David Wilkinson
> Visual C++ MVP

Visual Studio C++ >> VS2005 SP1 Hell

> We upgraded to VS2005 SP1 and of course our code doesn't run now :-) We
> get the "app config is incorrect, etc.".
>
> Anyway, I think its because its not loading the right runtime libraries.
> So, we've updated our installation so that the SP1 runtime libraries get
> put in our app directory now. Problem is, its still loading the libraries
> from the SxS storage area.
>
> We really don't want to force every user to go run some other MS runtime
> install kit to be able to run our SW.
>
> So... the question is, how do we force our app to load the runtime libs
> from the app directory?
>

Have you tried turning off the manifest?

> This used to be a simple matter of putting all the right DLLs in your app
> directory.
>
> Whats the easiest way to do this?
>
>

Visual Studio C++ >> VS2005 SP1 Hell

> We upgraded to VS2005 SP1 and of course our code doesn't run now :-) We get
> the "app config is incorrect, etc.".
>
> Anyway, I think its because its not loading the right runtime libraries.
> So, we've updated our installation so that the SP1 runtime libraries get put
> in our app directory now. Problem is, its still loading the libraries from
> the SxS storage area.
>
> We really don't want to force every user to go run some other MS runtime
> install kit to be able to run our SW.
>
> So... the question is, how do we force our app to load the runtime libs from
> the app directory?

Well, simply install the new VS2005 SP1 CRT in the SXS folder as part
of your setup. The SP1 comes with a MSM that is just there for that
(and with an exe that you can use if your setup is not MSI-based).

How did you distribute the VS2005 gold CRT before upgrading to SP1?
Just do the same thing!

Arnaud
MVP - VC

Visual Studio C++ >> VS2005 SP1 Hell

>> We upgraded to VS2005 SP1 and of course our code doesn't run now :-) We
>> get
>> the "app config is incorrect, etc.".
>>
>> Anyway, I think its because its not loading the right runtime libraries.
>> So, we've updated our installation so that the SP1 runtime libraries get
>> put
>> in our app directory now. Problem is, its still loading the libraries
>> from
>> the SxS storage area.
>>
>> We really don't want to force every user to go run some other MS runtime
>> install kit to be able to run our SW.
>>
>> So... the question is, how do we force our app to load the runtime libs
>> from
>> the app directory?
>
> Well, simply install the new VS2005 SP1 CRT in the SXS folder as part
> of your setup. The SP1 comes with a MSM that is just there for that
> (and with an exe that you can use if your setup is not MSI-based).
>
> How did you distribute the VS2005 gold CRT before upgrading to SP1?
> Just do the same thing!

VS2005 gold CRT is included in the .NET Framework 2.0, which is pushed by
Windows Update.

Microsoft needs to make the SP1 CRT appear in Windows Update as an optional
download.

>
> Arnaud
> MVP - VC
>

Visual Studio C++ >> VS2005 SP1 Hell Hi Dave,
Since you do not want to load libraries from SxS folder, I recommend that
you refer to the section "Deploying Visual C++ library DLLs as private
assemblies" of this article:
How to: Deploy using XCopy
http://msdn2.microsoft.com/en-us/library/ms235291(VS.80).aspx

For more background knowledge, you may refer to this article:
Choosing a Deployment Method
http://msdn2.microsoft.com/en-us/library/ms235316(VS.80).aspx

Hope this helps. If you have any other questions or concerns, please feel
free to let us know.

Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications

If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.

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.
======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

Visual Studio C++ >> VS2005 SP1 Hell No, distributing Microsoft's runtime installer (vcredist_x86.exe) with the
app and having that run and install stuff to the user's system folders is a
bad idea in general, because doing so requires admin priveleges. As it is
now and has been, our users can install our SW without admin which is a huge
plus for us.

What we had done previously was to just copy the MFC and CRT DLLs along with
their manifest files into our app directory and it worked.

Anyway, we followed the info in the MS link for deploying with private
assemblies and after that and some monkeying around with a library we use
its all working again.

Thankfully so as this is a much cleaner setup than forcing your users to run
some other runtime installer which puts stuff in their system folders. At
least that was our opinion of it.

>> We upgraded to VS2005 SP1 and of course our code doesn't run now :-) We
>> get
>> the "app config is incorrect, etc.".
>>
>> Anyway, I think its because its not loading the right runtime libraries.
>> So, we've updated our installation so that the SP1 runtime libraries get
>> put
>> in our app directory now. Problem is, its still loading the libraries
>> from
>> the SxS storage area.
>>
>> We really don't want to force every user to go run some other MS runtime
>> install kit to be able to run our SW.
>>
>> So... the question is, how do we force our app to load the runtime libs
>> from
>> the app directory?
>
> Well, simply install the new VS2005 SP1 CRT in the SXS folder as part
> of your setup. The SP1 comes with a MSM that is just there for that
> (and with an exe that you can use if your setup is not MSI-based).
>
> How did you distribute the VS2005 gold CRT before upgrading to SP1?
> Just do the same thing!
>
> Arnaud
> MVP - VC
>

Visual Studio C++ >> VS2005 SP1 Hell Even if MS provided it as an OS update, it would for us still be preferable
to provide the private assemblies with our app install. Who knows whether
or not they have (or are allowed to) run that particular update on every
machine which would be using our install? That just seems to fragile and
error prone. We need to be able to just install the app without admin privs
on any machine and not worry about coupled OS updates.

>

>>> We upgraded to VS2005 SP1 and of course our code doesn't run now :-) We
>>> get
>>> the "app config is incorrect, etc.".
>>>
>>> Anyway, I think its because its not loading the right runtime libraries.
>>> So, we've updated our installation so that the SP1 runtime libraries get
>>> put
>>> in our app directory now. Problem is, its still loading the libraries
>>> from
>>> the SxS storage area.
>>>
>>> We really don't want to force every user to go run some other MS runtime
>>> install kit to be able to run our SW.
>>>
>>> So... the question is, how do we force our app to load the runtime libs
>>> from
>>> the app directory?
>>
>> Well, simply install the new VS2005 SP1 CRT in the SXS folder as part
>> of your setup. The SP1 comes with a MSM that is just there for that
>> (and with an exe that you can use if your setup is not MSI-based).
>>
>> How did you distribute the VS2005 gold CRT before upgrading to SP1?
>> Just do the same thing!
>
> VS2005 gold CRT is included in the .NET Framework 2.0, which is pushed by
> Windows Update.
>
> Microsoft needs to make the SP1 CRT appear in Windows Update as an
> optional download.
>
>>
>> Arnaud
>> MVP - VC
>>
>
>

Visual Studio C++ >> VS2005 SP1 Hell We were able to get it working and so thankfully are able to move forward
without needing to invoke the runtime installer as part of our installer.

The below MS link covering deploying with private assemblies did the trick.

http://msdn2.microsoft.com/en-us/library/ms235291(VS.80).aspx

Also, even with the above we still had issues because one of our libraries
contained an embedded manifest which specified the pre-SP1 runtime libs.

Anyway, everything is working now and so I guess we're out of "SP1 Hell"
finally :-)

Thanks for all the replies!

> We upgraded to VS2005 SP1 and of course our code doesn't run now :-) We
> get the "app config is incorrect, etc.".
>
> Anyway, I think its because its not loading the right runtime libraries.
> So, we've updated our installation so that the SP1 runtime libraries get
> put in our app directory now. Problem is, its still loading the libraries
> from the SxS storage area.
>
> We really don't want to force every user to go run some other MS runtime
> install kit to be able to run our SW.
>
> So... the question is, how do we force our app to load the runtime libs
> from the app directory?
>
> This used to be a simple matter of putting all the right DLLs in your app
> directory.
>
> Whats the easiest way to do this?
>
>

Visual Studio C++ >> VS2005 SP1 Hell Hi Dave,
Thanks for your updating and response.

I am glad to hear that the suggestions are helpful. For the issue of the
embeded manifest which specified the pre-SP1 runtime libs, if it has not
been resolved, I recommend that you open up a new post in the community so
that we can track it and provide support in a more efficient manner.

If you have any other questions or concerns, please feel free to let me
know.

Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications

If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.

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.
======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================