Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 47455
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 10, 20262026-05-10T16:07:32+00:00 2026-05-10T16:07:32+00:00

Since VS 2005, I see that it is not possible to simply build a

  • 0

Since VS 2005, I see that it is not possible to simply build a dll against MS runtime and deploy them together (http://www.ddj.com/windows/184406482). I am deeply confused by manifest, SxS and co: MSDN documentation is really poor, with circular references; specially since I am more a Unix guy, I find all those uninformative. My core problem is linking a dll against msvc9 or msvc8: since those runtime are not redistributable, what are the steps to link and deploy such a dll ? In particular, how are the manifest generated (I don’t want mt.exe, I want something which is portable across compilers), how are they embedded, used ? What does Side by side assembly mean ?

Basically, where can I find any kind of specification instead of MS jargon ?

Thank you to everyone who answered, this was really helpful,

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. 2026-05-10T16:07:32+00:00Added an answer on May 10, 2026 at 4:07 pm

    We use a simple include file in all our applications & DLL’s, vcmanifest.h, then set all projects to embedded the manifest file.

    vcmanifest.h

    /*----------------------------------------------------------------------------*/  #if _MSC_VER >= 1400  /*----------------------------------------------------------------------------*/  #pragma message ( 'Setting up manifest...' )  /*----------------------------------------------------------------------------*/  #ifndef _CRT_ASSEMBLY_VERSION #include <crtassem.h> #endif   /*----------------------------------------------------------------------------*/  #ifdef WIN64     #pragma message ( 'processorArchitecture=amd64' )     #define MF_PROCESSORARCHITECTURE 'amd64' #else     #pragma message ( 'processorArchitecture=x86' )     #define MF_PROCESSORARCHITECTURE 'x86' #endif   /*----------------------------------------------------------------------------*/  #pragma message ( 'Microsoft.Windows.Common-Controls=6.0.0.0')  #pragma comment ( linker,'/manifestdependency:\'type='win32' ' \                   'name='Microsoft.Windows.Common-Controls' ' \                   'version='6.0.0.0' ' \                   'processorArchitecture='' MF_PROCESSORARCHITECTURE '' ' \                   'publicKeyToken='6595b64144ccf1df'\'' )  /*----------------------------------------------------------------------------*/  #ifdef _DEBUG     #pragma message ( __LIBRARIES_ASSEMBLY_NAME_PREFIX '.DebugCRT=' _CRT_ASSEMBLY_VERSION )      #pragma comment(linker,'/manifestdependency:\'type='win32' '            \             'name='' __LIBRARIES_ASSEMBLY_NAME_PREFIX '.DebugCRT' '         \             'version='' _CRT_ASSEMBLY_VERSION '' '                          \             'processorArchitecture='' MF_PROCESSORARCHITECTURE '' '         \             'publicKeyToken='' _VC_ASSEMBLY_PUBLICKEYTOKEN ''\'') #else     #pragma message ( __LIBRARIES_ASSEMBLY_NAME_PREFIX '.CRT=' _CRT_ASSEMBLY_VERSION )      #pragma comment(linker,'/manifestdependency:\'type='win32' '            \             'name='' __LIBRARIES_ASSEMBLY_NAME_PREFIX '.CRT' '              \             'version='' _CRT_ASSEMBLY_VERSION '' '                          \             'processorArchitecture='' MF_PROCESSORARCHITECTURE '' '         \             'publicKeyToken='' _VC_ASSEMBLY_PUBLICKEYTOKEN ''\'') #endif  /*----------------------------------------------------------------------------*/  #ifdef _MFC_ASSEMBLY_VERSION     #ifdef _DEBUG         #pragma message ( __LIBRARIES_ASSEMBLY_NAME_PREFIX '.MFC=' _CRT_ASSEMBLY_VERSION )          #pragma comment(linker,'/manifestdependency:\'type='win32' '            \                 'name='' __LIBRARIES_ASSEMBLY_NAME_PREFIX '.MFC' '              \                 'version='' _MFC_ASSEMBLY_VERSION '' '                          \                 'processorArchitecture='' MF_PROCESSORARCHITECTURE '' '         \                 'publicKeyToken='' _VC_ASSEMBLY_PUBLICKEYTOKEN ''\'')     #else         #pragma message ( __LIBRARIES_ASSEMBLY_NAME_PREFIX '.MFC=' _CRT_ASSEMBLY_VERSION )          #pragma comment(linker,'/manifestdependency:\'type='win32' '            \                 'name='' __LIBRARIES_ASSEMBLY_NAME_PREFIX '.MFC' '              \                 'version='' _MFC_ASSEMBLY_VERSION '' '                          \                 'processorArchitecture='' MF_PROCESSORARCHITECTURE '' '         \                 'publicKeyToken='' _VC_ASSEMBLY_PUBLICKEYTOKEN ''\'')     #endif #endif /* _MFC_ASSEMBLY_VERSION */  /*----------------------------------------------------------------------------*/  #endif /* _MSC_VER */  /*----------------------------------------------------------------------------*/ 
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I've searched for this info and see similar questions, but not one that matches
I'm trying to build a C/C++ static library using visual studio 2005. Since the
i have a trigger running against a table that does not return a results
Since 2005, when Microsoft prevented HtmlHelp functioning off a network share, e.g.: \\appserver\tos\PointScanner.exe \\appserver\tos\PointScanner.chm
I have been an avid TFS user since 2005 but decided to skip the
Since regular jQuery animations are not fluent on iOS ( .hide() , slideDown() ),
Since REST is stateless, each request that comes in has no knowledge of the
Try the following on MSSQL 2005: select convert(char(2), 123) The key here is that
I can see that there was a lot of issues with this error message
Javascript 1.6 has been available since 2005 (in FF 2.0). Since then we have

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.