Something that was talked about for a long time is getting closer to reality. F&O development will no longer require those huge VMs with SQL Server and everything. Instead, you’ll just install some VS extensions, connect to Dataverse, download F&O code and metadata and start developing. The runtime (web server, database) will be in cloud, …
Continue reading ‘Public preview of the new F&O dev experience’ »
The usual setup (documented by Microsoft) of version control for F&O is using Team Foundation Version Control and configuring the workspace mapping like this: $/MyProject/Trunk/Main/Metadata k:\AosService\PackagesLocalDirectory $/MyProject/Trunk/Main/Projects c:\Users\Admin123456789\Documents\Visual Studio 2019\Projects This means that PackagesLocalDirectory contains both standard packages (such as ApplicationSuite) and custom packages, i.e. your development and ISV solutions you’ve installed. This works fine …
Continue reading ‘F&O development with multiple version control workspaces’ »
Acceptance Test Library (ATL) in F&O isn’t a new feature, but many people aren’t aware of it, therefore let me try to raise awareness a bit. ATL is used in automated tests written by developers and its purpose is to easily create test data and verify results. Here is an example of such a test: …
Somebody asked in the Community forum for examples of display methods in views in the standard D365FO application. It’s not necessary to remember any concrete examples – finding all such methods is very simple. The right tool for this purpose is Metadata search. Open Metadata search (Visual Studio > Dynamics 365 > Metadata search) and …
Do you have many tabs in Visual Studio with designers and code editors and do you struggle to make sense of them? It’s not surprising – we often work with many things at once and some elements even have same names (e.g. VendTable table and form), which means that tabs for them look identical. Wouldn’t it …
