- [Automation Servers](../mfc/automation-servers.md)

Migrate VC++ directories settings from a .vssettings file that is created by an earlier release of Visual C++. Open the **Tools** menu, click **Import and Export Settings**, select **Import selected environment settings**, and then follow the directions in the wizard. Or when you start Visual Studio for the first time, on the **Choose Default Environment Settings** dialog box, select **Migrate my eligible settings from a previous version and apply them in addition to the default settings selected below**.

When you build your native C/C++ application using Visual C++, by default the Visual Studio project system generates a manifest file that describes your application's dependencies on Visual C++ libraries. If these are the only dependencies your application has, then it becomes an isolated application as soon as it is rebuilt with Visual Studio. If your application is using other libraries at runtime, then you may need to rebuild those libraries as side-by-side assemblies following the steps described in [Building C/C++ Side-by-side Assemblies](../build/building-c-cpp-side-by-side-assemblies.md).

[Concepts of Isolated Applications and Side-by-side Assemblies](../build/concepts-of-isolated-applications-and-side-by-side-assemblies.md)<br/>

This change may allow deployment of corresponding DLLs as a [private assembly](/windows/desktop/Msi/private-assemblies) in an application local folder or as a [shared assembly](/windows/desktop/Msi/shared-assemblies) in the WinSxS assembly cache. Several steps have to be followed in order to achieve correct runtime behavior of this new assembly; they are described in [Guidelines for Creating Side-by-side Assemblies](/windows/desktop/SbsCs/guidelines-for-creating-side-by-side-assemblies). After an assembly is correctly authored it can deployed as either a shared or private assembly together with an application that depends on it. When installing side-by-side assemblies as a shared assembly, you may either follow the guidelines outlined in [Installing Win32 Assemblies for Side-by-Side Sharing on Windows XP](/windows/desktop/Msi/installing-win32-assemblies-for-side-by-side-sharing-on-windows-xp) or use [merge modules](/windows/desktop/msi/merge-modules). When installing side-by-side assemblies as a private assembly, you may just copy the corresponding DLL, resources and assembly manifest as part of the installation process to the application local folder on the target computer, ensuring that this assembly can be found by the loader at runtime (see [Assembly Searching Sequence](/windows/desktop/SbsCs/assembly-searching-sequence)). Another way is to use [Windows Installer](/windows/desktop/Msi/windows-installer-portal) and follow the guidelines outlined in [Installing Win32 Assemblies for the Private Use of an Application on Windows XP](/windows/desktop/Msi/installing-win32-assemblies-for-the-private-use-of-an-application-on-windows-xp).

[Deployment Examples](../ide/deployment-examples.md)<br/>

[Building C/C++ Isolated Applications](../build/building-c-cpp-isolated-applications.md)<br/>

- [Decorated names](../build/reference/decorated-names.md)

[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)

|C++ Compiler|**CXX**|cl|**CXXFLAGS**|

|Resource Compiler|**RC**|rc|**RFLAGS**|

|**-**\[*number*] *command*|Turns off error checking for *command*. By default, NMAKE halts when a command returns a nonzero exit code. If -*number* is used, NMAKE stops if the exit code exceeds *number*. Spaces or tabs cannot appear between the dash and *number.* At least one space or tab must appear between `number` and *command*. Use /I to turn off error checking for the entire makefile; use **.IGNORE** to turn off error checking for part of the makefile.|

|**!** *command*|Executes *command* for each dependent file if *command* uses <strong>$\*\*</strong> (all dependent files in the dependency) or **$?** (all dependent files in the dependency with a later timestamp than the target).|

[Commands in a Makefile](../build/commands-in-a-makefile.md)

[Inline files in a makefile](../build/inline-files-in-a-makefile.md)