Finance forum

Show AOT twice in Visual Studio

(0) Share

Report

Posted on by Community Member

Hi Community,

is there a way to open the AOT Window twice ? Like can I have two or more AOT Windows in VS ? In AX it was possible.

I have the same question (0)

All responses (8)

Answers (2)

Verified answer

nmaenpaa 101,166 Moderator on at

Like (1)

Report
Copy link

Link copied!

To my knowledge it's not possible. Visual Studio will show only one Application Explorer window.

Was this reply helpful? Yes No
Verified answer

Tommy Skaue Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

While it can cause some issues around "files in use", you can try having multiple instances of Visual Studio running.

Was this reply helpful? Yes No
Joris dG 17,780 on at

Like (0)

Report
Copy link

Link copied!

Looks like you already have your answer. But I'm curious to know why you need this?

Was this reply helpful? Yes No
FlorinF on at

Like (0)

Report
Copy link

Link copied!

Hi Joris de Gruyter

It's very useful to have multiple AOT windows, because as a developer you work with multiple objects in the same time: Tables, Forms, Queries etc. It's very time consuming to navigate every time through AX objects when you need to investigate just a single object. For example, take the queries or views in ax: you will need to switch back and forth between objects. It's time consuming and you can't have a clear image of the relation/properties between objects. I miss very much the flexibility that we had in 2012.

For example, in 2012 we can have a view like this when we work with DirParty structure. It's very useful when you have multiple tables and classes working together.

Multiple AOT windows was the most useful tool for ax developers. Since AX have more then 5000+ tables and forms, it's a sure thing that you will not work with only one object in the same time .

Was this reply helpful? Yes No
Martin Dráb 238,782 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

You're not using Visual Studio in the right way. The place where you should work is a project (Solution Explorer), not Application Explorer.

Find the objects want (e.g. by filtering Application Explorer with ^DirParty) and them to a project. Then you don't have to go back and forth in Application Explorer - you already have all your objects in front of you.

Just note that each project can hold only objects from a single model - but nothing prevents you from having multiple projects in a single solution.

Was this reply helpful? Yes No
Tommy Skaue Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I would suggest pull in the elements you are working into a solution. You will have one project per model, but that way you can have the elements you need to look at handy. The Solution and Project(s) are just a way to group the elements you're working on or reference. Nothing more. Even if you include CustTable to the solution, you do not have to build the table, just your extension of it - if that makes sense.

Was this reply helpful? Yes No
FlorinF on at

Like (0)

Report
Copy link

Link copied!

Hi Martin Dráb

What are you suggesting is actually to take an object from AOT tool window and move it to an other tool window, like project. How does this help?

There is no use to me to add AOT objects to the project, actually I don't want every object that I'm looking at to be in my project.

You are missing the point here. I want the possibility to look at multiple objects in the same time by having one AOT filtering a specific model, one AOT filter by a specific table, an other AOT just to look at a class methods. I don't want to drag into my project those objects.

Was this reply helpful? Yes No
Martin Dráb 238,782 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

How does this help? It solves your problem of having "to switch back and forth between objects". It gives you "the possibility to look at multiple objects in the same time".

Sure, I too "don't want every object that I'm looking at to be in my project" - just the ones I need "to switch back and forth".

Regarding "just to look at a class methods", open the class is the designer (and possibly pin the tab). It, unlike Application Explorer, will allow you things like opening a method by double-clicking. You can also filter method names in the designer.

I'm sorry that you dislike the way how Visual Studio works, but there is little you can do besides of getting used to it. Fortunately there are many great features that you'll love, you'll just have to do certain things differently than in MorphX.

Was this reply helpful? Yes No