Please allow me to assist you with the list of your problems.

I'm a dumb newb but only the videos (not the written material) show how to resolve references etc.

You can refer to the tutorial video at http://www.intersoftpt.com/Support/ClientUI/Tutorial/Video/Create-Your-First-ClientUI-Application-Using-MVVM-Pattern-Part-I-Preparing-Project/ and http://www.intersoftpt.com/Support/ClientUI/Tutorial/Video/Create-Your-First-ClientUI-Application-Using-MVVM-Pattern-Part-II-Implementation/. The written material is available in http://www.intersoftpt.com/Support/ClientUI/Documentation/WalkthroughCreateYourFirstClientUIApplication.html.

I followed the step-by-step shown in the written material link and managed to create a running simple project as described in the walkthrough topic. Should you need to test my project on your end, please kindly let me know.

No matter how many times I copy, or cut and paste the code I am ending up with a Cannot Create an instance of “ContactListViewModel” error.

I’m willing to advise you further but in order to do so could you please let us know where you are getting the error, is it in xaml or during compilation?

I tried the forums but there does not seem to be any ability to search the forums for text (vis a vis scrolling through every post)

We have a plan to enhance the community (forum) site. In the roadmap of the enhancement, the ability of searching is included.

Your Live Chat help system launches a window that advises you to wait before disconnecting after about 5 mins.

Thank you for your valuable feedback. We will check whether the disconnecting problem is caused by the connection or the code of the live chat feature.

Calling your support number gives me a receptionist who transfers my call to a scratchy connection (overseas??) that rings then gives a busy signal and then disconnects the call.

Terribly apologize for all the inconveniences. I will surely investigate about our phone line problem to serve you the best.

Thanks, I created the project and cut and pasted the code again and have a working app -- though for us complete noobs there imho should be at the end of the guides instruction on how to add the component to the UXPage1.xaml.  Another question though is:

The Intersoft ClientUI tools in the VS2010 panel do not appear in alphabetical order and have some listed as UX___ and some just as the component name.  What are the differences and why do they appear in the order they do (i.e. it makes finding the right control difficult at times).

Also fyi the back button for your site seems to be broken for Firefox 4 (but not for IE9 or Chrome).  To replicate open FF4 and goto:

http://www.intersoftpt.com/Support/ClientUI/Documentation/ClientUIControls.html  then click any link such as

http://www.intersoftpt.com/Support/ClientUI/Documentation/ClientUIControls.html#url=ControlsbyAlphabet.html then click back button.

Glad to hear that you have managed to get the sample working.

The reason why does the ClientUI controls not appear in alphabetical order is: because the controls were added or installed into Visual Studio 2010 toolbox based on its assembly sort order. For example: UXAutoFitDockPanel; UXAutoFitStackPanel; UXButton; and so on are located on the upper side of Visual Studio 2010 toolbox because those controls are using Intersoft.Client.UI.Aqua assembly.

To have a better description, please try to check “Controls by Assembly” topic in ClientUI documentation (the online version is available in: http://www.intersoftpt.com/Support/ClientUI/Documentation/#url=ControlsbyAssembly.html).

Please allow me to explain the difference between controls that has UX prefix and controls that doesn’t. Here in this sample I will compare CallOut control and UXCallOut control. CallOut is a simple content control featuring highly customizable callout shape rendering. CallOut is inherited from ISContentControl, which means that it can contain a single object of any types, such as string, an image, or a panel.

UXCallOut is an interactive popup control in a form of CallOut which can be used to represent the content inside the callout as well as the content of the control itself. UXCallOut derives from ISHeaderedContentControl, which means that it is using headered content presentation model. UXCallOut uses UXPopup control to display content which stays on the top of other elements along with comprehensive hide and display animation.

Thank you for your valuable feedback about the back navigation in Mozilla Firefox 4 that is not working in the online version of ClientUI documentation. I have forwarded this to our team to be investigated further.

Hope this helps.