This topic describes how existing INtime projects may be upgraded to use a more recent Visual Studio product and its debugger. INtime software continues to support the older Visual Studio products, but the use of newer Visual Studio versions allows you to take advantage of the INtime debugging features of the product and also provides access to more advanced Visual Studio technology.

Upgrading to a newer Visual Studio from VC6 and earlier

When you open an existing project (.dsp or .dsw file for Visual Studio 6.0, or .sln for later Visual Studio versions) in a newer Visual Studio version, you are asked whether you want to upgrade; if you refuse, the workspace is not opened. If you agree, Visual Studio modifies your file set and you now have these files:

The solution file, proj.sln, contains solution properties (a solution is a container for one or more projects). There can be different types of projects, but for INtime we are interested only in the C/C++ project type, which is identified by the file extension .vcproj or vcxproj; a C/C++ project file contains compiler and linker settings.

What if upgrading did not work?

If for any reason upgrading fails, you can proceed as follows:

1. Create a new solution if you wish.
2. In the solution, create a new project; use the INtime projects Application wizard for this, and select an empty project.
3. When the wizard is finished, modify the C/C++ project to suit your needs (add configurations, change compiler and linker settings). Note that you will not be able to modify the platform in the configuration manager; it will always get "INtime".
4. Add project items such as .c and .cpp source files, .h and .hpp include files, and so on.

Converting to a .intp project

A solution may contain more than one project, each of which can be one of many types. In the case of an INtime application, there will be one or more projects that produce an INtime executable or library; we will refer to these as the INtime projects.

When you have upgraded from Visual Studio 6.0 or have created the project as a Windows project, you need to convert the project to an .intp project. If you are not sure if this is necessary, check if the Solution Explorer window in Visual Studio shows the INtime icon for your INtime project; if it does, you can skip this step.

An .intp project encapsulates a C/C++ project and contains properties that are INtime specific; these properties are contained in a file with the .intp extension. When Visual Studio reads an .intp project, it provides access to features specific to INtime projects, which includes the integrated INtime debugger. Before leading you there, let us see how you convert a project.

Converting to a .intp project in Visual Studio .NET and 2005

Open the solution. Load the macros provided by INtime as follows (loading the macro project needs to be done only once):

1. Select Tools>Macros>Load macro project.
2. Navigate to the vstudio (Visual Studio .NET) or vstudio80 (Visual Studio 2005) directory in INtime's installation directory.
3. Open the tointp.vsmacros file.
4. Locate ToIntp in the Macro Explorer window:
   1. Click the plus icon to expand ToIntp.
   2. Click the plus icon to expand Module1.
5. Double-click ToIntp, or click it once and press Enter.

   Progress messages display in the Output window, located at the bottom of Visual Studio. You are then prompted to save files.

6. Click Yes to save files.

Converting to a .intp project in Visual Studio 2008 and 2010

Open the solution. Select the INtime menu, "Convert solution to INtime" menu item.

Progress messages display in the Output window, located at the bottom of Visual Studio. You are then prompted to save files. Click Yes to save files.

You now have a solution with one or more .intp projects identified by an INtime icon; each .intp project contains a C/C++ project. Your set of files now looks like this:

What if the conversion did not work?

The conversion to .intp project makes some assumptions about projects that can be converted to INtime projects:

• Such a project is identified by the Version=21076.20052 option in the Linker/General properties page. Projects that do not have this option are skipped by the conversion.
• There are two configurations, named Debug and Release.
• Compiler and linker options are set to default values applicable for INtime.

There is a second macro ToIntpSelected or "Convert project to INtime" menu item that only converts the selected project.

If for any reason you choose not to use the conversion macro but still want to use the integrated debugger, you can proceed as described above in "What if upgrading did not work?"

Setting project properties

An .intp project has an additional set of options: when you right-click the C/C++ project and select properties, you see the compiler and linker settings, just like before. Right clicking the .intp project and selecting properties shows two pages (there are also menu items to achieve the same results):

• Launch settings, that determine on which INtime node the application will run and what command line arguments are passed to it, and
• INtime settings, which control resources in the INtime system.

The pool maximum parameter on the INtime settings page is the same as the Heap reserve size on the Linker/System page of the VC project properties.

Getting to work with the debugger

All of these steps had to be done only once. From now on you can use the integrated INtime debugger, just like you are used to doing so with Windows applications:

• Press F9 to set a breakpoint on a source line.
• Press F5 (run), Control-F5 (run without debugging), or F10 (single step) to start debugging.
• When at a breakpoint, view threads, variables, registers, call stack, modules, etc.

Note that the integrated debugger will refuse to debug an INtime RSL you must select a project that represents a .RTA file.