hi all,
I am experimenting adding WPF controls to an existing MFC app. Everything seems to work fine except that everytime i make changes to the WPF control xaml, the hole MFC app recompile itself. I looked at the sample app in the handon lab, and it does the same thing. Is there a way to get around this
jz
WPF in MFC App
Hot Topic
- Generating Type from Xsd using SVCUTIL tool
- The long term goal of Cider vs.XAML
- Wrong Re-Install Procedure. Problems running VS2005.
- Can't stop StoryBoard
- z-order in XAML?
- ServiceHost OnApplyconfiguration
- Get pinned version of VSS through automation
- How to pass parameters to Web Browser Application?
- Report Viewers
- Visual Basic 2005 Express / Excel 2000
Visual Studio
- Add IVsUIHierarchy to Team Explorer
- IVsHiColorItem caching
- Binding to a list box item in code
- DLinq Sql Tracing
- SourceSafe setup fails, exits in an unusual way
- Visual Studio 2005 RC and WinFX SDK
- North Face Demo errors
- Comments and CommentShapes
- Message protection for an arbitrary function?
- Crystal Reports
WPF in MFC App
Csabi
I am not familiar with the code of the hands on lab. But the following usually happens when a user-defined header is included in stdafx.h. Perhaps each time when you change XAML, it changes a specific header file in WPF project. Same header is included in stdafx.h of the MFC Project. If WPF's headers is changed, IDE is going to recompile pre-compiled header (stdafx.h) and then re-build whole MFC project.
Nikola
VC++
JohnYe
Hi,
This usually happens because of IDE detecting that a piece of code that other code depends on has been changed. Are these two projects One project with several files How does MFC code knows about WPF control #include, added reference on a project level
Nikola
VC++
Lelle