Why has this been allowed to get through QA? Don't you guys have any regression testing? It makes you wonder.....
Do you have an eta on when this will get fixed? I assume that it WILL be when..

Yes it's a very annoying issue and will waste my time in having to manually implement what used to be done by the wizard. Why continue to ship ATL then break the tools that support it?

So...original issue entered in July, and unless I am missing something there has been not one comment from the VS team? This is unacceptable. I hate the fact that I am being forced by a third party to even write a COM dll, something I was quite good at sixteen years ago but remember shockingly little about. Now I find that my job is going to be made just that much harder by a team that appears to care very little about the fact they have completely screwed up fundamental support for authoring these projects.

This blows. You guys should really be embarrassed by this,but given the lack of attention to this thread I am assuming everybody is sleeping soundly in houses paid for by our MSDN subscriptions.

I re-installed VS 2015 and the wizard works well there.

still running the visual studio 2015 runtime for that very reason.

I found the old wizard painfully slow if I had more than a few COM objects.

So, these days, I manually edit the idl, h and cpp files after creating a COM class with Add New Item/ATL Simple Object. It helps that I have plenty of similar methods already defined that I can use as templates.

Visual Studio 2019 version 16.2 Preview 1 (released last week) now has fixes for the issues reported by Christian.

If you can try that build we would appreciate your feedback on the updates.

As Marian said, we want to make sure we've addressed your feedback before we take these changes back to VS 2017.