How can I maintain different features having dialog/forms through different projects in one application in MFC?

Question

1.00/5 (1 vote)

See more:

VS2010

I am having an MFC application of SDI document with multiple views developing in Visual Studio 2010. I have shown functionality of each view in individual tab. Even the ribbon bar will show buttons related to both views.
Currently I am having one project showing each view in different tabs/windows.

Now I want to add some different functionality in that application, to be shown in new tab means one more view. It will have forms/dialogs to show controls in that tab. I prefer to separate the functionality and code files from the main project, so created a new project and created a form/dialog. So now I have two projects in same solution. This form/dialog will have its unique ID. This new project will also have .rc file and resoure.h. So when I use the source file of form/dialog created in new project, in main project, it is not able to identify the ID.

It is possible to maintain different projects in such situation, and access forms/dialogs of other project in main project in same application solution? How can I achieve this? Or is there any other way to maintain integrity of different functionalities in same solution?

Thanks in advance.

Posted 10-Sep-15 20:43pm

Sweta Mittal

Updated 11-Sep-15 0:51am

v7

Add a Solution

Comments

Sergey Alexandrovich Kryukov 11-Sep-15 3:13am

Not clear how you view that. Why? What is "same application code"?
—SA

Sweta Mittal 11-Sep-15 3:28am

I mean in one document has multiple views and each view is associated with each tab. With "same application code" I mean to say that multiple projects in same solution. Thanks

Sergey Alexandrovich Kryukov 11-Sep-15 3:32am

You express yourself in extremely unclear way, sorry; the term "same application code" is a bright illustration. I wish you could explain the rest as clearly as the part "multiple projects in the same solution".
—SA

Richard MacCutchan 11-Sep-15 4:27am

You could create each of your viewing projects as a library (static or DLL), with their own resource file. You then use the main project to call their functions as you need them. The real issue is whether the work to create these projects would make it easier to maintain.

Sweta Mittal 11-Sep-15 8:52am

I tried by creating static library, normal functions are called. But how to access form/dialog to be shown in tab. Its resource id is not identified in main project.

Richard MacCutchan 11-Sep-15 9:01am

You need to add the resource ids to the DLL's associated header file, ensuring that each DLL has a unique set of ids. You can also use strings rather than numbers to address resources.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

KarstenK · Answer 1 · 2015-09-11T00:04:00

Yes. The concept of solutions in Visual Studio is to include multiple projects and build targets. If you right click in the project explorer at the solution you should find a menu to add a project.

To organize it, it is best to create subfolders on disc to store the different project files separate. Use macros to separate some additional code or resources. It can get tricky, so make regularly a backup.