Hi, as far as I understand, you did not generate-proxy after Suite code generation, right?
You should generate C# proxies, as described in the Microservice Tutorial, here is the link for the related section: https://abp.io/docs/latest/tutorials/microservice/part-03#generating-the-ui-proxy
Please, follow this section and let me know if it's fixed. Best regards.
Thank You. So looking at it I am currently stuck and can't proceed until there is a fix. Please let me know how to proceed in the absence of a fix. If Proxies can't be created then how do we proceed with building UI
Actually there is no blocking problem. You can use the following flow for now ( I assume that you already have an microservice solution ):
I created a Category entity with Name as its only property for demonstration.
Run all projects:
CatalogService's endpoint (/api/abp/api-definition)
Response of the endpoint (catalog section)
Please note that, normally you don't need to manually run the generate-proxy, because ABP Suite already should be doing it for you in the angular code generation. However, if there is a problem you can follow this step and manually generate-proxies.
Change the URL from adminstrationService url's to CatalogService's URL, for only proxy generation, then please don't forget to revert it)
default: {
// url: 'http://localhost:44316', -> administration service
url: "http://localhost:44334", // -> catalog service
rootNamespace: 'Issue8665',
},
Generate proxies:
abp generate-proxy -t ng -m catalog
Hi, yes they need to have an active ABP License to be able to make changes and uses it because LeptonX Theme is a commercial product.
We don't have a guide or documentation that shows how to migrate from LeptonX Theme to LeptonX Lite. However, it's a really straightforward process. You normally just need to change package dependencies and change some constant names. You can take the Installation section in the LeptonX Lite Theme documentation as a guide, which shows how to migrate from Basic Theme to LeptonX Lite theme.
Btw, you can also select LeptonX Lite while creating a solution with ABP CLI (here are all the options: https://abp.io/docs/9.0/cli#options):
abp new MyProjectName --theme leptonx-lite
Please also note that the pro modules are licensed to you, but it is not open source and cannot be redistributed or made publicly available for others to use or modify unless they also have a valid ABP license.
https://abp.io/eula
Also, you can see this comment for further info.
You have to switch it manually. It's too much trouble https://abp.io/docs/latest/studio/version-mapping#abp-studio-and-abp-startup-template-version-mappings
Hi, yes currently there is a restriction as you stated. We have a documentation that shows which ABP Studio version creates templates in which ABP versions: https://abp.io/docs/9.0/studio/version-mapping
You can check this documentation to see the version mapping. We have an internal issue supporting creating a template in a specific version and we will consider it and will try to prioritize it asap.
Thanks for your understanding. Regards.
Hi, thank you for the detailed explanation. We will try to reproduce the problem by following your instructions, then I will let you know about the process.
Regards.
But I believe Abp Studio doesn't allow to create proxy for Angular, is my understanding correct here?
Yes, currently ABP Studio doesn't allow to generate proxies for Angular. However, in case you would need to generate C# or Js proxies, you can use this documentation. We will update the microservice tutorial asap for Angular UI. I've just shared that if you need a guidance. Regards.
I am using Angular as my front end so why should I create proxy for C#. Is my understanding not correct here about proxy generation?
You should only generate proxy for angular. I just shared the documentation to show you where you can do it in Abp Studio UI
The suite doesn't generate the Angular code until you run generate-proxy after using Abp Suite. So the same issue will happen, please provide me a work around until you fix this issue
Hi, for the Microservice template, you should manually generate-proxy (or use the ABP Studio's UI) after Suite code generation. We will update our microservice template, regarding Angular UI.
https://abp.io/docs/latest/tutorials/microservice/part-03#generating-the-ui-proxy
Please open up a new ticket for tracking possible errors etc. for the newly release React native/Expo templates as it would probably be better to track those outside of this thread.
First error after having created a new project in ABP 0.9.22 and just running npx expo start and trying to browse Expo Web
Console:
Refused to execute script from 'http://localhost:8081/node_modules/expo/AppEntry.bundle?platform=web&dev=true&hot=false&transform.engine=hermes&transform.routerRoot=app&unstable_transformProfile=hermes-stable' because its MIME type ('application/json') is not executable, and strict MIME type checking is enabled.Terminal:
Web Bundling failed 6705ms node_modules\expo\AppEntry.js (2320 modules) Unable to resolve "normalize-css-color" from "node_modules\native-base\lib\module\utils\react-native-web-fucntions\normalizeColor.js"Just for reference, this the now closed support ticket about the upgrade itself https://abp.io/support/questions/7625/React-Native--Expo-migration but probably better to have a new ticket for this.
Yes, we updated the React Native template versions in v0.9.22. I will create an internal issue regarding the problem you mentioned.
Do you have any solutions at the moment?
Unfortunately, we don't have a quick solution for that purpose. We have created an internal issue for this and we will consider it for next releases.
