The backend (.net core) does not allow to make the request from a different domain. Another port is also restricted. Have a look at this site for solving your problem: https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-2.2
I have solved it with this code:

options.AddPolicy(quasarOrigins,
            builder =>
            {
                builder.WithOrigins("http://localhost:8080")
               .AllowAnyHeader();
            });

a-x-i

Hi!
I’m trying the beta version of quasar-framework 1.x
I have a .net core application as backend. In my former testings with framework 0.17 I routed all axios requests to api to http://localhost:5000/api and therefore I had settings in quasar.config.js as follows:

devServer: {
      // https: true,
      // port: 8080,
      open: true, // opens browser window automatically
      proxy: {
        // proxy all requests starting with /api to jsonplaceholder
        '/api': {
          target: 'http://localhost:5000/api',
          changeOrigin: true,
          pathRewrite: {
            '^/api': ''
          }
        }
      }
    },

In axios.js:

export default ({ Vue }) => {
  axios.defaults.baseURL = '/api'
  Vue.prototype.$axios = axios
}

So all axios-requests are going to api and the port 5000 and not to the app port 8080.
But with beta framework I don’t get the api-calls to this port. axios always try to call port 8080 and not 5000.
I compared all settings and the only difference I found was, that axios in 0.17 is in the plugin-folder and now it’s in the boot-folder and also in client-entry.js (in .quasar) this plugin is handled differently.
So what do I have to do (configure) that all my axios calls are going to http://localhost:5000/api/…?
I hope I explained it clearly and my english wasn’t as bad as I think it is
Greetings from Tyrol / Austria!
a-x-i

Thank you max, that did the trick.
I didn’t want to completely remove node because of another app. I thought this would have some sideeffects. But the app runs properly!
Thank you again for you help!
greets from Tyrol (Austria)
a-x-i

How do you solve this problem on windows? I think I’ve the same problem as I mentioned here: http://forum.quasar-framework.org/topic/2023/can-t-update-quasar-cli

[edit] Answered by max in the other thread mentioned [/edit]

thank you
a-x-i

I’ve tried a lot, but nothing works.
Running windows 10
node version: v9.8.0
npm version: 5.6.0
vue-cli version: 2.8.2
everytime I try to run “npm i -g quasar-cli” it seems to work.
output:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.3 (node_modules\quasar-cli\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})

• quasar-cli@0.15.12

if I do “quasar version”:
Quasar CLI v0.6.4
Update available 0.6.4 → 0.15.12 │
Run npm i -g quasar-cli to update

I deleted all appData/Roaming/npm and appData/Roaming/npm-cache. For my user and for admin-user. But my console recognize quasar as a command! Why? I’ve totally removed it and restarted the machine!!

On another machine I’ve installed a starter-Kit for Quasar and everything works fine if I do “quasar dev”.
On this machine if I type “quasar dev” for the same starter-kit: npm ERR! missing script: dev and the “update available” message.

Please help!
thx
a-x-i

Okay I got you!
You have two separate applications. One with dotnet core and one with vue/quasar.

The starter-kit I mentioned has a totally different approach. It’s a .net core mvc-app which uses vue.js and javascript.
The template from dotnet core does the same but with typescript.
The only thing I missed was quasar and I didn’t find any solution so I thought I wait for the umd-version of quasar and now I’m here

Maybe your way will also be my kind of solution!
Thanks a lot again for your help and your time!
a-x-i

Hi!
Thank you for your input.
If you can assist me with your script, it would be very helpful.
But one more question: the starter kit I mentiond is a mvc project, so how would I handle this with a dotnet core mvc project because the view of mvc has to be totally replaced with my quasar/vue view
thx
a-x-i

Has anybody successfully build an app with quasar-framework and dotnet core?
Or maybe somebody can guide me in the right direction to develop one?
I have developed a webapp with this starter kit: https://github.com/MarkPieszak/aspnetcore-Vue-starter
Now I want to develop another one with same starter kit AND quasar-framework.
Should I use UMD or starterKit from quasar and include everything I need for .net core manually?

thx for your help
a-x-i