After looking at the generated application, there are a few things that I consider a deviation from other projects, particularly those using precompiled headers, so I'll outline them.
The use of using directives and declarations in header files, which I already wrote a long post. I still think it is a bad practice that will spread very quickly through the canned project templates provided by VS.
Inclusion of App.xaml.h in pch.h, and viceversa: inclusion of
pch.h in App.xaml.h. Before you say...but it uses
#pragma once, that's not the point. What I'd like to know is why is it included also in
App.xaml.hand MainPage.xaml.h. It seems that the template is "pch happy", and the bigger problem is that this practice would break the "self sufficient header files" good practice. The typical project without
precompiled headers, assuming one class per header files, #include's the header file for the class as the first file. When using precompiled headers, the stdafx.h is the first header file, followed by the corresponding header file:
I could not find anyone reporting this feedback so far. Could you send this feedback thru our Connect site so our team that builds the templates is sure to get this?
Here are the instructions if you haven't used it yet.
Thanks so much!
Thank you for posting your feedback, we want to make sure we get the right info including your log files. Can you also submit feedback using the Windows Feedback Tool from
the Connect Site associated with your Windows Developer Preview program? If you’re an MSDN subscriber, the information on how to join the Connect program is included on the download page where you installed Windows
Developer Preview. There’s a link to the Connect site and an invitation code that you can click on to join using a Windows Live ID account. If you’re not an MSDN subscriber follow this limited use
to join the Connect program and then follow the steps here.