I just hope that you are not developing a standard line of business applications for non-technical users.
I was involved in the line of business applications. which tried to use the Magic library (from memory) and implemented property windows, etc., so it looked "like Visual Studio."
Then we released the prototype for end users, and they hate it. These were non-technical finances and people like accounts, some even experienced users. The main complaints were that "the windows do not stay in one place", "it is too easy to accidentally drag the windows", "too strange", "my window continues to disappear", etc.
Just because your boss thinks the Visual Studio IDE is great doesn't mean your target user group doesn't.
Do not forget that Visual Studio was designed / built by developers for developers. If your users arenโt too technical, it might be wise to prototype them first.
source share