The publishing schedule for these articles are as follows:
| Published Date | Featured Article |
|---|---|
| 05/09/2011 | Microsoft Dynamics GP "12" Web Client Architecture - Part 1 |
| 05/11/2011 | Microsoft Dynamics GP "12" Web Client Architecture - Part 2 |
| 05/16/2011 | Microsoft Dynamics GP "12" Web Client Architecture - Part 3 |
| 05/23/2011 | Microsoft Dynamics GP "12" Named System Database Architecture |
Disclaimer: Some images and content reproduced with express permission from Microsoft Business Solutions, a division of Microsoft Corporation. The content of these articles should not be reproduced without permission from this author.
Until next post!
MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/
Edits:
05/23/2011 - Added link to Named System Database Architecture article on Dynamics Community.
7 comments:
Great info Mariano - can't wait for parts 2 and 3!
Thanks Aaron! Working on it!
MG.-
Mariano Gomez, MVP
Thank you so much for explaining how the it is going to work. I was wondering how the cusomisations were going to come through to the webclient.
Can't wait to have a try.
Hi Mariano, please i really need your good advise, i am going to develop a big application that works with Dynamics GP purchasing, sales, inventory and financials modules, this is going to take about 6 months, so my doubt is, the next version of GP is really going to be web? like CRM, should I make my app like a Web Client, or i can still using VST to make a windows app inside GP. I really appreciate your help. thanks a lot
Fernando,
The Dexterity client is still going to be around, so your VST customizations should work just fine. I can't provide any further insight into the web client and custumizing it, because I simply don't have any more details.
MG.-
Hello Mariano, and thank you for the informative articles. I have two small questions which I am hoping you can answer:
1. It looks like the web interface exactly reflects all GUI elements between windows and web versions. In other words the two versions of the Client Interface can not contain different set of controls and if you wish to add new fields you have to add it to the windows version first and then it generates the Web version in Silverlight for you automatically. Is that correct or am I reading it wrong?
2. It appears that the actual business logic will remain in Dexterity since both Client GUIs use the same Template Processor which executes the same logic block. So in order to customize GP 12 a Developer has to learn Dexterity even in this new system and can not custom code it in c# / .net. Is that correct?
3. Lastly, is there any way currently for existing GP Customers and/or MSDN Subscribers to try out a beta version of GP 12?
Thanks,
Pete
1. That's correct. The UI customizations reside on the Dex client and are rendered in Silverlight, so from that perspective, both interfaces cannot have different sets of controls.
2. Yes and No. Clearly, Dex knowledge will be fundamental, but there's a lot of code written in VST (and VBA, if you consider Modifier) as well, and I have to believe MS will find a way to make that code work with Silverlight. In summary, it will be probably a good thing to pick up some Dex skills, just perhaps as much as it will be important to learn some Silverlight (at least from a concept point of view).
3. Not that I know of or I would've already had a copy :-)
MG.-
Post a Comment