DEPLOY A .NET APPLICATION DIRECTLY OVER KITL
As an alternative, the OS project’s release directory can be set as the build target for the managed code application. This would allow some further development because the application is not part of the image but can be run from the Target Control Window and the Run Programs dialog. This works because .NET applications only need to be copied to a target system and also because the release directory is exposed to the running OS if it is configured as previous. The managed source code can’t be stepped through though, as Platform Builder supports debugging of only native code. Also, the application would need to reference any resources its uses from the \Release directory.
This approach can avoid the need for a second instance of Visual Studio. The project can be added to the Solution of which the OS is a part, not as a subproject of the OS but as a subproject of the solution. It can then be built independent from the OS by right-clicking it in Solution Explorer.
Building to the Release Directory
This activity uses the same Serial Port Project. It will build directly to the Release directory where it can be run from the OS.
1. Shut the OS down.
2. The OS needs to be configured for KITL debugging as outlined in the native code debugging section of this chapter.
3. Uncheck the Serial program from the Catalog.
4. Perform a clean build of the OS.
5. You need to get rid of the subproject files from the image and release directory.
6. Run the ...