Office.ASP.NETCoreReactAddins can not be loaded the add-in module by Excel in debugging. about office-add-in-samples HOT 3 CLOSED

It is not what I see (it loads on my machine and able to stop on a breakpoint), technically I think @yhayak872 is right and the URL in the manifest should be index.html

The unmodified project works however on my machine (I live streamed it on YouTube so if you have a couple of hours you can look back what I did 😉).

Out of the box it did work for me:

The URL in the manifest.xml will reflect on runtime though like this:

After changing the manifest to index.html you will get this:

Either way in both scenarios I see the page to be resolved to https:.//localhost:44340 (as defined in the VS settings)

My guess is that .NET Core is resolving the URL to index.html, not sure why this is not happening with @yhayak872
(maybe the issue is related to the fact that the URL sometimes is given ending on $$$$3 ?)

The livestream where I debugged this can be found here:
Live stream here

from office-add-in-samples.

Thank you to report many information and suggestions. Your live stream was very helpful for me.
After your report, I checked again my project and executed.
Curiously, My Project worked fine too with original URL path ( it is "~remoteAppUrl/taskpane.html" ).
But I can not understand why it did not work before because I have not modified anything but above URL.
After my report, my machine had two updates for .NET- flamework ( KB4576484, KB45707323 ) and these may be related this.
.NET core resolves the requested URL to index.html as you say, therefor any URL was working as long as the file name doesn't match. ( ex: "~remoteAppUrl/anything.html" or "~remoteAppUrl/")
Thanks a lot.

-PS-
This is not related to above but I can not set breakpoint well on Apps.js as you did.
VS said "the breakpoint will not currently be hit. ... " like this.

I'm checking continuously to resolve this. (I'll ask again this to other proper forum.)
Best regard.

from office-add-in-samples.

This is a post-report of this issue.
Repairing my Visual Studio resolved the breakpoint issue.
Perhaps the first problem of not loading the add-in module is for the same reason too.
My Visual Studio was updated several times while debugging this add-in project, so it's possible that Visual Studio wasn't working properly.

Best regard.

from office-add-in-samples.