Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: How to run "BasicTestApp" from Visual Studio #15474

Closed
StevenTCramer opened this issue Nov 13, 2018 · 3 comments
Closed

Question: How to run "BasicTestApp" from Visual Studio #15474

StevenTCramer opened this issue Nov 13, 2018 · 3 comments
Labels
area-blazor Includes: Blazor, Razor Components

Comments

@StevenTCramer
Copy link
Contributor

I have Blazor building locally now and all the test cases pass, I want to add another test case for SVGs to first correctly catch the error then fix it.

I want to be able to run the "BasicTestApp" but when I attempt to I get:

jsinteroptests.js:1 Uncaught SyntaxError: Unexpected token <
blazor.webassembly.js:1 Uncaught SyntaxError: Unexpected token <

Looking at the "Network" tab, I see it is returning html. thus the error... but why?

I turn off headless on selenium tests and see that this app actually loads for the tests... why doesn't it when I just set it as StartUp Project and run from Visaul Studio?

Thanks.

@StevenTCramer
Copy link
Contributor Author

I thought it had to do with
missing:
"commandLineArgs": "--pathbase=/subdir",

But I still get the same error.

@StevenTCramer
Copy link
Contributor Author

Only way I can get it to run is by removing the tag and all refs to the subdir.

@SteveSandersonMS
Copy link
Member

Instead of running BasicTestApp directly, run TestServer. You can then browse to either of the following:

  • /subdir for client-side (WebAssembly) execution
  • /subdir#server for servier-side execution

@mkArtakMSFT mkArtakMSFT transferred this issue from dotnet/blazor Oct 27, 2019
@mkArtakMSFT mkArtakMSFT added the area-blazor Includes: Blazor, Razor Components label Oct 27, 2019
@dotnet dotnet locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components
Projects
None yet
Development

No branches or pull requests

3 participants