mfp
-
Microsoft Dynamics AX 2012 - Creating an ISV ModelThis recording shows how an ISV can create a solution in AX 2012, including:
- How to create a new model in AX.
- Why element IDs are not a concern anymore.
- Protecting the solution using a licensing scheme.
- Generating a signed model file for deployment.
- How to generate licenses for customers.
THIS POST IS...
-
Microsoft Dynamics AX 2012 - Uninstalling the Upgrade modelThis short recording shows an alternative use of models. It shows how to get rid of all the development artifacts that only has to do with data upgrade - and once data upgrade is completed, you don't really need them any more!
This way "DEL_" tables , fields and indexes no longer pollutes your...
-
Microsoft Dynamics AX 2012 - Type HierarchiesThis is a sneak preview of two new tools in Microsoft Dynamics AX 2012: The Type Hierarchy Context and the Type Hierarchy Browser.
Please notice that:
- AX 2012 supports table inheritance
- These tools runs off live meta data - no need for cross reference to fuel them
- These tools improves the navigation and...
-
Microsoft Dynamics AX 2012 - X++ EditorHere is a sneak preview of the new X+ Editor in Microsoft Dynamics AX 2012
Notice that the editor now features word-completion, automatic indenting, scripting, zoom, multiline editing, and much much more.
THIS POST IS PROVIDED AS-IS AND CONFERS NO RIGHTS.
-
Microsoft Dynamics AX 2012 - Developer WorkspaceHere is a sneak preview of the Developer Workspace in Microsoft Dynamics AX 2012.
THIS POST IS PROVIDED AS-IS AND CONFERS NO RIGHTS.
-
10 MorphX tricks in 10 minutesThis screencast shows 10 small demos that will make you more efficient as a MorphX / X++ developer.
It turned out to be almost 20 minutes; so you'll have to play it at double speed to see it all in 10 minutes. -
Version control in MorphXThis screencast is a preview of the version control system integration options in the next release of MorphX - the IDE of Dynamics AX.
It shows a side-by-side comparison of the integration options with Team Foundation Server, Visual Source Safe, and MorphX VCS.
The latter is a... -
MorphX Best Practices in Dynamics AXThis screencasts show you how to use the X++ Best Practices inside Dynamics AX to build solid business applications.
It also shows you how you can create your own best practice rules. -
Application Fundamentals in Dynamics AXThe talk covers the most basic frameworks you must know about to be an effective X++ developer:- Dialog
- Operation Progress
- Usage Data
- Runbase
- Batch
-
Exception handling in X++The screencast shows how exceptions handling works in X++ in Microsoft Dynamics AX 4.0, and how exceptions are integrated with the Infolog.
Staff
Here is a list of Channel 9 staff members.
10 MorphX tricks in 10 minutes
Jun 10, 2009 at 5:07 AMCan you let me know the link that fails for you? Can you stream other Channel 9 screencasts?
I've just tried them all; and they do work for me - and by the comments I can see others got it to work too.
10 MorphX tricks in 10 minutes
Jun 10, 2009 at 5:04 AMThe video is available in different resolutions. The best resolution is "Screencast" which is 1280x768 and 2MBPS, here you should be able to read the X++ code.
Here is the direct link:
http://mschnlnine.vo.llnwd.net/d1/ch9/2/4/0/1/7/4/10MorphXTricksIn10minutes_2MB_ch9.wmv
10 MorphX tricks in 10 minutes
Jun 04, 2009 at 2:51 AMThe media issue has been resolved.
Version control in MorphX
Jan 02, 2008 at 1:06 AMIn the AOT you will find the VersionControl class, it has methods like checkin, checkout, undoCheckout. These can be customized like you normally do in MorphX.
The documentation for this class on MSDN will (eventually) be available here:
http://msdn2.microsoft.com/en-us/library/aa843010.aspx
Version control in MorphX
Dec 20, 2007 at 8:25 AMWith regards to multiple check-out nothing new is added in 5.0. VSS in 4.0 already supports this, if you enable it in the VSS Admin tool. The way it works is that the version control backend will automatically attempt to merge the files. In most cases it succeeds and both check-ins succeed. In cases where the exact same lines has been modified the last check-in is rejected. The developer then has to resolve the conflict manually, and check-in again.
Keeping track of versions across installation can be difficult. Even more so if you use XPO files as a way of deploying. I strongly recommend only using AOD files. In combination with a VCS it requires a build step. In the next update of the documentation on MSDN we will release a documentation on how to setup an automated build procedure. Using an AOD file you can stamp each version with a build number, and you can label (VSS term) your VCS files with the build number. Then you know what you got at all times, in every environment.
Regarding IDs, *sigh*, we know. What I can promise is we will address this in the very near future after 5.0. If we don't Microsoft will be out-of-IDs very shortly.