Jaliya Udagedara

For some reason, I still need to explicitly accept *. If you are PowerShell, came up with this workaround, Edit PowerShell profile ``` code $PROFILE # or notepad $PROFILE ```...

Seems this suggested hasn't moved to the specification yet. Should we update the spec?

@elachlan, I am extremely sorry for the delay in responding. Hmm, that's interesting. This is what I am seeing.  Let me see what else I can provide.

When I close the solution and open the solution back, it works. This is the output I am getting. ``` [22:24:01.965947] info: Creating VsDesignerLoader [22:24:02.028950] info: [Thread 1] Creating design-time...

Updated Visual Studio to `Visual Studio 17.10 – Preview 2` ``` Microsoft Visual Studio Enterprise 2022 (64-bit) - Preview Version 17.10.0 Preview 2.0 ``` Same error!  But with more...

I have repaired Visual Studio, still the same :(. I am on `Windows 11 Pro for Workstations`:  Not sure whether screen resolution matters:  A key thing is, when...

I have reported the issue through `Visual Studio Developer Community`, captured all the logs, and included them in the report. Issue: [Windows Forms Designer not loading: System.InvalidOperationException: Designer load encountered...

Related: #295

And I am seeing we are using `Azure.AI.FormRecognizer`, shouldn't we be moving to `Azure.AI.DocumentIntelligence`?

Personally, I would definitely not vote for transaction per migration. At least it shouldn't be baked in and maybe an opt-in feature. I am voting 110% on introducing an option...