Thanks Archie.
Okay, so maybe I'll just keep writing my HMI in my own solution and then import the files into the AdvancedHMI at a later time when the newer version is posted. What about the Solution name? Am I to assume there's a bunch of steps in renaming the solution? Also, I want to better understand the AdvancedHMI solution and the benefits that it may give me. I know it has the standard HMI controls with the buttons, indicators, meters, etc. But if I don't plan on using any of that, are there any benefits to me using the AdvancedHMI solution for my TwinCAT project? Am I understanding it correctly in stating that the AdvancedHMI solution is TwinCAT ready as far as communications drivers, etc for my project (once the new TC drivers are up to date)? If that is true, then yes I will plan on using it as its ready to go and less headaches for me trying to establish comms between the TC PLC project and VS HMI project.