title: Maintaining a Statically Linked MFC Project vs Dynamically Linked
body: <p>I have a project that targets legacy systems (XP/2000 being the earliest), maintained in Visual Studio 2019, that currently uses dynamically linked libraries.</p>
  <p>When installing on other systems I have to install the VC++ redistributable on those systems before the program will function. One solution to this problem I found was to statically link the files so that they are contained within the executable.</p>
  <p>I looked at setting prerequisites in the setup project, but these require access to an internet connection which is often not the case for my software's users.</p>
  <p>First, is this a reasonable response to this issue?</p>
  <p>Second, is maintaining a statically linked project different than maintaining a dynamically linked project, say when the compiler updates or Visual Studio comes out with a new version/toolset?</p>