As I'm preparing for my presentation at ALVIN tomorrow it occurred to me that there was one aspect of this discussion about Environment VIs vs Project VIs that could be improved quite easily.
So just to clarify.
Most if not all of the VIs in these directories can be edited or replaced. This will potentially cause changes across all of your projects on this machine and undo these changes when you load your project on a new machine. This somewhat makes a mockery of source code control.
I think it would be good to have some warning of this. Something akin to the following dialog box would work.
Personally I would go further and move the affected VI into the project directory, but this at least explains the ramifications rather than silently causing chaos in your code-base.
I think we're getting close to having this idea thrashed out now.
Here's where I'm staying for the week (I'm a lucky lad really)
Lots of Love
Steve
Steve
Opportunity to learn from experienced developers / entrepeneurs (Fab,Joerg and Brian amongst them):
DSH Pragmatic Software Development Workshop
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.