Search

DECLARE_DYNAMIC in CMFCEditBrowseCtrl missing by tobias.loew

Closed
as Fixed Help for as Fixed

2
0
Sign in
to vote
Type: Bug
ID: 724022
Opened: 2/8/2012 4:17:39 AM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
1
User(s) can reproduce this bug
CMFCEditBrowseCtrl does not have a DECLARE_DYNAMIC declaration.
Thus

IMPLEMENT_DYNAMIC(CMyMFCEditBrowseCtrl, CMFCEditBrowseCtrl)

produces a compiler error if _AFXDLL is not defined (i.e. linking mfc statically)

(of course writing
IMPLEMENT_DYNAMIC(CMyMFCEditBrowseCtrl, CEdit)
instead solves the problem)
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling version

Visual Studio 2010

Steps to reproduce

derive your own class CMyMFCEditBrowseCtrl from CMFCEditBrowseCtrl, choose static MFC and comiple
IMPLEMENT_DYNAMIC(CMyMFCEditBrowseCtrl, CMFCEditBrowseCtrl)

!!! please see also my latest comment !!! (from March 5th 2012)

Product Language

German

Operating System

Windows Server 2008 R2

Operating System Language

German

Actual results

compiler error

Expected results

no compiler error
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 3/14/2012 at 12:59 AM
Thanks again for your feedback. We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.These specialized experts will follow-up with your issue.
Posted by tobias.loew on 3/7/2012 at 1:31 AM
Hello,

I'm sorry for reacting so late. But I'm not sure if you understood the problem.
Steps to reproduce are: Create an new MFC-Application project and make it statically linking to the MFC-library. Then derive your own class (e.g. CMyMFCEditBrowseCtrl) from CMFCEditBrowseCtrl with DECLARE_DYNAMIC inside the class and IMPLEMENT_DYNAMIC(CMyMFCEditBrowseCtrl, CMFCEditBrowseCtrl) in the classes implementation file.

If you are not sure what to do, please forward the problem to someone who knows the MFC.

Thank you
Posted by Microsoft on 2/28/2012 at 9:50 PM
Hello,

At this point, it has been more than two weeks since we initially requested additional information to reproduce your issue. Since we have not heard back from you we will close the issue. If you need further assistance on this or any other issues in the future, please feel free to contact us and we will be happy to help.
Posted by Microsoft on 2/21/2012 at 10:50 PM
Hello,

Sorry for bothering. Is there any update?

It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.
Posted by MS-Moderator08 [Feedback Moderator] on 2/9/2012 at 2:34 AM
Thank you for reporting this issue. Could you please attach a sample project about this issue?
Posted by MS-Moderator01 on 2/8/2012 at 4:45 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.