Running React app through Azure WebApp locally
up vote
0
down vote
favorite
I created a new react app and also a new project on Visual Studio: .NET Framework Web Application, under my Azure subscription.
What should be the process so when I run the Web Application locally, I will see the new react app and not the ASP.NET screen ?
I deployed the new react app to azure so when I run the website I do see the new react app, however when I run it from the .sln file, I get this screen:
Thanks in advance!
reactjs
azure web-applications deployment asked Nov 11 at 11:31
I.zv
1029
add a comment |
up vote
0
down vote
favorite
I created a new react app and also a new project on Visual Studio: .NET Framework Web Application, under my Azure subscription.
What should be the process so when I run the Web Application locally, I will see the new react app and not the ASP.NET screen ?
I deployed the new react app to azure so when I run the website I do see the new react app, however when I run it from the .sln file, I get this screen:
Thanks in advance!
reactjs
azure web-applications deployment asked Nov 11 at 11:31
I.zv
1029
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I created a new react app and also a new project on Visual Studio: .NET Framework Web Application, under my Azure subscription.
What should be the process so when I run the Web Application locally, I will see the new react app and not the ASP.NET screen ?
I deployed the new react app to azure so when I run the website I do see the new react app, however when I run it from the .sln file, I get this screen:
Thanks in advance!
reactjs
azure web-applications deployment asked Nov 11 at 11:31
I.zv
1029
I created a new react app and also a new project on Visual Studio: .NET Framework Web Application, under my Azure subscription.
What should be the process so when I run the Web Application locally, I will see the new react app and not the ASP.NET screen ?
I deployed the new react app to azure so when I run the website I do see the new react app, however when I run it from the .sln file, I get this screen:
Thanks in advance!
reactjs
azure web-applications deployment reactjs
azure web-applications deployment asked Nov 11 at 11:31
I.zv
1029
asked Nov 11 at 11:31
I.zv
1029
asked Nov 11 at 11:31
I.zv
1029
asked Nov 11 at 11:31
I.zv
1029
asked Nov 11 at 11:31
I.zv
1029
1029
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I think the step you missed is to update the Index view which is used to generate the website root to include the bootstrapping of the React app. It should be located at Views/Home/Index.cshtml or Pages/Index.cshtml, depending on the template you used when you created the project.
As a side note, I would consider dropping the ASP.Net project entirely and just use VS Code for the React app, through there you can easily deploy your app to an Azure Storage Account using the new Static website hosting in Azure Storage, thus removing the need for an ASP.Net website.
Hope it helps!
answered Nov 11 at 14:52
Itay Podhajcer
1,117312
As I need to configure my webApp to work with Azure storage table I'm afraid I will still need to use the .Net project as it will be the server or "hosting" side. Also, can you please elaborate about the first part of your answer? thanks!
– I.zv
Nov 11 at 15:57
I would still separate it to two different projects: one for the React app and one for the server side API, which in turn has access to the Azure table. Using the Azure Storage Static Website hosting will save both technical issues (due to npm compatibility issues) and cost, as downloading the API won't utilize VM resources
– Itay Podhajcer
Nov 11 at 18:00
Regarding the update required for the Index view, the most simple way for you to see how the React app needs to be integrate, will be to generate an ASP.Net Core React app (it is available on the wizard when creating a ASP.Net App)
– Itay Podhajcer
Nov 11 at 18:05
Well I will try this out. Toda Raba :)
– I.zv
Nov 11 at 21:44
Happy to help :)
– Itay Podhajcer
Nov 11 at 22:12
|
show 2 more comments
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I think the step you missed is to update the Index view which is used to generate the website root to include the bootstrapping of the React app. It should be located at Views/Home/Index.cshtml or Pages/Index.cshtml, depending on the template you used when you created the project.
As a side note, I would consider dropping the ASP.Net project entirely and just use VS Code for the React app, through there you can easily deploy your app to an Azure Storage Account using the new Static website hosting in Azure Storage, thus removing the need for an ASP.Net website.
Hope it helps!
answered Nov 11 at 14:52
Itay Podhajcer
1,117312
As I need to configure my webApp to work with Azure storage table I'm afraid I will still need to use the .Net project as it will be the server or "hosting" side. Also, can you please elaborate about the first part of your answer? thanks!
– I.zv
Nov 11 at 15:57
I would still separate it to two different projects: one for the React app and one for the server side API, which in turn has access to the Azure table. Using the Azure Storage Static Website hosting will save both technical issues (due to npm compatibility issues) and cost, as downloading the API won't utilize VM resources
– Itay Podhajcer
Nov 11 at 18:00
Regarding the update required for the Index view, the most simple way for you to see how the React app needs to be integrate, will be to generate an ASP.Net Core React app (it is available on the wizard when creating a ASP.Net App)
– Itay Podhajcer
Nov 11 at 18:05
Well I will try this out. Toda Raba :)
– I.zv
Nov 11 at 21:44
Happy to help :)
– Itay Podhajcer
Nov 11 at 22:12
|
show 2 more comments
up vote
0
down vote
I think the step you missed is to update the Index view which is used to generate the website root to include the bootstrapping of the React app. It should be located at Views/Home/Index.cshtml or Pages/Index.cshtml, depending on the template you used when you created the project.
As a side note, I would consider dropping the ASP.Net project entirely and just use VS Code for the React app, through there you can easily deploy your app to an Azure Storage Account using the new Static website hosting in Azure Storage, thus removing the need for an ASP.Net website.
Hope it helps!
answered Nov 11 at 14:52
Itay Podhajcer
1,117312
As I need to configure my webApp to work with Azure storage table I'm afraid I will still need to use the .Net project as it will be the server or "hosting" side. Also, can you please elaborate about the first part of your answer? thanks!
– I.zv
Nov 11 at 15:57
I would still separate it to two different projects: one for the React app and one for the server side API, which in turn has access to the Azure table. Using the Azure Storage Static Website hosting will save both technical issues (due to npm compatibility issues) and cost, as downloading the API won't utilize VM resources
– Itay Podhajcer
Nov 11 at 18:00
Regarding the update required for the Index view, the most simple way for you to see how the React app needs to be integrate, will be to generate an ASP.Net Core React app (it is available on the wizard when creating a ASP.Net App)
– Itay Podhajcer
Nov 11 at 18:05
Well I will try this out. Toda Raba :)
– I.zv
Nov 11 at 21:44
Happy to help :)
– Itay Podhajcer
Nov 11 at 22:12
|
show 2 more comments
up vote
0
down vote
up vote
0
down vote
I think the step you missed is to update the Index view which is used to generate the website root to include the bootstrapping of the React app. It should be located at Views/Home/Index.cshtml or Pages/Index.cshtml, depending on the template you used when you created the project.
As a side note, I would consider dropping the ASP.Net project entirely and just use VS Code for the React app, through there you can easily deploy your app to an Azure Storage Account using the new Static website hosting in Azure Storage, thus removing the need for an ASP.Net website.
Hope it helps!
answered Nov 11 at 14:52
Itay Podhajcer
1,117312
I think the step you missed is to update the Index view which is used to generate the website root to include the bootstrapping of the React app. It should be located at Views/Home/Index.cshtml or Pages/Index.cshtml, depending on the template you used when you created the project.
As a side note, I would consider dropping the ASP.Net project entirely and just use VS Code for the React app, through there you can easily deploy your app to an Azure Storage Account using the new Static website hosting in Azure Storage, thus removing the need for an ASP.Net website.
Hope it helps!
answered Nov 11 at 14:52
Itay Podhajcer
1,117312
edited Nov 11 at 15:02
answered Nov 11 at 14:52
Itay Podhajcer
1,117312
answered Nov 11 at 14:52
Itay Podhajcer
1,117312
answered Nov 11 at 14:52
Itay Podhajcer
1,117312
1,117312
As I need to configure my webApp to work with Azure storage table I'm afraid I will still need to use the .Net project as it will be the server or "hosting" side. Also, can you please elaborate about the first part of your answer? thanks!
– I.zv
Nov 11 at 15:57
I would still separate it to two different projects: one for the React app and one for the server side API, which in turn has access to the Azure table. Using the Azure Storage Static Website hosting will save both technical issues (due to npm compatibility issues) and cost, as downloading the API won't utilize VM resources
– Itay Podhajcer
Nov 11 at 18:00
Regarding the update required for the Index view, the most simple way for you to see how the React app needs to be integrate, will be to generate an ASP.Net Core React app (it is available on the wizard when creating a ASP.Net App)
– Itay Podhajcer
Nov 11 at 18:05
Well I will try this out. Toda Raba :)
– I.zv
Nov 11 at 21:44
Happy to help :)
– Itay Podhajcer
Nov 11 at 22:12
|
show 2 more comments
As I need to configure my webApp to work with Azure storage table I'm afraid I will still need to use the .Net project as it will be the server or "hosting" side. Also, can you please elaborate about the first part of your answer? thanks!
– I.zv
Nov 11 at 15:57
I would still separate it to two different projects: one for the React app and one for the server side API, which in turn has access to the Azure table. Using the Azure Storage Static Website hosting will save both technical issues (due to npm compatibility issues) and cost, as downloading the API won't utilize VM resources
– Itay Podhajcer
Nov 11 at 18:00
Regarding the update required for the Index view, the most simple way for you to see how the React app needs to be integrate, will be to generate an ASP.Net Core React app (it is available on the wizard when creating a ASP.Net App)
– Itay Podhajcer
Nov 11 at 18:05
Well I will try this out. Toda Raba :)
– I.zv
Nov 11 at 21:44
Happy to help :)
– Itay Podhajcer
Nov 11 at 22:12
As I need to configure my webApp to work with Azure storage table I'm afraid I will still need to use the .Net project as it will be the server or "hosting" side. Also, can you please elaborate about the first part of your answer? thanks!
– I.zv
Nov 11 at 15:57
As I need to configure my webApp to work with Azure storage table I'm afraid I will still need to use the .Net project as it will be the server or "hosting" side. Also, can you please elaborate about the first part of your answer? thanks!
– I.zv
Nov 11 at 15:57
I would still separate it to two different projects: one for the React app and one for the server side API, which in turn has access to the Azure table. Using the Azure Storage Static Website hosting will save both technical issues (due to npm compatibility issues) and cost, as downloading the API won't utilize VM resources
– Itay Podhajcer
Nov 11 at 18:00
I would still separate it to two different projects: one for the React app and one for the server side API, which in turn has access to the Azure table. Using the Azure Storage Static Website hosting will save both technical issues (due to npm compatibility issues) and cost, as downloading the API won't utilize VM resources
– Itay Podhajcer
Nov 11 at 18:00
Regarding the update required for the Index view, the most simple way for you to see how the React app needs to be integrate, will be to generate an ASP.Net Core React app (it is available on the wizard when creating a ASP.Net App)
– Itay Podhajcer
Nov 11 at 18:05
Regarding the update required for the Index view, the most simple way for you to see how the React app needs to be integrate, will be to generate an ASP.Net Core React app (it is available on the wizard when creating a ASP.Net App)
– Itay Podhajcer
Nov 11 at 18:05
Well I will try this out. Toda Raba :)
– I.zv
Nov 11 at 21:44
Well I will try this out. Toda Raba :)
– I.zv
Nov 11 at 21:44
Happy to help :)
– Itay Podhajcer
Nov 11 at 22:12
Happy to help :)
– Itay Podhajcer
Nov 11 at 22:12
|
show 2 more comments
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248296%2frunning-react-app-through-azure-webapp-locally%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
