google chrome pdf plugin not working ppapi out-of-process

You can compile, start, and debug your code with one click or key-press. Using platforms, your workflow is faster and more efficient. The diagram below shows the platforms, the ways they are normally used, and the build products they produce. The other group, which we’ll call the Native Client platforms, contains platforms that all have “NaCl” in their names: NaCl32, NaCl64, NaClARM, and PNaCl. It is helpful to consider the Visual Studio add-in platforms in two groups. The platforms also define the behavior associated with the debug command so you can test your code while running in Visual Studio. The platforms configure the properties of your project so it can be built and run as either a Pepper plugin or a Native Client module. These platforms can be applied to the debug configuration of solutions and projects. The add-in defines five new Visual Studio platforms: PPAPI, NaCl32, NaCl64, NaClARM, and PNaCl. Use the Native Client debugger, nacl-gdb, to test your code when it’s running as a Native Client object.pexe file using the Native Client SDK tools and run it as a bona fide Native Client module. Use Visual Studio’s built-in debugger to debug your code while it’s running as a Pepper plugin.This allows you to develop code incrementally, coding and/or porting one feature at a time into the Pepper APIs while continuing to use native Windows APIs that would otherwise be unavailable in an actual Native Client module. Compile your module into a dynamically-linked library (DLL) using Visual Studio’s C/C++ compiler and run it as a Pepper plugin.

Visual Studio handles the details of launching a web server to serve your module and run the module in Chrome with a debugger attached.

Iteratively write and test your application more easily.

Organize and maintain your code as a Visual Studio project.

The Native Client add-in for Visual Studio helps you develop your application more efficiently in many ways:

Visual Studio Express is also not supported. No other versions of Visual Studio are currently supported. The Native Client add-in requires Visual Studio 2012 or Visual Studio 2010 with Service Pack 1. Whether you’re porting an existing project or starting from scratch, the Native Client Visual Studio add-in makes it easier to set up, build, run and debug your Native Client app by integrating the Native Client SDK development tools into the Visual Studio environment. Porting Windows applications to Native Client in Visual Studio.Developing for Native Client in Visual Studio

Google chrome pdf plugin not working ppapi out-of-process