I've finally got a web sample of mine configured to at least navigate using ther UIPAB.
The next challenge is to figure out how to take care of traditional forms control operations. Do we try to include all these methods in the controller class?? or do we continue to call them in the code behind?
Seems like most of the samples from MS are one task, one screen type architecture, whereas in the real world, the ASP.NET screen does a lot of work simply posting back to itself.....trying to grasp this new paradigm.
Any ideas, thoughts, or grotesque noises??
Harry