eXpand
eXpand copied to clipboard
XpandModelEditor fails with .netcore/blazor models
apparently as it uses the full netframework
We will try to answer all questions that do not require research within 24hr. To prioritize cases that require research we use the following labels in order. For all other issues the posting time is respected.
- ❇️ Exclusive-Services
- ❤ Bronze Sponsor
- ❤ Sponsor
- ❤ Backer
- Installation
- ShowStopper
- Nuget
- Contribution
- BreakingChange
- ReproSample
- Deployment
- must-have
This case is prioritized.
eXpand.lab release 20.2.401.3 includes commit that relate to this task:
- VSIX XpandModelEditor support Blazor application project models #792
- VSIX: ModelEditor fails to resolve Dependencies #792
Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS.
To minimize version conflicts we recommend that you switch to PackageReference format and use only the eXpandAgnostic, eXpandWin, eXpandWeb packages. Doing so, all packages will be at your disposal and .NET will add a dependecy only to those packages that you actually use and not to all (see the Modules installation-registrations youtube video).
Thanks a lot for your contribution.
eXpand.lab release 20.2.500.0 includes commit that relate to this task:
Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS.
To minimize version conflicts we recommend that you switch to PackageReference format and use only the eXpandAgnostic, eXpandWin, eXpandWeb packages. Doing so, all packages will be at your disposal and .NET will add a dependecy only to those packages that you actually use and not to all (see the Modules installation-registrations youtube video).
Thanks a lot for your contribution.
Issue is deprioritized as no Assignee found and scheduled for auto-close if no activity in the next 60 days. Thanks a lot for your contribution.
Closing issue for age. Feel free to reopen it at any time.
.Thank you for your contribution.