Any more information? Which version of Visual Studio? Installed manually or with NuGet?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2019-05-17
Manually. VS 2017 and VS 2019. Both fail
Nuget does not have AppWizard, I believe.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2019-05-17
OK, it succeeds in a fresh VS install, but somehow after it was installed in the past, it fails to create the project properly even though the AppWizard setup reports success. Maybe there is some bulletproof way to uninstall a previous wizard.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2019-05-19
My earlier conclusion was mistaken. After real research (ProcMon) i found that if the setting "Beta: Use UTF-8 for worldwide language support" is checked (Administrative, regional settings), then it fails. Once cleared, system restarted, the wizard works just fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm... I don't know why would this happen. Can you check the ABSOLUTE_PATH line in WTL10AppWiz.vsz? Does it contain the correct path to where the App Wizard files are?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did some digging and figure out what is going on. WTL App Wizard uses Visual Studio Wizard Engine to parse the list of files to be included in the project. The negine creates a file with parsed list. If UTF-8 is enabled, that file has UTF-8 BOM characters are the beggining (EF BB BF). Engine then uses that created file to find source files, and because of the BOM it cannot find the file.
I think that the problem is with Wizard Engine in Visual Studio. I can't change anything in WTL App Wizard to fix this.
I filed a new problem report with Visual Studio.
Cheers,
Nenad
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Copy the message "Cannot find: ...\AppWizard\Files\Templates\1033\stdafx.cpp" as is with Ctrl+C when the error message appears. If you check, you'll see that there's a hidden unicode character before "stdafx.cpp".
Go to ...\AppWizard\Files\Templates\1033\, copy stdafx.cpp, and rename it to the copied "stdafx.cpp" with the hidden unicode character. You'll see as if you have two "stdafx.cpp" files in the same folder.
Generate the project, it will work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Any more information? Which version of Visual Studio? Installed manually or with NuGet?
Manually. VS 2017 and VS 2019. Both fail
Nuget does not have AppWizard, I believe.
OK, it succeeds in a fresh VS install, but somehow after it was installed in the past, it fails to create the project properly even though the AppWizard setup reports success. Maybe there is some bulletproof way to uninstall a previous wizard.
My earlier conclusion was mistaken. After real research (ProcMon) i found that if the setting "Beta: Use UTF-8 for worldwide language support" is checked (Administrative, regional settings), then it fails. Once cleared, system restarted, the wizard works just fine.
Hmm... I don't know why would this happen. Can you check the ABSOLUTE_PATH line in WTL10AppWiz.vsz? Does it contain the correct path to where the App Wizard files are?
WTL10AppWiz.vsz is in <vsfolder>\Common7\IDE\VC\vcprojects</vsfolder>
I did some digging and figure out what is going on. WTL App Wizard uses Visual Studio Wizard Engine to parse the list of files to be included in the project. The negine creates a file with parsed list. If UTF-8 is enabled, that file has UTF-8 BOM characters are the beggining (EF BB BF). Engine then uses that created file to find source files, and because of the BOM it cannot find the file.
I think that the problem is with Wizard Engine in Visual Studio. I can't change anything in WTL App Wizard to fix this.
I filed a new problem report with Visual Studio.
Cheers,
Nenad
This is the reported problem: https://developercommunity.visualstudio.com/content/problem/603411/visual-studio-custom-app-wizard-engine-creates-utf.html
I can't do anything to fix this - it must come from Visual Studio since they own the App Wizard engine.
This is "Closed-external" now. Feel free to reopen if there is a need to follow up.
Encountered it too. Dirty workaround:
Oh, and: