title: Migration from .NET framework 2.0 to 4.5.2
body: <p>We have an application with around 300+ components (dll's and a couple of exe's). Some of them target 4.0 framework, some use 2.0 framework, some are written in native C++ (unmanged), some uses C++/CLI and a couple of them are written in ManagedExtensions for C++.</p>
  
  <p>Now our requirement is to migrate to .NET Framework 4.5.2.</p>
  
  <p>So my question is:</p>
  
  <p>Will it be OK if I just change the TargetFramework version on all the exe's to 4.5.2 with out changing the dll's TargetFramework version?</p>
  
  <p>Does it guarantee that all my dll's are loaded and run in 4.5.2 runtime? (Included all the C++ dll's).</p>
  
  <p>I have gone through multiple articles on internet and I could not find a concrete answer in the scenario where we have a mix of C#, managed c++ and unmanaged c++ dlls. Any help is appreciated.</p>
  
  <p>Edit: Our team generate core libraries (sort of a framework) and few executables (targetted to 2.0 framework) which can be used by various other teams to meet their customer specific requirements. Some of the customers are not yet migrated from XP (Max .NET framework used in XP is 4.0). So along with newer OS's we still need to support clients using XP.</p>