I started working on Real-Time systems prior to having the project. It was a hassle to switch between Windows and LabVIEW Real-Time instances especially when developing and debugging communication code.
When the project came along it was natural to have the host PC and Real-Time target in the same project for editing either application and common libraries used on each target. Classes are favorable, but the fact you can't edit them when you have instances of a class in target and host such as a communication class is not excusable in my mind. Having to split a target and host into two separate projects goes against the best practices and marketing NI has done for quite some time.
Being able to put both the Real-Time controller and Windows UI in the same project was nice while it lasted, but once again we are back to having to have separate project spaces for our UI and Real-time controller if I take your advice as it stands. The only way I have found to work around this it to create a project just to edit my class that is shared between the targets (silly for a simple update such as changing a data type), close that project, and then resume editing in my Host/Target project.
Are there any other platforms out there that don't allow you to share common classes between target and host? Mathworks and their partners seem to integrate target and host reasonably well. I'm not sure about Speedgoat. In short, this is an issue where NI needs to step up and be competitive with ease of development.
