Leaderboard

Back in the early days of LabVIEW, the Separate Compiled Code From Source feature had a lot of quirks (and we discussed them in this old thread). I'm wondering what are people's current feelings and practical experiences with this useful feature. Do you trust it (e.g. to not corrupt your code)? What are the current issues/quirks (e.g. occasional broken VIs)? How do you work around them (e.g. object cache flushing)? Thanks for sharing. I'm working to put together a set of best practices for using this feature and I'd like to know everyone's... well... best practices

I've been told that NI is using the Separate From Compiled for any VI they develop. For Windows only projects, I have never had an issue (working in 2013 and 2014). We had a small hiccup when trying to use the same VI in a project on Windows and cRIO RT. Cleared the object cache once and it was fine again for the rest of the project.

I'm rather fond of applying behaviours en masse via callbacks. Ctrl CB.zip

Here are the VIs we use for Windows authentication and domain groups. Validate Username and Password.vi takes the username and password and returns a TRUE if it validates against the domain controller. User in Group.vi takes a username (or current user if left blank) and a Domain Group name and returns TRUE if the user is a member. User Groups.vi takes a username (or current user if left blank) and returns an array of Domain Groups to which the user belongs. We only use these on our internal network, so I can't guarantee they work in every situation. Still, they may give you a starting point if you need something similar. Pat P.S. LabVIEW 2010sp1 User Groups.vi User in Group.vi Validate Username and Password.vi