Since Graphics Mill for .NET 5.0 was released, we have received a number of emails from our customers who get the following error whenever run an application which uses Graphics Mill for .NET 5.0.



Eliminating this problem on the development computer

To eliminate this problem you should install the Microsoft Visual C++ 2005 SP1 Redistributable Package on your development computer before using Graphics Mill for .NET 5.0. You can download this package from Microsoft site:

Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)

Microsoft Visual C++ 2005 SP1 Redistributable Package (x64)

Eliminating this problem on the target computer

If you are going to distribute your application which uses Graphics Mill for .NET 5.0 to computers where it is not guaranteed that Visual C++ 2005 is installed, you should redistribute Visual C++ DLLs along with your application. There are three ways to redistribute Visual C++ DLLs with your application:

1. Use Visual C++ Redistributable Merge Modules to install a particular Visual C++ library as shared side-by-side assemblies into the native assembly cache (WinSxS folder). This is the primary recommended way for redistributing Visual C++ libraries. Access to this folder requires that the installer application be run by a user with administrative rights.
   
   
2. Use Visual C++ 2005 SP1 Redistributable Package to install all Visual C++ libraries as shared side-by-side assemblies into the native assembly cache (WinSxS folder). This package can be downloaded from the Microsoft download site using links above. To deploy Visual C++ libraries by using Visual C++ 2005 SP1 Redistributable Package, perform the following steps:
   
   
   1. Create a folder structure on the development computer that matches the folder structure to be used on the target computer.
      
   2. Copy this folder to the target computer.
      
   3. Copy Visual C++ 2005 SP1 Redistributable Package to the target computer.
      
   4. Run VCRedist_x86.exe (or VCRedist_x64.exe) on the target computer.
      
   
   
3. Install a particular Visual C++ DLLs as a private assemblies for the application using files provided in the c:\Windows\WinSxS directory. This way is recommended to enable installation of applications by users who do not have administrative rights or when it should be possible to run an application from a share. To deploy Visual C++ DLLs as private assemblies, perform the following steps:
   
   
   1. Create a folder structure on the development computer that matches the folder structure to be used on the target computer.
      
   2. On your development machine open c:\Windows\WinSxS folder and copy the following folders to the folder containing binary assemblies in your application:
      x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_[…];
      x86_Microsoft.VC80.OpenMP_1fc8b3b9a1e18e3b_8.0.50727.762_[…].
      
   3. Rename folders copied in the previous step:
      x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_[…] to Microsoft.VC80.CRT;
      x86_Microsoft.VC80.OpenMP_1fc8b3b9a1e18e3b_8.0.50727.762_[…] to Microsoft.VC80.OpenMP.
      
   4. Open c:\Windows\WinSxS\Manifests folder on your development machine, take the following files:
      x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_[…].manifest
      x86_Microsoft.VC80.OpenMP_1fc8b3b9a1e18e3b_8.0.50727.762_[…].manifest,
      and copy them to Microsoft.VC80.CRT and Microsoft.VC80.OpenMP folders, accordingly.
      
   5. Rename the files copied in the previous step:
      x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_[…].manifest file to Microsoft.VC80.CRT.manifest
      x86_Microsoft.VC80.OpenMP_1fc8b3b9a1e18e3b_8.0.50727.762_[…].manifest file to Microsoft.VC80.OpenMP.manifest.
      
   6. After that make installation package included the files and folders prepared above and redistribute it.
      

Note:

• Make sure that you copy folders with dlls and manifests of .762 version (this version should be in the name of folders and manifest files).
  
• If you use x64 system you should copy the same folders and manifests with the difference that their names are started with x64_[...]

See the Choosing a Deployment Method topic for details.

---

Best regards,
Tatyana Bertyakova

Have Sp1 installed and also latest update for Sp1 and still get this message. Using a spanish Visual Studio 2005 edition and service packs.
Can run the compiled demos as distributed by you but not the sample projects from Visual Studio IDE.
Thanks in advance.

Solved now, thanks. Really outstanding support even on evaluation.

Hello,



Yes, you need to install it.

---

Sincerely yours,
Dmitry Sevostjanov.