Just open the properties pane for the manifest project, and set the start action to Internet Explorer or Chrome. Since you already are in Visual Studio, and if you have an Office 365 for Business tenant you could use the actual built-in feature for debugging in Excel Online. But the manifest itself is not actually 'valid' in that it doesn't have real URLs - just things like ' ~remoteAppUrl/App/Auth/About.html' instead of ' Two things you can do: the reason it works on desktop through Visual Studio is that VS does a special F5 process where it automatically substitutes the relative web paths with the spun-up IIS location. Is that true?Īssuming my assumption is true. Taking a guess from looking at the manifest, I would guess that by 'runs correctly in Excel 2016 on my machine', you mean that you can 'F5' in Visual Studio and it runs correctly.
